Your Forever Domain Has an Expiration Date

A domain name feels permanent as long as you keep paying the renewal fee. For roughly 22,000 .name registrants, that assumption now has an expiration date: their addresses will disappear by 2040, even if they never miss a payment.

That sounds like the retirement of a niche legacy product. If one of those domains anchors your email, logins, and recovery accounts, it is closer to an identity crisis.

john.smith.name Was a Product, Not Just a Subdomain

The .name top-level domain was designed for personal identities. Its signature format looked like john.smith.name, pairing a first and last name.

Technically, that address resembles a subdomain created by whoever owns smith.name. Commercially, it worked differently. Registrars sold john.smith.name directly to an individual as a third-level domain, with its own registration and renewal cycle.

The system also offered email forwarding. Messages sent to [email protected] could be routed to the user’s regular inbox.

That email layer is where the shutdown becomes dangerous. A website can display a moving notice. An email address may be buried inside hundreds of services as a username, contact address, or password-recovery channel. Most people could not list every account tied to an address they have used for 20 years.

Why 22,000 Domains Are Being Retired

Verisign operates the .name registry, while ICANN oversees the contracts and policies that keep the domain-name system running. Verisign is retiring this legacy third-level registration model, and ICANN has approved the wind-down process.

The addresses will not all vanish overnight. New registrations and renewals are being restricted in stages, while customers retain the time they have already purchased.

Domain registrations can be extended years in advance. The final expiration therefore stretches to 2040, when the longest remaining terms are expected to run out.

From Verisign’s perspective, the logic is straightforward. Maintaining a specialized product for about 22,000 registrations is difficult to justify in a global domain market measured in hundreds of millions.

The structure is awkward, too. If different people own john.smith.name and jane.smith.name, neither can fully control the second-level namespace smith.name. That does not fit neatly with today’s standard model, where one registrant controls a second-level domain and everything beneath it.

Operationally, retiring the exception makes sense. For users whose identities depend on it, that is cold comfort.

You Never Really Own a Domain

People talk about buying domains. In practice, they register the right to use them for a limited period under rules set by registrars, registries, and ICANN.

It is less like buying land and more like renewing a personalized license plate. Keep paying, and you can usually keep using it. Usually is doing a lot of work.

A registry agreement or policy change can end future renewals even when the registrant has broken no rules. The contract may allow it, but contracts do not capture what a domain becomes after two decades.

A longtime address can connect business cards, personal sites, search results, email archives, and online accounts. It is infrastructure for a digital identity, not merely another subscription.

A long runway helps, but time alone is not a migration plan. ICANN and Verisign should provide clear, repeated notices and practical guidance for moving web and email services. They should also explain exactly what happens to retired addresses, including whether anyone could ever register the same or a confusingly similar name.

The Quiet Shutdown Is the Risk

The decision has barely surfaced in the usual online venues where infrastructure changes spark debate. There is little sign of widespread outrage on Hacker News, Reddit, or X.

That silence may reflect the real problem: many affected users probably do not know the shutdown is happening.

Longtime domain owners often enable automatic renewal and stop reading registry notices. Everything works until it does not. By then, the consequences extend well beyond a missing homepage.

Password-reset emails may never arrive. Old contact details may stop working. Links preserved in articles, résumés, forum posts, and public records will begin returning errors.

The post-expiration policy matters as much as the shutdown itself. If a third party can later claim an identical or similar address, the result could be impersonation, intercepted correspondence, or account takeover. Permanent retirement would reduce that risk, but users need an explicit answer rather than an assumption.

Start With Email, Not the Website

Anyone using an affected .name address should begin by mapping their email dependencies. Update usernames and recovery addresses for financial services, retailers, social networks, cloud platforms, and password managers.

Next, register a conventional second-level domain that you control. Publish a migration notice on the old website and keep redirects running for as long as possible. Remember that every redirect dies when the original domain does.

Run both email addresses in parallel. Notify important contacts, then update profiles, documents, and business cards in stages. If you operate your own mail server, rebuild SPF, DKIM, and DMARC records for the new domain rather than assuming the old configuration will follow you.

The important number is not 22,000. It is the number of pieces of your life attached to an address that ultimately exists at someone else’s discretion.

2040 sounds distant. Migrating a digital identity rarely is.