New foundation structure clears a hurdle for ENS’s new TLD application.
ENS forms operating foundation to pursue an ICANN top-level domain
The Ethereum Name Service (ENS) has created a new operating entity, a step that clears an important administrative and governance hurdle for the organization as it moves to pursue a top-level domain (TLD) with ICANN. Token holders recently approved a governance proposal labeled “Next Era of ENS DAO: Empowering the ENS Foundation,” which establishes the ENS Foundation as an operating foundation with a board, executive director, and staff. The board itself is subject to ratification by ENS token holders.
Establishing an operating foundation aligns ENS’s organizational structure with the expectations of traditional internet governance bodies. ICANN typically requires clear legal and operational accountability from applicants seeking to manage a new TLD. Forming a foundation with named leadership, formal staff, and documented responsibilities helps ENS present itself as a capable and accountable registry operator, which may ease the application process.
Why .ens rather than .eth?
ENS’s web3 namespace is widely known under the .eth label, but .eth is effectively unavailable as an ICANN TLD because it is an ISO 3166-1 alpha-3 code associated with Ethiopia. That reservation blocks usage of .eth as a conventional ICANN root domain. As a consequence, the organization is planning to apply for the string .ens as its ICANN TLD instead. Using .ens would allow ENS to obtain a recognizable, short namespace at the DNS root while avoiding the ISO restriction tied to .eth.
Shifting from a native web3 label to an ICANN-root TLD is not simply a cosmetic change. ENS will need to address technical and policy questions around how existing .eth registrations and the ENS protocol interact with a canonical DNS namespace. Pursuing .ens gives the organization an option to bridge those ecosystems while sidestepping the reserved string problem.
Process considerations: RSEP and technical evaluation
If the ENS Foundation proceeds with an ICANN application, the organization may be required to navigate policy and technical review processes that assess registry services and integrations. For new or novel services that alter how a registry functions, ICANN’s Registry Services Evaluation Policy (RSEP) and related technical review panels often come into play. These procedures examine whether a proposed service is compatible with DNS stability, security, and existing policy commitments.
For ENS, these evaluations would likely focus on how a web3 namespace—already active within ENS’s protocol and smart contract ecosystem—could be integrated with an ICANN-managed namespace. Topics under scrutiny could include name collision risks, delegation and resolution mechanics, operational control of the registry, and safeguards to ensure continued reliability for users on the DNS root.
Governance and protocol control
The approved ENS proposal carefully preserves core protocol control for ENS token holders. It defines “protocol control” to include smart contract upgrades, pricing and fee structures, root key and registry control, DAO-held ENS tokens, constitutional amendments, and the appointment, renewal, and removal of directors. In other words, the token-holder community retains exclusive authority over the protocol-level decisions that define ENS’s on-chain behavior and economic model.
At the same time, the new ENS Foundation will operate as the entity responsible for pursuing ICANN-related work, managing staff, and executing administrative responsibilities. To integrate a newly obtained .ens TLD with the existing ENS protocol, the foundation will likely need to demonstrate that it effectively controls the corresponding namespace within the Ethereum Name Service. That proof of control will be an important part of any technical and policy evaluation tied to registry operations.
Implications and next steps
Forming the ENS Foundation is a pragmatic move that aligns the organization with established internet governance norms, making it more straightforward to engage with ICANN and other institutions. Applying for .ens opens the door to a DNS-root presence that mirrors ENS’s existing brand and user base, while avoiding the ISO-related restriction on .eth.
Going forward, observers will watch how the ENS Foundation approaches the RSEP and any technical assessments, and whether it can reconcile the user experience and security expectations of both the DNS and the ENS protocol. Successful integration would set a precedent for how web3 naming systems can coexist and interoperate with conventional internet naming infrastructure, balancing on-chain governance with off-chain regulatory and operational requirements.
Overall, the governance change represents a significant administrative milestone. It does not, by itself, guarantee ICANN approval, but it positions ENS to engage the application and evaluation processes with a clearer, more conventional organizational structure.