.node aims to establish a trusted, universal digital namespace for organizations, businesses, creators, and innovators across every industry, spanning global enterprises, supply chains, technology, healthcare, creative networks, and beyond. By providing semantic clarity and a distinct identity for any point of connection, interaction, or collaboration on the internet, .node serves as an intuitive digital anchor for all interconnected systems. Furthermore, evaluations via the ICANN Name Collision Observatory confirm that .node carries a low name collision risk compared to other strings and is neither classified as a special case nor listed among ICANN’s reserved names.
The mission of .NODE is to provide a namespace associated with the concept of node as a point of connection or interaction within a larger system or network. The .NODE gTLD is intended to serve a broad range of registrants and users, including individuals, businesses, organizations, communities, projects, and other entities that identify with, relate to, or wish to be associated with the concept represented by the applied-for string.
The purpose of .NODE is to enable registrants to establish online identities using domain names that correspond to this concept. To achieve this purpose, Toddler Logic, LLC will make .NODE available for registration through registrars and other appropriate distribution channels; maintain a secure, stable, and reliable registry infrastructure; implement registration and operational policies that support the availability, security, and integrity of the namespace; and provide ongoing administration of the gTLD to enable registrants to register and use domain names within the namespace.
The purpose of .NODE is sustainable over time because points of connection or interaction within a larger system or network will continue to play a fundamental and enduring role across society and technology. As society and technology evolve, organizations and individuals will continue to establish online identities associated with the applied-for string.
The mission of .node is to give distributed and cloud computing a namespace named after its own unit of composition. The string is the ordinary English noun ""node"" - a point at which paths meet, and, in computing, a machine or process taking part in a larger system. It is applied for and will be operated in that plain descriptive sense, as an open namespace.
Registrants are the organisations and people who build systems out of parts: cloud and platform providers, operators of clusters and distributed systems, container and orchestration vendors, content delivery and edge operators, monitoring and observability vendors, open source infrastructure projects, research computing groups and universities running clusters, the IT teams of organisations of every size, and individual developers.
Users are the people and systems that reach those addresses: operators opening a console, client software resolving a regional endpoint, customers consulting a status page, and developers following documentation.
Computing has moved from single machines to systems assembled from many interchangeable parts, and each part has to be addressed. That addressing is done today inside a domain chosen for commercial reasons, so an operational name inherits a marketing brand that may change and tells the reader nothing about what sits behind it.
A top-level namespace whose word is precisely ""node"" resolves that mismatch. name.node is short, self-describing and legible to the audience that matters. It suits a regional or edge endpoint, a cluster member, a project's public entry point and the console that goes with it, and it separates operational naming from the commercial identity of whoever owns the infrastructure.
The TLD will launch with the rights protection mechanisms required by Specification 7, including a Sunrise period and a Trademark Claims period. General Availability will then be open, with no eligibility restrictions and no reservation of the namespace to the applying entity or its affiliates. Distribution will be through ICANN-accredited registrars on published, non-discriminatory terms consistent with Specification 9, including any registrar affiliated with the applying entity, which will receive the same terms as every other; availability will not be conditioned on being a customer of any affiliated company. Technical operation is contracted to a pre-evaluated Registry Service Provider, and abuse mitigation follows the Mandatory Public Interest Commitments and the DNS abuse obligations of the Base Registry Agreement.
The purpose is sustainable because the underlying activity is attached to no product cycle: systems will continue to be assembled from addressable parts, and those parts provisioned, moved and retired, which is a source of continuous rather than one-off demand. A domain used as an operational address behaves differently from one used as a website, being written into configuration files, DNS records, monitoring systems and client software, so letting it lapse breaks running systems rather than merely taking a page offline, and the registrant renews it as a matter of operational necessity. The applying entity belongs to an established hosting and infrastructure group whose customer base is precisely the population of intended registrants, so awareness does not rest on paid acquisition alone. The technical sense of the word is understood identically across language markets, and the string is tied to no single vendor, protocol or platform, so the namespace does not become obsolete if one of them declines. Registry operations are contracted to a pre-evaluated Registry Service Provider under a signed agreement, so the obligations of the Registry Agreement are met throughout ramp-up without depending on registration revenue alone.
1. Mission and purpose. This gTLD will be operated as an open, unrestricted generic top-level domain. Its purpose is to expand naming choice in the DNS by making this term available at the top level for any lawful use chosen by the registrant. Registrations will be available to all registrants on a first-come, first-served basis through ICANN-accredited registrars, subject only to the Registry Agreement, ICANN Consensus Policies, and applicable law. The applicant will not operate this gTLD on an exclusive basis.
2. Intended registrants and users. Intended registrants are individuals, businesses, and other organizations worldwide seeking a short, meaningful domain name. There are no eligibility or name selection restrictions beyond those required by the Registry Agreement, ICANN Consensus Policies, and applicable law. Intended users are internet users worldwide who access domain names registered in this gTLD.
3. Related activities. The applicant is an established registry operator under contract with ICANN for 35 gTLDs, including .xyz. It has in place a qualified Registry Service Provider, distribution agreements with ICANN-accredited registrars across multiple regions, and all required rights protection mechanisms and DNS abuse mitigation practices. For this gTLD the applicant will onboard the TLD to its existing registry platform, conduct a Sunrise Period and Trademark Claims Period, launch General Availability through its registrar channel, and maintain ongoing registrar enablement, abuse monitoring, and compliance reporting.
4. Sustainability. Operation is funded by recurring registration and renewal revenue and does not depend on any single registrant, sector, or campaign. This gTLD will run on the applicant's existing shared registry infrastructure, so incremental operating cost is low and no minimum registration volume is required for viability. The applicant has operated gTLDs continuously since 2014.