The .name top-level domain (TLD) will no longer support new third-level domain registrations after a policy change approved by ICANN. The decision, formalized in a registry request submitted on 15 April 2026, targets the discontinuation of formats such as john.smith.name while allowing existing second-level registrations like smith.name to continue unchanged. No timeline for the phase-out has been specified beyond the policy’s approval date in August 2026, leaving operators and registrants uncertain about enforcement deadlines or grandfathering provisions for active third-level domains.
What happened
ICANN’s Registry Services Evaluation Process (RSEP) approved a request from the .name registry to eliminate third-level domain registrations. The policy does not affect second-level domains under .name, which will remain available for registration and renewal. The request was filed in mid-April 2026, and ICANN’s approval was documented in a consensus policy published on 31 August 2026. No public announcement has clarified whether existing third-level domains will be forcibly deleted, migrated, or allowed to expire naturally.
What we don’t know yet
Sources do not specify when the policy will take effect or how it will be enforced. There is no information on whether registrars will receive advance notice, what grandfathering measures—if any—will apply to active third-level domains, or whether registrants will be offered migration paths to second-level equivalents. The registry has not disclosed whether the change is driven by technical constraints, declining usage, or cost considerations. Operators relying on third-level .name domains should monitor ICANN and registry communications for updates on implementation timelines and transition policies.
Companies mentioned
Automated pipeline · Domains
Synthesized from 1 industry feed on 3 Sep 2026. Passed independent editor verification (score 85/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — Deduped batch of 1 candidates
- Checking for duplicates — New story No recent or in-pipeline article covers the discontinuation of third-level domain registrations for the .name TLD.
- Checking for duplicates — New story pre_write:; No recent or in-pipeline article covers ICANN's discontinuation of third-level domain registrations for the .name TLD.
- Writing the article — Brief only thin sources; quick-read mode
- Writing the article — Draft created article_id=499 slug=name-tld-to-end-third-level-domain-registrations quick_read=1
-
Editor review — Approved
- Score: 85/100
- Factual grounding: The draft states the policy was 'approved in August 2026' and cites a 'consensus policy published on 31 August 2026'. The source publication date is 31 August 2026, but the source (PDF) does not explicitly state the approval date as 31 August 2026. The PDF filename and text reference the request date (15 April 2026) but do not confirm the approval date. The draft should clarify that the approval was documented on 31 August 2026 (source publication date) rather than stating it as a confirmed approval date.
- Style compliance: The standfirst includes the year '2026' explicitly ('after 2026'), but the body does not specify whether this is the cutoff year or a general reference. The sources do not confirm 2026 as the sunset year for third-level registrations, only the policy approval timeline. The standfirst should avoid implying a specific year unless confirmed by sources.
- No copied phrasing: The phrase 'Registry Services Evaluation Process (RSEP)' appears verbatim in the draft and is likely sourced from the PDF. While this is a technical term, the draft should paraphrase or reword the explanation to avoid direct echoing of source phrasing.
- Generating reader Q&A — Generated 3 items
- Assigning hero image — Reused library image reused image #152
- Linking related stories — Linked 5 relations from 432 candidates
- Publishing — Published name-tld-to-end-third-level-domain-registrations
- Mastodon — Posted https://mstdn.social/@hostingpaper/117204843310566799




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