Verisign’s decision to remove 22,000 third-level .name domains has triggered a wave of opposition from registrants who claim the move amounts to domain seizure for commercial resale. The registry, which operates the .name top-level domain (TLD), received approval from ICANN to proceed with the deletions, arguing most affected domains were unused and posed no security risks. Registrants, however, dispute this characterization, with some alleging the plan will expose them to identity theft and disrupt decades-old online identities.
What happened
Verisign notified registrars in late August that it would delete approximately 22,000 third-level .name domains—structured as firstname.lastname.name—as part of a push to standardize the TLD around conventional two-level domains (e.g., lastname.name). The registry stated the change would simplify technical operations for itself and registrars. Under the current structure, registrants own only the third-level domain, while Verisign retains control of the second-level (lastname.name). The deletions would free these second-level domains for future registration, potentially as early as February 2027.
Registrants, many of whom have held their domains for over 20 years, were caught off guard by the decision. Software developer Neil Fraser, representing himself and nine others, warned ICANN that deleting the domains could enable new registrants to impersonate the original owners by recreating their email addresses. "They would have access to banking, government, taxes, and other services," Fraser wrote, noting the impossibility of updating every account tied to an email address used for 25 years. Another affected registrant, lawyer Troy Rollo, described the difficulty of changing email addresses linked to accounts established since 2002, calling the process "nigh-on impossible."
Background: The .name TLD launched in 2001 with a unique structure allowing registrants to claim third-level domains (e.g., firstname.lastname.name) while the registry retained ownership of the second-level (lastname.name). This model was designed to prevent name squatting but created technical and administrative complexities as the domain industry standardized around two-level domains.
Legal and regulatory pushback
ICANN has received four Requests for Reconsideration (RfRs) from affected registrants, including two filed in the past week. The filings argue that ICANN should reverse its approval of Verisign’s plan or at least grandfather existing registrants to prevent disruptions. Historically, ICANN’s RfR process has a low success rate, and neither ICANN nor its Ombuds has indicated willingness to intervene. The final decision now rests with ICANN’s board of directors, though no timeline has been provided.
Fraser, in a public statement, suggested legal action may be inevitable. "I’m just one of 22,000 people who will lose their domains," he wrote. "This is going to be fun. Time to lawyer up…" Verisign has not publicly responded to the backlash beyond its initial justification for the deletions.
Why it matters
The dispute highlights tensions between registry operators seeking to modernize legacy TLD structures and registrants who rely on long-standing domain configurations. For .name users, the deletions could force costly migrations or risk losing access to critical online services. The case also raises broader questions about ICANN’s role in approving registry policy changes that may disproportionately affect small groups of registrants, even when the changes align with industry standards.
For professionals: Registrars with .name customers should proactively notify affected registrants and prepare for potential support requests related to domain migration or email updates. Legal teams may need to monitor ICANN’s board decision for precedents on registry policy disputes.
What to watch
The outcome of the RfRs will signal how ICANN balances registry flexibility with registrant protections. If the board upholds Verisign’s plan, similar disputes could arise in other legacy TLDs with non-standard structures. Conversely, a reversal might encourage more registrants to challenge registry decisions through formal channels, increasing operational uncertainty for TLD operators.
Automated pipeline · Domains
Synthesized from 1 industry feed on 22 Sep 2026. Passed independent editor verification (score 95/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — Deduped batch of 1 candidates
- Checking for duplicates — New story No previously published or in-pipeline article covers Verisign's .name domain deletion plan.
- Checking for duplicates — New story pre_write:; No previously published or in-pipeline article covers Verisign's .name domain deletion plan.
- Writing the article — Draft created article_id=583 slug=verisign-to-delete-22-000-name-domains-amid-backlash
-
Editor review — Approved
- Score: 95/100
- Factual grounding: The draft states '.name TLD launched in 2001' in the Background block, but the source states 'when it launched 25 years ago' (relative to 2026). This implies a launch year of 2001, which is correct, but the phrasing in the draft should clarify the launch year is derived from the source's relative term. No material issue, but the exact year should be traceable to the source's relative date.
- Style compliance: The standfirst uses the term 'seizing domains for resale,' which is a paraphrase of the source's 'accusing the company of trying to steal their domains to auction off to the highest bidder.' While not a direct quote, the phrasing is close to the source's wording. The draft should avoid echoing the source's distinctive phrasing ('steal their domains to auction off').
- Style compliance: The draft includes a Background block, which is allowed, but the content closely mirrors the source's explanation of the .name TLD structure. The draft should restructure the idea further to avoid paraphrasing the source's wording too closely.
- Generating reader Q&A — Generated 5 items
- Assigning hero image — Rejected library image #198: The candidate depicts a generic corporate office building with no relevance to domain registries, TLDs, or the .name domain deletion issue. The alt text and context do not match the article topic.
- Assigning hero image — Rejected library image #152: No candidate matches the article topic (Verisign deleting .name domains, registries/TLDs, or related controversies). The provided candidate depicts domain registration growth, which is unrelated to the article's focus on domain deletions, backlash, or Verisign's actions.
- Assigning hero image — Rejected library image #405: The candidate depicts legal documents and a gavel, which is too generic for the article about Verisign deleting .name domains and the associated controversy. It does not directly relate to domain registries, TLDs, or the specific issue of domain deletion.
- Assigning hero image — Rejected library image #55: No candidate matches the article topic (Verisign deleting .name domains, TLD registry operations, or domain-related issues). The provided candidate depicts an email security warning unrelated to domain registries or TLDs.
- Assigning hero image — Rejected library image #140: The candidate depicts the GoDaddy headquarters exterior, which is unrelated to the article topic about Verisign's deletion of .name domains. The alt text is incorrect (mentions GoDaddy instead of ICANN), and the image does not illustrate domain registries, TLDs, or the specific issue described in the article.
- Assigning hero image — Reused library image unsplash_id=_Jb1TF3kvsA q=domain registration dashboard on computer screen picker=The article is about domain registries and the deletion of .name domains, making a domain registration dashboard on a co
- Linking related stories — Linked 3 relations from 323 candidates
- Publishing — Published verisign-to-delete-22-000-name-domains-amid-backlash
- Mastodon — Posted https://mstdn.social/@hostingpaper/117314786548835378




Discussion · coming soon
Be the first to join the thread when community discussion launches.