Verisign to Purge 22,000 Third-Level .name Domains After ICANN Approval.

Verisign to Terminate Third-Level .name Domains, Triggering Security and Digital Identity Concerns

Verisign, the registry operator for the .name top-level domain (TLD), has received regulatory approval from ICANN (Internet Corporation for Assigned Names and Numbers) to completely discontinue its legacy third-level domain registration service.

When .name launched in 2002, it featured a unique personal naming structure in a [first].[last].name format (such as john.doe.name). Unlike conventional web domains where subdomains are free add-ons controlled by a single registrant, .name allowed individual users to separately register and own distinct third-level addresses under shared surname domains. Under Verisign’s shutdown plan, all active third-level registrations will be permanently deleted from the global Domain Name System (DNS).

ICANN Approval and Verisign’s Rationale

Verisign formally requested the termination through ICANN's Registry Services Evaluation Policy framework, pointing to shrinking adoption and administrative overhead:

• Declining Registrations: Verisign reported that only about 22,000 active third-level .name registrations remain globally, with a vast majority sitting parked or unused.

• Regulatory Clearance: ICANN approved the removal of third-level domain support in May, concluding that ending the legacy service presents no operational risks to overall Internet stability.

• Forced Deletion: Following required registrar notices, all third-level .name domain records will be systematically purged from the registry database.

Developer Backlash and Security Exposure

The planned shutdown has drawn sharp criticism from long-time users who relied on the platform as a permanent personal identity system. Neil Fraser, a software engineer who registered neil.fraser.name in 2002 and later set up corresponding domains for his family, publicly voiced outrage over the decision.

Beyond breaking active websites and primary email addresses established over two decades, Fraser highlighted severe security vulnerabilities created by the purge:

• Impersonation Risks: Deleting third-level subdomains allows anyone to register the liberated second-level domain (e.g., fraser.name).

• Account Hijacking Threat: A bad actor securing fraser.name could easily create wildcard email aliases to intercept sensitive messages, initiate password resets across banking or developer platforms, and impersonate any former owner of a third-level domain sharing that surname.

Domain discontinuation undermines fundamental authentication assumptions. Security frameworks rely on the premise that an email address linked to a user remains permanently under that user's control. Unilateral deletion of a multi-tenant subdomain shatters this boundary, enabling third parties to acquire the second-level domain and intercept authentication traffic originally intended for the legitimate owner.

The original shared-namespace model of .name was conceived during an era of domain scarcity, aiming to provide individuals with clean, personalized URLs. However, as second-level domain registration expanded and email security standards (such as SPF, DKIM, and DMARC) became more stringent, managing multiple independent owners under a single second-level domain created technical complexities that ultimately led to the model's collapse.

Relying on niche Top-Level Domains (TLDs) for long-term digital identity creation entails a significant dependency on the domain registrar. If a niche domain model ceases to be commercially viable, users risk losing their prepaid assets and long-standing digital footprints—entirely at the discretion of the registrar.

Source: Neil Fraser 

💬 AI Content Assistant

Ask me anything about this article. No data is stored for your question.

Verisign to Terminate Third-Level .name Domains, Triggering Security and Digital Identity Concerns

Verisign, the registry operator for the .name top-level domain (TLD), has received regulatory approval from ICANN (Internet Corporation for Assigned Names and Numbers) to completely discontinue its legacy third-level domain registration service.

When .name launched in 2002, it featured a unique personal naming structure in a [first].[last].name format (such as john.doe.name). Unlike conventional web domains where subdomains are free add-ons controlled by a single registrant, .name allowed individual users to separately register and own distinct third-level addresses under shared surname domains. Under Verisign’s shutdown plan, all active third-level registrations will be permanently deleted from the global Domain Name System (DNS).

ICANN Approval and Verisign’s Rationale

Verisign formally requested the termination through ICANN's Registry Services Evaluation Policy framework, pointing to shrinking adoption and administrative overhead:

• Declining Registrations: Verisign reported that only about 22,000 active third-level .name registrations remain globally, with a vast majority sitting parked or unused.

• Regulatory Clearance: ICANN approved the removal of third-level domain support in May, concluding that ending the legacy service presents no operational risks to overall Internet stability.

• Forced Deletion: Following required registrar notices, all third-level .name domain records will be systematically purged from the registry database.

Developer Backlash and Security Exposure

The planned shutdown has drawn sharp criticism from long-time users who relied on the platform as a permanent personal identity system. Neil Fraser, a software engineer who registered neil.fraser.name in 2002 and later set up corresponding domains for his family, publicly voiced outrage over the decision.

Beyond breaking active websites and primary email addresses established over two decades, Fraser highlighted severe security vulnerabilities created by the purge:

• Impersonation Risks: Deleting third-level subdomains allows anyone to register the liberated second-level domain (e.g., fraser.name).

• Account Hijacking Threat: A bad actor securing fraser.name could easily create wildcard email aliases to intercept sensitive messages, initiate password resets across banking or developer platforms, and impersonate any former owner of a third-level domain sharing that surname.

Domain discontinuation undermines fundamental authentication assumptions. Security frameworks rely on the premise that an email address linked to a user remains permanently under that user's control. Unilateral deletion of a multi-tenant subdomain shatters this boundary, enabling third parties to acquire the second-level domain and intercept authentication traffic originally intended for the legitimate owner.

The original shared-namespace model of .name was conceived during an era of domain scarcity, aiming to provide individuals with clean, personalized URLs. However, as second-level domain registration expanded and email security standards (such as SPF, DKIM, and DMARC) became more stringent, managing multiple independent owners under a single second-level domain created technical complexities that ultimately led to the model's collapse.

Relying on niche Top-Level Domains (TLDs) for long-term digital identity creation entails a significant dependency on the domain registrar. If a niche domain model ceases to be commercially viable, users risk losing their prepaid assets and long-standing digital footprints—entirely at the discretion of the registrar.

Source: Neil Fraser