.node
Is .node a real TLD? Who’s applying to run it?
.node is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 18 November 2026. They are XServer and Identity Digital. Radix named .node as a backup string for its .agent application. ICANN’s list shows it as deactivated: the application cannot move to it.
Who is applying, and what they run today
One of the two already run TLDs, 14.80M names between them. One runs one of .node's closest 2012 strings: Identity Digital .network. XServer runs none.
Will names sell?
A short technical word that infrastructure, blockchain and developer projects would genuinely use, but it needs explaining outside tech.
Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .node’s closest 2012 strings hold .network 80K, .cloud 552K and .dev 713K.
The nearest 2012 strings, and how many names each holds today
The closest 2012 string, .network, held 80,112 names, June 2026. .cloud held 551,867; .dev held 712,600. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.
Same bet: an unowned, abstract piece-of-infrastructure noun that nobody can claim as a brand, sold to operators and service providers who want their primary identity to be the plumbing itself rather than a product name.
Also an engineering-infrastructure abstraction with no natural owner, bought by compute/hosting providers, but it was the mass-market buzzword of its moment whereas a node is narrower practitioner jargon, so the addressable base is far wider.
Same buyer — engineers putting their identity on a word from their own working vocabulary — but it labels the practitioner rather than a unit of infrastructure, so it rides developer self-identification instead of a thing you deploy.
developers, blockchain-node operators and infrastructure or networking products that want a short technical identity, with a secondary pull for AI-agent and distributed-systems tooling
What a .node domain is
.node is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. 2 applications for it are on ICANN’s Reveal Day list.
Is the .node domain extension real yet?
.node 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 .node domain?
You can’t yet. A .node 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 .node was .network, delegated on 22 August 2014.
Is .node a real TLD?
Not yet. .node is not in the DNS root, so nothing resolves under it. It’s here because .node is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
The source’s 5 linesHide the lines
PPND2513-T68462 · Perkumpulan Pengelola Nama Domain Internet Indonesia · primary · contention set 2026-166 RTIS2674T-T51870 · Radix Technologies Inc SEZC · replacement string of .agent · Deactivated TT2652T-T75877 · Toddler Logic, LLC · primary · contention set 2026-166 XI2694T-T16045 · XRegistry Incorporated · primary · contention set 2026-166 XL2625T-T11396 · XYZ.COM LLC · primary · contention set 2026-166
The source’s 4 linesHide the lines
PPND2513-T68462 · Perkumpulan Pengelola Nama Domain Internet Indonesia · primary · contention set 2026-166 TT2652T-T75877 · Toddler Logic, LLC · primary · contention set 2026-166 XI2694T-T16045 · XRegistry Incorporated · primary · contention set 2026-166 XL2625T-T11396 · XYZ.COM LLC · primary · contention set 2026-166
- Band chosen: 50-69, strong niche. 'Node' is a live working term across three adjacent tech communities — JavaScript runtime culture, blockchain validator and node-operator services, and networking or distributed-systems infrastructure — so a serious project (a node-hosting service, a validator, a mesh-network product) could plausibly use a .node address as its primary identity without it reading as a joke. The record shows four applicants in one contention set, including established registry operators and an Applicant Support Program applicant, which I read neutrally as several parties seeing commercial demand in the string. It is not in the 70-89 band because no major category defaults to it: developers default to .dev/.io/.com and crypto projects to .xyz/.io/.com (analogy from how those TLDs are used), so adoption of .node will always need a sentence of explanation and the aftermarket is unproven. It is not in the 30-49 band because the demand would be semantic and primary-identity rather than purely price-driven; by analogy, strings like .cloud and .network found sustained technical use while broader generic-word tech strings relied on discount volume, and .node sits closer to the former on meaning. Main market uncertainty: whether 'node' reads as a brandable product name (one project per address) or as a generic infrastructure noun that ends up on throwaway operational hostnames with little resale value — the latter would push the score toward the mid-40s. A second, smaller uncertainty is whether the runtime community treats the term as too closely associated with an existing software name to brand on freely; I state no facts about that from memory.