.name Domains: Third-Level Addresses to Be Expunged Next Year

The End of an Era for Third-Level .name Domains

If you're still holding onto a third-level .name domain—like john.smith.name—it's time to face an uncomfortable reality: your address will be permanently expunged next year. A recent Hacker News thread, started by user nikanj, has brought this impending doom to the community's attention, sparking a mix of frustration, confusion, and practical advice.

The news, first reported by DomainNameWire, confirms that Verisign, the registry operator for .name, is discontinuing third-level registrations. This means that the unique structure that allowed individuals to register firstname.lastname.name as a standalone domain will cease to exist. For those who have built their personal brand or email infrastructure on this niche TLD, the countdown has begun.

Why Verisign Is Pulling the Plug

The official reasoning from Verisign remains thin, but the Hacker News community has its own theory. As nikanj bluntly puts it: “By kicking old nerds off legacy.domain.name, they can relist domain.name on the open market and make an absolute killing.” This sentiment resonates with many who see the move as a purely commercial decision to reclaim and resell premium second-level domains.

Verisign's decision isn't just about cleaning up an outdated namespace. Third-level .name domains were a creative experiment in the early 2000s, offering a more personal and structured approach to online identity. However, as the internet has consolidated around a few dominant TLDs, the .name registry has become a liability rather than an asset. By expunging third-level domains, Verisign can simplify its operations and potentially monetize the now-vacated second-level names, many of which are desirable short, common words.

The Human Cost: Email and Identity at Risk

For many, the impact goes beyond a simple URL change. Email addresses tied to third-level .name domains are a lifeline for personal and professional communication. The original poster shares a harrowing tale of being locked in a Microsoft Azure admin account with an email address that cannot be changed. “Support is both uncaring and powerless,” they lament, highlighting a real-world consequence that goes beyond mere inconvenience.

This is a stark reminder that domain names are not just addresses; they are often the keys to our digital identities. When a registry decides to revoke a namespace, it can cascade into locked accounts, lost credentials, and inaccessible services. The lack of a clear migration path from Verisign exacerbates the problem, leaving users to fend for themselves in a frantic race against time.

Community Reactions: Frustration and Pragmatism

The Hacker News thread reveals a split in the community. Some see the move as inevitable and even logical, given the changing landscape of domain names. One commenter notes, “There's no strict need to do it, let alone to do it now, but an eventual transition does make sense, if spread out over a couple of years with guaranteed backwards compatibility.” This perspective acknowledges the commercial reality while criticizing the abruptness of the change.

Others are less forgiving, lamenting the loss of creativity in the domain space. “Shame that there's no room in the world for some creativity and we need to normalize the space of all TLDs into the same uncreative .com clone,” writes another user. This sentiment captures the broader trend of the internet's homogenization, where unique and quirky TLDs are sacrificed for uniformity and profit.

Technical Implications and Migration Strategies

For those affected, the immediate question is: What now? The most straightforward solution is to migrate to a standard TLD like .com or .net. However, this is easier said than done, especially for those who have used their domain for email and other services.

One technical nuance highlighted in the discussion is the unique registration model of .name. Unlike other TLDs, where you register a second-level domain and create subdomains, .name allowed direct registration of third-level domains. This meant that john.smith.name and dave.smith.name could be entirely separate registrations, each with its own control panel. This feature made .name particularly attractive for families or small groups sharing a surname.

Unfortunately, this model is now being retired. For those on shared second-level domains, the suggestion is to transition to an intermediary that can privately manage third-level registrations and email forwarding. As one commenter suggests, “You could transition to an intermediary as the registrant of the second level domain and privately providing third level registration and email forwarding.” While this is a viable workaround, it lacks the durability and trust of a registry-backed solution.

What You Should Do Now

If you are one of the affected users, don't wait until the last minute. Start by auditing your current domain and email setups. Identify all services that rely on your third-level .name address, from email to social media logins to cloud services.

Next, consider your migration path. If you're moving to a new domain, prioritize setting up email forwarding and updating your accounts. For critical services like Azure, contact support early to see if they can assist with email changes, though as the original poster discovered, this may be a dead end.

Finally, keep an eye on Verisign's official communications. While the expungement is scheduled for next year, there may be additional details or support options announced in the coming months. In the meantime, the community is your best resource for tips and workarounds.

The Bigger Picture: A Cautionary Tale

The .name expungement is a cautionary tale about the fragility of digital ownership. In an era where our online presence is intertwined with our professional and personal lives, the decisions of a single registry can have far-reaching consequences. It underscores the importance of diversifying your digital footprint and not becoming overly reliant on any single TLD or provider.

As the internet continues to evolve, we can expect more such consolidations and retirements. The .name situation is a reminder that what seems permanent today can be gone tomorrow. For now, the advice from the Hacker News community is clear: migrate early, migrate thoroughly, and don't look back.