.anon
Is .anon a real TLD? Who’s applying to run it?
.anon is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Link Freedom Group. Starlight (Namecheap) named .anon as a backup string for two of its applications: .did and .clone. ICANN deactivated those backups, because another applicant applied for the same string or named it as a backup.
A catchy privacy-culture name for crypto anons and privacy tools, but too niche and trust-conflicted to become a serious default.
pseudonymous builders and creators in crypto culture, plus privacy tools, VPN-style services, and anonymity-themed communities wanting an identity that signals privacy
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Privacy is your superpower.”
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .clone application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .did application, shown as deactivated: another applicant applied for the same string or named it as a backup
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: an unowned abstract assurance word sold as the primary identity for any operator whose whole pitch is the attribute itself, which only works if the promise in the string is credible enough that registrants accept being judged by it.
Same shape of bet — a short, adjectival trust-attribute word rather than an industry or product noun — but it addresses a mass reassurance audience where .anon addresses a self-selecting one that actively wants to be unidentified.
Shares the clipped-insider-vocabulary character of a privacy/security tribe naming itself in its own shorthand, but it is narrow professional jargon aimed at B2B practitioners rather than a consumer-and-culture word anyone can claim.
What a .anon domain is
.anon is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Culture category. One application for it is on ICANN’s Reveal Day list.
Is the .anon domain extension real yet?
.anon is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .anon domain?
You can’t yet. A .anon name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .anon was .secure, delegated on 10 August 2016.
Is .anon a real TLD?
Not yet. .anon is not in the DNS root, so nothing resolves under it. It’s here because .anon is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Starlight (Namecheap) · first recordedICANN
- Starlight (Namecheap) · first recordedICANN
- Link Freedom Group · now confirmedICANN
- Link Freedom Group · first recordedLink Freedom Group
“LFGL2683T-T74111 · Link Freedom Group Ltd · primary”ICANN
“AEI2676T-T59914 · Aldebaran Exploration, Inc. · replacement string of .clone · Deactivated CEI2644T-T88328 · Canopus Exploration, Inc. · replacement string of .did · Deactivated LFGL2683T-T74111 · Link Freedom Group Ltd · primary”ICANN
“.anon · Culture · “Privacy is your superpower.””Link Freedom Group
- Band: usable but limited (30-49), at its low end. The string has genuine cultural resonance: 'anon' is an identity word in crypto and pseudonymous internet culture, and it is short, pronounceable, and self-explanatory, which lifts it above the vanity/joke band (10-29) where strings have only event-driven novelty. It does not reach the strong-niche band (50-69) because there is no evidence of sustained demand, and the concept carries a structural tension: buyers who care most about anonymity tend to distrust conventional registry namespaces, where registrant-data and takedown regimes sit at odds with the 'anon' promise, so the best-fit buyer may rationally prefer other infrastructure for their primary identity. Applicant status is announced only (unknown pricing, unknown registry policies), so adoption reasoning is by analogy: privacy- and edge-culture strings in prior rounds have tended toward volume-on-price registrations and meme use rather than durable primary identities, and I infer, by analogy, that .anon skews the same way, with a thin aftermarket concentrated in a handful of dictionary-word and crypto-culture names. Main market uncertainty: whether crypto-native pseudonymous identity demand converges on a DNS TLD at all, versus staying on platform handles and non-DNS naming systems.