An 882-point Hacker News surge around one developer's scheduled-for-deletion address exposed a policy gap far larger than neil.fraser.name. ICANN has authorized Verisign to delete approximately 22,000 registered third-level .name domains. ICANN's own accountability committee says migration costs, loss of internet identity, and questions about refunds sit outside the review that approved the change. For anyone who treats a domain as a durable account anchor, that boundary matters more than .name's small user base. ICANN's authorization letter records both the count and the limited scope of its review.
The .name top-level domain is staying online. The approved change targets a registration service created for addresses in the form firstname.lastname.name, along with a related email-forwarding service considered in a separate request. New registrations will stop and existing ones will be deleted after registrars receive at least 90 days' notice. That means a valid, paid registration can end before the date its owner expected, even while ordinary second-level .name domains continue to work. Verisign's April 15 request states that outcome directly.
How registered third-level .name worked
The third level is easy to misread as a subdomain controlled by whoever owns the second level. That was not how this part of .name worked. A customer could register neil.fraser.name through a registrar, and the registry processed it as a registered item with its own record. Verisign's filing says third-level registrations began under the original 2001 agreement between ICANN and Global Name Registry. The filing also says the registry will stop accepting the relevant EPP transactions and delete existing registrations when the service ends. The RSEP request describes both the old model and the deletion mechanism.
Software engineer Neil Fraser says he registered neil.fraser.name nearly 25 years ago and uses it for his website, email, and API hosting. He also registered beverly.fraser.name shortly after his daughter's birth. His registrar told him the service would end in February, despite his registration being paid through 2040. His account documents one registrant's notice and dependencies. ICANN's own records establish the approval and the total affected count. Fraser's September 3 post supplies those personal details.
Verisign gave two reasons for retiring the service: declining use and limited support among registrars. It said removal would make the .name registry more efficient. The same filing answered that the change would have no effect on the life cycle of domain names, no effect on competition, and no effect on the domain market, even though it also said existing third-level registrations would be deleted. Those answers became the center of a formal challenge. Verisign's submitted questionnaire puts the claims side by side.
What ICANN knew before filing
Verisign and ICANN met on October 15, November 4, and December 16, 2025, before the request was filed. ICANN later said those consultations covered the termination of approximately 22,000 third-level registrations and Verisign's view that most were unused. The figure refers to registrations, so it should not be translated automatically into 22,000 individual people. The Board Accountability Mechanisms Committee's August 24 recommendation lays out that pre-filing record.
The public process then moved quickly. Verisign submitted its request on April 15. ICANN approved it on May 7 and posted the approval on May 8. On July 28, ICANN issued a "free to deploy" letter allowing Verisign to proceed. The conditions listed in that letter are operational: registrars get at least 90 days' notice, a reminder at least 30 days before shutdown, and customer-service support from Verisign. The letter does not set the final deletion date or promise that registrations will run to their paid expiration dates. ICANN's July 28 letter records the dates and notice requirements.
Verisign reported that it had consulted a selected group of registrars managing a majority of the user base, and that none identified security, stability, or competition concerns. The public filing does not describe direct consultation with registrants. ICANN's letter says registrars manage the registrar-customer relationship, which helps explain why Fraser learned through his registrar rather than from the registry or ICANN. It also leaves long-time users dependent on how each registrar handles notice and migration. The request and approval letter describe that chain of communication.
Why the security review did not stop it
Doytchin Spiridonov, who said he held three affected registrations, filed Reconsideration Request 26-2 on June 2. He asked ICANN to suspend the approvals, disclose more of the analysis, open public comment, and require grandfathering through paid terms or an equivalent remedy. The ICANN Ombuds recommended denial. On August 24, the Board Accountability Mechanisms Committee also recommended that the full Board deny the request. The committee's recommendation is the latest decision document linked on ICANN's case page.
The committee drew a narrow process boundary. Under the Registry Services Evaluation Policy, ICANN reviews whether a requested registry change could raise significant security, stability, or competition issues. The committee said costs of moving services, operational disruption, continuity of identity, and possible refunds mattered to registrants but fell outside that test. It added that refunds, credits, grandfathering, and compensation depend on contracts between registrars and customers, contracts to which ICANN is not a party. The 16-page recommendation states that division explicitly.
The disputed life-cycle answer survived for a similarly technical reason. Spiridonov argued that deleting a registered name plainly changes its life cycle. The committee replied that early termination does not alter the standard stages a domain can pass through before closing. It also found that ICANN already knew deletion was the intended result, so Verisign's "no effect" answer did not cause the approval team to miss the relevant fact. The committee's analysis separates awareness of the deletions from the policy's definition of a life-cycle effect.
Public comment was absent by design. The committee says an RSEP approval does not require a comment period when ICANN finds no apparent significant security, stability, or competition issue. ICANN's July letter goes further: its assessment does not extend to other possible effects of removing a registry service. The result is a process that can account for thousands of forced migrations while leaving the user-facing consequences to registrars and their separate customer agreements. ICANN's letter explains that its review was confined to the RSEP tests.
What happens to fraser.name?
If the second-level label fraser.name later becomes available to another buyer, that buyer could recreate neil.fraser.name, receive traffic sent there, and present addresses that look like Fraser's old identity. He says that could threaten accounts tied to his email, code attributed through that address, and devices that call services on the domain. This is Fraser's risk assessment. His post says the release of those second-level names is assumed, while Verisign's request is silent about their eventual availability.
That distinction affects how owners should plan. The approved deletion alone is enough to break websites, inbound mail, API clients, certificate renewal, and devices that depend on an affected name. A later release of the parent label would add an impersonation risk, but the published documents do not establish that release as part of the plan. Owners therefore need answers from their registrars on two separate questions: when service ends, and whether the corresponding second-level label will stay reserved. Fraser's inventory of his own dependencies and Verisign's deletion plan establish the known failure points and the remaining gap.
A migration also reaches beyond DNS records. Fraser says there is no complete way to enumerate every online and offline account opened with his email over a quarter century. An affected owner can search code, configuration, password-manager entries, mail archives, account recovery settings, signing identities, and hard-coded device endpoints, yet old records and dormant accounts may remain. That is the practical cost hidden by a count in which most registrations are described as unused. An inactive website can still have an active email identity behind it. Fraser's account explains why his registration still carries dependencies even after 25 years.
The next decisive document should come from the ICANN Board, because the August 24 committee paper is a recommendation to deny reconsideration rather than the Board's final determination. Registrants also need Verisign or their registrars to publish the exact cutoff date, treatment of prepaid terms, and fate of the matching second-level labels. Until then, owners have to plan against the published status: deletion is authorized, the notice window can be as short as 90 days, and the pending accountability challenge has not suspended the plan. ICANN's authorization and the committee recommendation define that current position.