.nas
Is .nas a real TLD? Who’s applying to run it?
Nobody has applied for .nas in its own right, as of 7 October 2026. OPEN DEVELOPMENT CAMBODIA named .nas as the replacement string of its .api application.
A short, ambiguous three-letter ending with no obvious meaning to most buyers; a curiosity, not a serious web address.
network-storage vendors and homelab hobbyists who read "nas" as network-attached storage, plus a thin tail of brands and acronyms that happen to spell NAS
No applications recorded for this TLD yet.
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 form and buyer: a three-letter acronym for a consumer/prosumer hardware device class that only means anything to people who already know the expansion, sold to device makers and the service layer around them rather than to a general public.
The plain-language category noun for exactly the job NAS does, chasing the same vendor-and-service buyer set, but betting on a word everyone understands instead of an insider acronym.
Also an infrastructure-category string aimed at storage and hosting providers putting primary identity on where data lives, but it is a mass-market generic for the remote model rather than a niche term for the box on your own network.
What a .nas domain is
.nas is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .nas in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .nas domain extension real yet?
.nas is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .nas domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .nas name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .nas was .dvr, delegated on 30 September 2016.
Is .nas a real TLD?
Not yet. .nas is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .nas as part of an application for another string. Every entry on this page links to its source.
- OPEN DEVELOPMENT CAMBODIA · first recordedICANN
“ODC2534-T66083 · OPEN DEVELOPMENT CAMBODIA · replacement string of .api”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows .nas as a replacement string for a .api application by OPEN DEVELOPMENT CAMBODIA under the Applicant Support Program, with no category tag recorded and zero contention; the intended meaning of the string is unknown from the facts. In market, the string's strongest reading is network-attached storage, a real but small hardware/software niche whose vendors and enthusiasts already identify under their own brands or on .com/.io; a secondary tail of acronym holders (organizations and names abbreviating to NAS) would register defensively or as vanity at best. By analogy (flagged as analogy), narrow tech-term TLDs from the 2012 round such as .storage-adjacent or hosting-themed strings like .host and .cloud show that even broad infrastructure words struggle to become primary identities, and a three-letter acronym with multiple competing meanings is weaker still. It is not in the 30-49 band because there is no evident volume or price-driven registration base and no category where a serious project would adopt it as its default identity; it is above the 1-9 band because short three-letter strings and the storage/homelab community give it a plausible, if shallow, hobbyist and defensive-registration market. Main market uncertainty: whether the operator positions .nas around a specific community (storage, a regional or linguistic meaning, or an open-data use) with a registration policy that makes the string legible to buyers, versus an undifferentiated open TLD.