.did
Is .did a real TLD? Who’s applying to run it?
.did is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 8 October 2026. They are Verse International and Starlight (Namecheap).
A niche bet on decentralized identity; most of its target community names things outside DNS, so demand stays small and specialist.
decentralized-identity and web3 identity projects (wallets, credential platforms, DID-method teams), plus a smaller tail of word-hack buyers using "did" as the English verb
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 in shape: take a lowercase internet-standards acronym that only insiders can parse and turn it into an addressable namespace, wagering that the standard itself becomes mainstream enough that its abbreviation reads as a category to ordinary buyers.
Both bet that a new addressing/identifier scheme outside the ordinary web-page model can bootstrap adoption by owning a TLD as its entry point, so the registry's fate is tied to the protocol's uptake rather than to demand for the word.
Both are the bet that a universal identifier system for entities can be turned into a name people register and publish as their canonical handle, though DUNS is a single proprietor's number scheme while a DID namespace would be an open multi-method one.
What a .did domain is
.did is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Crypto. 2 applications for it are on ICANN’s Reveal Day list.
Is the .did domain extension real yet?
.did 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 .did domain?
You can’t yet. A .did name can only be registered once the string is delegated (added to the DNS root) and its registry opens.
Is .did a real TLD?
Not yet. .did is not in the DNS root, so nothing resolves under it. It’s here because .did is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Starlight (Namecheap) · noteDomain Name Wire
- Verse International · first recordedICANN
- Starlight (Namecheap) · first recordedICANN
“CEI2644T-T88328 · Canopus Exploration, Inc. · primary · contention set 2026-66 VIL2659T-T55269 · Verse International Limited · primary · contention set 2026-66”ICANN
“For us, moving into the registry side is a natural extension of what we have been building.”Domain Name Wire
- "DID" reads directly as Decentralized Identifier, the W3C identity standard, which gives the string a genuine semantic hook into the web3/identity sector; counts of active DID projects are unknown. The complication is that the DID ecosystem natively uses did: URI schemes rather than DNS, so the most obvious users may not need domains at all — by analogy with how crypto-native naming (ENS-style systems) grew outside ICANN TLDs rather than inside them. Analogous niche tech-term TLDs suggest steady but modest registration volume driven by retail pricing rather than premium brand demand, and a thin aftermarket outside a handful of exact-match identity keywords. The applicant is Starlight Registry, a registry venture established by Namecheap, one of the largest domain registrars, which applied for 40 strings in the 2026 round; large-registrar distribution plausibly lifts baseline registration volume, supporting the low 30s band. I place it at 31: above the vanity band because the identity-tech niche and word-play tail are real and durable, but below the strong-niche band because there is no sign the sector treats DNS names as primary identity, and adoption would need explaining everywhere. Main market uncertainty: whether decentralized-identity platforms adopt DNS-anchored handles at all, or keep naming entirely inside did: URI methods.