Key Takeaways from ICANN84 in Dublin
Prepared for ENS Public Goods Working Group by Emily Murray
Members of ENS Labs and ENS DAO attended ICANN84, held in Dublin from October 25-30, 2025. Several members attended in person, with remote support provided for many sessions by Policy Consultant Emily Murray. The team’s work focused on developments relating to the new generic top-level domain (gTLD) program; activities of the Governmental Advisory Committee (GAC) and other stakeholder organizations such as the Generic Names Supporting Organization (GNSO) and Country Code Names Supporting Organization (ccNSO); sessions relating to Domain Name System (DNS) abuse and rights protection mechanisms; and ongoing discussions within the ICANN community of the relationship between the traditional DNS and Web3/blockchain domains. Please find below a summary of key takeaways from the ENS Team’s engagement in ICANN84.
High-Level Takeaways
- ICANN’s next round of new gTLDs is moving forward with the application window scheduled to launch in April 2026 (likely late April).
- The ICANN Board voted to approve the New gTLD Applicant Guidebook (AGB), which provides all of the policies and procedures for participation in the new gTLD program as an applicant or other interested party (i.e., a party who may wish to object to applications). A few pieces remain to be finalized in the AGB, but it is due to be published by December 30, 2025. (As a reminder, ENS participated extensively in the public comment process during the development of the final AGB.)
- Other than the new gTLD program, key ICANN policy priorities discussed during the meeting included: combating DNS abuse (and continuing to enhance rights protection mechanisms for doing so); and continuing to improve global ICANN engagement, particularly from historically underserved regions.
- Other than the work of the Security and Stability Advisory Committee (SSAC) Responsible Integration into the DNS Ecosystem (RIDE) Working Party, blockchain/Web3 issues were not widely discussed during formal ICANN84 sessions, except for a brief mention during the Public Forum. Accordingly, this further emphasizes the importance of continued ENS/Public Goods Working Group participation in ICANN so that Web3 issues can be better understood by the broader ICANN community and a greater cross-section of Internet users, instead of continuing to be viewed as a niche, specialized technical topic that is not relevant to most of the community. There does seem to be a great deal of interest from the general ICANN community in this topic based on conversations held during ICANN84 outside of official sessions, and thus there is room for collaboration with both ICANN staff and other stakeholders to ensure information is made available to the community from trusted, reliable sources such as ENS.
New gTLD Program Updates and Reminders
- The new gTLD program is generally on track for a launch in April 2026, likely late that month. Once the application window opens, it will likely run for about 12-15 weeks before closing in July or August 2026.
- The base application fee is confirmed at $227,000. Only organizations (not individuals) can participate as applicants in the program. Certain additional evaluation fees, ranging from a few hundred to many thousands of dollars, may be required for certain applications. Applicants may also face objections from other parties, and participation in objection proceedings may require up to tens of thousands of dollars per objection based on the costs from the 2012 application round. Also, applicants should be prepared for the possibility that their string will be in a contention set that goes to auction to the highest bidder - this could be up to millions of dollars per string. Private resolution of contention sets to avoid an auction is prohibited in this new gTLD round, however, some community members are exploring workarounds for this restriction.
- With the exception of an initial technical check of the proposed string, evaluations will not begin until the close of the application window, so there is not likely an advantage to submitting an application early in the process.
- The Applicant Support Program (ASP) remains open for a bit longer. This is a program that allows applicants with limited financial resources to apply for some support, which will amount to about an 80% reduction in new gTLD program costs, including credits toward an auction (to certain limits) if the desired string ends up in contention. Parties interested in the ASP must begin their applications by November 19 and must complete them by December 19.
- ICANN estimates that the full evaluation process will take around 14-19 months (before the first new gTLDs begin to be delegated), so the first new gTLDs from the 2026 round would not likely be added to the Internet until at least late 2027.
- Organizations that are members of the blockchain/Web3 community may be particularly interested in applying for the “.brand” type of new gTLD, in which the new gTLD extension represents a brand name and in which the new gTLD is operated for the sole benefit of the operator (domains would not be sold or offered to third parties). Please note that one requirement for this type of new gTLD is that the new gTLD string be identical to a Trademark Clearinghouse (TMCH) registration owned by the applicant. The TMCH is a rights protection mechanism implemented for the 2012 new gTLD application round. As completing an initial TMCH registration can take several months, interested organizations should begin the TMCH process as soon as possible to ensure they are eligible to apply for .brand type new gTLDs.
- The base new gTLD Registry Agreement, the contract that successful applicants will sign in order to be able to operate their gTLDs for a period of 10 years, is not quite finalized yet but should be by around March 2026. This should not delay the launch of the application window.
- The technical aspects of the string similarity review process, which will be a part of the new gTLD evaluations, are also still under development. A public comment window is open on this topic through December 4, 2025. ENS is planning to participate in this comment opportunity, particularly to advocate for the inclusion of Web3 domains in the string similarity analysis due to name collision concerns.
- Overall, most groups of ICANN stakeholders appear to be enthusiastic about the new gTLD program and are eagerly anticipating its launch in April 2026. Some ICANN84 attendees expressed concerns about program readiness in a couple areas, specifically, the technical capacity of the application system to handle the load, as well as the capacity of the GAC to review and evaluate applications quickly. Some members of the community also relayed concerns that, once again, the new gTLD program might not succeed in serving the broader global community, and that applicant representation from typically underserved regions may be less than originally hoped.
DNS Abuse and Rights Protection Mechanisms
- In addition to the new gTLD program, combating DNS abuse is a top ICANN policy priority for the coming years. ICANN recently held a public comment opportunity on its Preliminary Issue Report on this topic, in which ENS participated. The GNSO Council is currently preparing a Final Report in advance of considering moving forward with a formal Policy Development Process. Assuming ICANN does move forward with a PDP on this topic, this would be an excellent opportunity for ENS to contribute visibly to the public good by sharing its technical expertise and advocating for broader but practical and cost-effective measures to reduce DNS abuse and mitigate its effects.
- ICANN recently concluded a pilot program on its Registration Data Request Service (RDRS). Following the implementation of GDPR in 2018, Internet registrars have not been able to publish most domain registration data without the express authorization of the registrant, leading to delays in combating infringing registrations. The RDRS allowed parties with some justified need for registration data (i.e., suspected infringement, law enforcement reasons, etc.) to request this data in advance of initiating a formal dispute resolution proceeding. The RDRS pilot program had mixed results, with fewer than half of domains under management participating in the voluntary program. In addition, under 40% of requests made were actually fulfilled, with registrars often citing that they believed they were legally barred from providing the requested data. Citing a need for additional data and looking to increase participation in the program, ICANN has extended the RDRS program for two more years, through December 2025. The GAC and some other ICANN stakeholder groups have expressed concerns that a service such as RDRS will only be effective if it is mandatory, rather than voluntary; however, it appears the voluntary program will remain in place for at least two more years. ICANN has recently opened a public comment window on RDRS policy alignment, which will run through December 9, 2025. ENS may wish to consider participating in this public comment opportunity in order to contribute its technical expertise and continue to build its reputation for good citizenship in the ICANN community.
- In addition to attending official ICANN84 sessions that were part of the public program schedule, Alex Urbelis had the opportunity to attend an offsite session on DNS abuse that ICANN had organized in Dublin for law enforcement professionals, and provided a presentation and led a discussion on this topic. Accordingly, ENS is seen as a trusted source for information on DNS abuse, and this presents a further opportunity for collaboration and educating the public on why attention to this topic is essential to ensure a safe and secure Internet.
Blockchain and Web3 Discussions
- The past Annual General Meeting, held in Istanbul in November 2024, offered several sessions devoted to blockchain and Web3 issues. At that time, ICANN had expressed that there might be another focus on such issues during the 2025 Annual General Meeting. However, the ICANN84 schedule showed very minimal attention to blockchain and Web3 issues. Instead, sessions devoted to cutting-edge technologies instead focused on issues such as the use of AI in combating DNS abuse. ICANN did touch on the increasing use of country code top-level domains (ccTLDs) in cryptocurrency schemes - an issue somewhat adjacent to Web3 - but this discussion still focused on the traditional DNS.
- The Security and Stability Advisory Committee (SSAC) has formed a Working Party called RIDE (Responsible Integration into the DNS Ecosystem), which deals with the intersection of the traditional DNS and Web3. This group, which appears to be the only group formally organized by ICANN that is paying ongoing attention to Web3 issues, held a meeting in Dublin. The issues discussed in this meeting largely echoed those raised at the prior ICANN meeting, particularly that without increased attention to this matter, significant name collision issues could arise between new gTLDs added to the traditional DNS, and Web3 names. Group members cited, for example, that some web browsers now integrate access to Web3 names without special plug-ins required, and that users may face either domain resolution issues, or may be directed to domains they did not intend to access, once more new gTLDs are added to the DNS. As with the prior discussion, the meeting in Dublin raised issues and concerns more than proposing specific solutions, with all agreeing that ongoing work and study is needed. The RIDE Working Party does plan to publish a report on this topic in the first half of 2026; however, this will likely overlap with the launch of the new gTLD application round. Again, ENS should look for opportunities to amplify the voice of the RIDE Working Party, which for the moment appears to appeal to a smaller group of technical experts rather than the broader ICANN community. However, the existence and ongoing work of the RIDE Working Party does lend further legitimacy to ENS and the Public Goods Working Group’s advocacy points, such that the concerns we express are not solely coming from outsiders.
- @clowes.eth also attended the RIDE Working Party meeting and contributed his technical expertise to the discussion, and has been invited to explore future collaborations with the group.
- Participants in the Public Forum, during which members of the community can ask questions of the ICANN Board and executive team, did also bring up Web3 issues briefly, particularly asking about how the intersection of Web3 and the traditional DNS might impact ICANN compliance matters and service obligations for Internet registries. No definitive response was provided from ICANN leadership, but this is an issue to continue monitoring for further discussion and potential advocacy.
- Overall, the biggest concerns from other ICANN stakeholders regarding Web3 as highlighted by @simona_pop seem to be:
- Language vs. mechanics: ENS’ constitutional language about not infringing name-owner rights can sound like “perpetuity,” even though the mechanics are term-limited with expiry. That messaging gap alone is triggering policy anxiety.
- Dispute resolution parity: Without a built-in, binding UDRP-style pathway, brands and rights-holders lack a familiar, enforceable mechanism to recover abusive registrations. That’s a notable divergence from ICANN norms.
- Governance priorities: "Integrate with DNS without sacrificing decentralization” is philosophically sound for web3, but for ICANN it raises the question: When these values collide, who yields?
Next Steps for ENS and the Public Goods Working Group
- Monitor and review public comments submitted by third parties in the Proposed Next Round Base gTLD Registry Agreement public comment window, due to close on November 17, 2025, and review the final Base gTLD Registry Agreement when published.
- Prepare and submit comments for the String Similarity Evaluation Data for New gTLD Program: Next Round public comment opportunity, due by December 4, 2025.
- Consider the opportunity to prepare and submit comments for the Registration Data Request Service (RDRS) Policy Alignment Analysis public comment opportunity, due by December 9, 2025.
- Prepare Venn diagrams illustrating what a collaborative approach would look like between ENS/the public goods community and various ICANN stakeholders, in particular, looking at areas of overlap and opportunities for closer collaboration and alignment.
- Conduct a detailed analysis of the final New gTLD Applicant Guidebook (AGB) when published, anticipated by December 30, 2025.
- Develop outreach strategy to educate other blockchain/Web3 organizations that may not currently be participating in ICANN about the new gTLD program opportunity.
- Monitor for publication of the public comment report on the Preliminary Issue Report on a Policy Development Process on DNS Abuse Mitigation (ENS recently submitted public comments on this topic; ICANN’s report should be published in the coming weeks), as well as continue monitoring for additional developments in connection with a potential formal Policy Development Process on this topic.
- Evaluate opportunities to participate in the SSAC RIDE Working Party or to amplify the voice of this group, to ensure that blockchain/Web3 issues remain on the radar for the broader ICANN community.
- Begin preparations for ICANN85 in Mumbai, which will be held from March 7-12, 2026.