Verisign is terminating third-level .name domains by early 2027, erasing personal websites, email addresses, and API endpoints that some registrants have maintained for nearly 25 years. There's no migration path.
When Neil Fraser registered neil.fraser.name in the early 2000s, it was a deliberate bet on stability. The .name top-level domain, approved by ICANN in its first round in 2000, was purpose-built for personal identity. It predated YouTube, Facebook, and smartphones. For developers and technologists who wanted a permanent home on the internet — one tied to their actual name rather than a platform profile — it was an elegant solution.
Now Verisign, which acquired the original .name registry operator Global Name Registry years ago, is pulling the plug. On April 15, 2026, Verisign proposed discontinuing all third-level .name domain registrations. ICANN approved the request on July 28, 2026. Existing registrations will be terminated, not just frozen. No new third-level domains will be sold.
The impact is small in raw numbers but severe for those affected. Verisign told ICANN that roughly 22,000 third-level .name registrations exist, Domain Name Wire reported, though many are unused. For the active registrants, the consequences cascade far beyond losing a URL.
What's Actually Happening
To understand why this matters, you need to understand how .name worked differently from other domains. Domain Incite explained that .name launched exclusively as a third-level domain operation. If you wanted kevin.murphy.name, the registry would register murphy.name to itself and control the second-level DNS. This meant two unrelated people — say, andrew.hedges.name and david.hedges.name — could register under the same surname through different registrars, years apart, without either owning hedges.name.
This wasn't some shady reseller arrangement. Third-level .name domains had full WHOIS records and were registered through accredited registrars, structurally identical to domains like *.co.uk or *.ny.us. Fraser makes this distinction explicitly on his site, noting that .name's third-level system was fundamentally different from operators who buy a second-level domain in some country-code TLD and resell subdomains underneath it.
Verisign's rationale, per the RSEP filing, is "declining usage and limited registrar support." The registry is simplifying its administration. For a company managing hundreds of millions of domain registrations across multiple TLDs, 22,000 third-level .name domains are a rounding error.
The Identity Cascade
For developers who built on .name, the termination creates a chain of failures that goes well beyond web hosting.
Fraser's case is instructive. As he wrote on his personal site, the termination means his website vanishes in February — despite being paid for until 2040. His email address disappears. IoT devices that call APIs on his domain become bricks. "Basically, I disappear from the Internet," he wrote.
The email problem is especially acute. A decades-old email address isn't just a communication channel. It's the recovery key for countless online accounts, the address on file with banks and government agencies, the contact information embedded in published academic papers and open-source project documentation. Fraser noted there is "no way to enumerate all accounts (online and offline) which have been opened using this email address over the past quarter century".
Domain Name Wire's Andrew Allemann put it plainly: "losing access to a decades-old personal email address would be a serious hardship for almost anyone".
There's also a security dimension: once third-level registrations are terminated, the now-vacant second-level domains presumably become available for registration. As Domain Incite reported, it's unclear how Verisign plans to handle this — through standard drops, auctions, or some other mechanism. If someone registers fraser.name after the third-level domains are deleted, they could potentially receive email intended for any previous fraser.name subdomain holder. That's not just an inconvenience. It's an account hijacking vector.
Why Developers Chose .name in the First Place
The .name TLD appealed to a specific kind of developer: someone who wanted a personal identity layer on the internet that wasn't tied to an employer, a social platform, or a trendy namespace. It was the anti-vanity domain — professional, stable, and semantically clear. Your name, on the internet, as a domain.
This mattered particularly for people who maintained long-running personal sites, contributed to open-source projects under their own name, or ran small API services. The domain wasn't a brand. It was infrastructure for identity.
The appeal also reflected a deeper principle that many technologists held in the early 2000s: that you should own your presence on the internet rather than renting it from a platform. The irony of .name's termination is that the "owned" domain turned out to be just as precarious as a social media profile — subject to the business decisions of a registry operator with no obligation to maintain services indefinitely.
The Migration Gap
What makes this situation particularly frustrating is the absence of any structured domain migration path. Verisign isn't offering domain portability, forwarding services, or transition tools. Registrants are simply being told their domains will cease to exist.
This exposes a rarely discussed gap: there is no standard for migrating a personal identity domain. When a company shuts down, employees update their LinkedIn. When a social platform dies, users move to the next one. But when a TLD effectively evicts you, the remediation is entirely manual and incomplete.
Developers facing this situation have several alternatives, each with tradeoffs:
Country-code and purpose-built TLDs
Domains like .dev (operated by Google), .io, and .me have become popular for developer personal sites. They're widely recognized and well-supported by registrars. The risk is the same one that .name exposed: you're trusting a registry operator's long-term commitment. The .io TLD, for instance, has faced periodic uncertainty tied to the geopolitical status of the British Indian Ocean Territory.
Traditional TLDs with personal branding
A firstname-lastname.com or similar .com/.org registration remains the most portable and widely understood option. It lacks the semantic elegance of .name but carries no third-level dependency risk.
Decentralized identity systems
ENS (Ethereum Name Service) and similar blockchain-based naming systems offer censorship resistance and user ownership. They also carry usability challenges, limited mainstream recognition, and their own set of governance risks.
Platform-based identity
GitHub profiles, personal pages on dev-focused platforms, and even well-maintained LinkedIn profiles serve as de facto identity anchors for many developers. They're not domains you control, but they're unlikely to vanish overnight without warning.
None of these fully replaces what .name offered: a clean, registrar-agnostic, ICANN-governed personal namespace. The closest equivalent would be registering a second-level .name domain, but the uncertainty around how Verisign will handle newly available second-level .name domains makes that a risky bet right now.
What This Means Going Forward
The .name termination is a small-scale event with outsized implications for how developers think about digital identity infrastructure. It demonstrates that even ICANN-approved, registry-operated domain namespaces can be discontinued when the economics stop making sense for the operator.
For the roughly 22,000 registrants affected, the practical advice is unglamorous but urgent: inventory every account tied to your .name email address, set up forwarding or replacement addresses now, and migrate critical services before the February deadline. For IoT devices and API endpoints, there may be no clean fix — just replacement.
For the broader developer community, the lesson is that domain-based identity requires the same redundancy planning as any other infrastructure dependency. A domain is not a permanent address. It's a lease, and the landlord can decide not to renew.
The .name situation also raises a policy question ICANN has yet to meaningfully address: what obligations should registry operators have to long-term registrants when discontinuing services? Fraser's own domain, after all, is paid through 2040. Domain Incite noted that the process for handling the newly available second-level domains remains unclear. A single reconsideration request has been filed and, according to Domain Name Wire, appears on track to be denied.
For a system designed to be the stable addressing layer of the internet, that's a remarkably thin safety net.
