.dns
Is .dns a real TLD? Who’s applying to run it?
.dns is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are Suffix Inc. and Nepal Internet Foundation.
A technical label for DNS and hosting providers; useful for a few product endpoints, but rarely a company's main web address.
dns, hosting and network-security vendors, registrars and infrastructure tooling teams who want a self-describing address for a resolver, nameserver or dns-management product
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 as .dns: a lowercase technical acronym drawn from the naming-infrastructure vocabulary itself, owned by no company, whose value depends entirely on a technical/registry-adjacent audience accepting an initialism as a credible namespace rather than on any consumer recognition.
Also a generic internet-plumbing term that infrastructure providers would put their primary identity on, and it works only if the operator can look like neutral stewardship of shared infrastructure instead of one vendor fencing off the industry's own word — but it is a plain-language word with mass recognition, where .dns is an insider acronym.
The same shape of bet one layer up the stack: an unowned category noun for an internet-infrastructure service, bought by the providers who sell that service and dependent on registrars and hosts wanting an obviously-descriptive technical address.
What a .dns domain is
.dns is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Infrastructure. 2 applications for it are on ICANN’s Reveal Day list.
Is the .dns domain extension real yet?
.dns 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 .dns domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .dns name can only be registered after that, once the string is delegated and its registry opens.
Is .dns a real TLD?
Not yet. .dns is not in the DNS root, so nothing resolves under it. It’s here because .dns is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“NIF2590-T63192 · Nepal Internet Foundation · primary · contention set 2026-68 SI2639T-T82042 · Suffix Inc. · primary · contention set 2026-68”ICANN
“LFGL2683T-T12771 · Link Freedom Group Ltd · primary SI2639T-T84933 · Suffix Inc. · replacement string of .rep · Deactivated”ICANN
“Catalog lists: .asap .create .future .lfg .mvp .out .pal .planet .research .share .tag .this .visit”Suffix Inc.
- Band chosen: 30-49 (usable but limited), at its floor. The string names a real, persistent professional sub-sector (DNS resolvers, managed DNS, registrars, network security), so demand is steady and buyer-driven rather than joke- or event-driven, which keeps it out of the 10-29 band. It stays out of 50-69 because the natural buyers already hold established brands on legacy TLDs and would treat a .dns address as a product endpoint or defensive registration rather than a primary identity; adoption needs explaining to anyone outside infrastructure, and the aftermarket would be thin. By analogy (flagged as analogy), industry-descriptor TLDs such as .domains, .host and .hosting drew modest volume dominated by in-industry and defensive registrations with weak resale value, while .cloud did better mainly because 'cloud' became a broad marketing term; 'dns' is narrower and more technical than any of those. The record shows two confirmed applicants in a single contention set and no category tag; applicant facts are stated neutrally and do not change the market read. Main market uncertainty: whether any large DNS/CDN operators or registrars adopt .dns addresses as primary product identities (which would pull the score toward the 40s) versus only parking defensive registrations, and whether the eventual registry prices it as a low-volume premium namespace or a mass-market one.