ICANNWiki

New gTLD Program: Next Round

For another use, see New gTLD Program (2012).

The New gTLD Program: Next Round (also referred to as the New gTLD Program: 2026 Round) is the second application round for new gTLDs, following the 2012 New gTLD Program. It enables further expansion of the Domain Name System (DNS) and provides businesses, communities, governments, and other organizations the opportunity to apply for new top-level domains tailored to specific organizational, cultural, linguistic, or customer needs.

The 2026 Round application submission period is defined in the Applicant Guidebook (AGB) as opening "no later than 30 April 2026 (23:59 UTC)", remaining open for 105 days, and closing August 12, 2026 (23:59 UTC).[1]

The program is being implemented by ICANN in line with community-developed policy recommendations contained in the Generic Names Supporting Organization's Final Report on the new gTLD Subsequent Procedures Policy Development Process.[2]

Background

edit

The first New gTLD Program application round opened in January 2012 and resulted in over a thousand new gTLD delegations, including geographic, community, brand, and generic strings. After the close of the 2012 round, ICANN and the community launched a broad series of reviews and studies on topics such as rights protection mechanisms, DNS Abuse, consumer trust, competition, and name collisions.

In December 2015, the GNSO Council initiated the Policy Development Process on New gTLD Subsequent Procedures (SubPro) to determine whether, and under what conditions, additional application rounds should proceed.[3] The GNSO New gTLD Subsequent Procedures (SubPro) Working Group conducted several years of deliberations, including work tracks on overarching issues, application types, geographic names, and technical and operational criteria. Its "Final Report on the new gTLD Subsequent Procedures Policy Development Process" was delivered in February 2021 and organized into a set of affirmations, recommendations, and implementation guidance.[4]

On February 18, 2021, the GNSO Council approved all SubPro outputs that achieved "Full Consensus" or "Consensus" and transmitted them to the ICANN Board.[3] Following receipt of the SubPro Final Report, ICANN org conducted an Operational Design Phase (ODP) to assess the practical, financial, and risk implications of implementing the new policies; the resulting Operational Design Assessment (ODA) was delivered to the Board in December 2022.[3]

On March 16, 2023, the Board adopted the majority of SubPro recommendations and marked a smaller set as pending while it consulted further with the GNSO and the GAC.[5] The Board also requested an implementation plan from ICANN org describing how a subsequent round could be operationalized, which was delivered on July 31, 2023.[6]

Implementation Governance

edit

SubPro Implementation Review Team

edit

To help ensure fidelity to the policy recommendations, the GNSO Council chartered the SubPro Implementation Review Team (IRT). The IRT consists of community volunteers who review draft implementation proposals, comment on operational details that interpret policy, and receive regular updates on communications, outreach, and systems development.[6][7]

ICANN org provides monthly reports to the IRT on outreach and engagement efforts for the Next Round, and holds regular IRT calls where program timelines, draft Applicant Guidebook text, and related implementation topics are discussed.[7]

ICANN Oversight

edit

The ICANN Board oversees the overall direction of the Next Round, adopting relevant policy recommendations, approving key program documents such as the Applicant Guidebook (AGB), and authorizing the opening of the application window.[8] ICANN org is responsible for detailed program design, systems implementation, contracting, and ongoing operations, reporting back to the Board and community through public sessions at ICANN meetings and written updates.[6] [9]

Applicant Guidebook and ICANN Board Adoption

edit

The Applicant Guidebook (AGB), or 2026 Round Applicant Guidebook, is the primary rulebook for the 2026 Round, setting out application requirements, evaluation and objection procedures, contention resolution, contracting steps, and the conditions for delegation and operation of new gTLDs.[1]

On November 3, 2025, ICANN announced that the Board adopted the AGB at ICANN 84 and directed ICANN org to publish the AGB no later than 30 December 30, 2025 (with only insignificant changes while final consistency checks and alignment with Dispute Resolution Service Provider rules were completed).[10] The final AGB (V1-2025.12.16) was published on 16 December 2025.[1][11]

Policy Framework

edit

The policy basis for the Next Round is the SubPro Final Report, which affirms the continuation of subsequent rounds for new gTLDs, the use of discrete application cycles ("rounds") rather than a fully continuous model, and the availability of different gTLD types (standard, community, geographic, and brand TLDs).[4]

Applications in Rounds

edit

SubPro recommends that further new gTLD applications continue to be processed in periodic rounds rather than through a fully continuous model. At the same time, it calls on ICANN to work toward more predictable and regularly recurring application opportunities, so that potential applicants can plan around an anticipated cadence of rounds and not face long, indeterminate gaps between them.[4]

Applicant Types and TLD Categories

edit

The Next Round maintains multiple gTLD application types, including standard, community-based, geographic, and dotBrand-type applications, with differing eligibility and evaluation considerations. For example, community-based applications may seek Community Priority Evaluation, geographic names require additional support or non-objection documentation, and brand-type applications may qualify for tailored contractual treatment.[4][1]

String Similarity

edit

The 2026 Round includes string similarity review to assess potential user confusion with existing TLDs and other applied-for strings. In addition, the AGB implements a separate process for 'Singular/Plural Notifications.

Under this mechanism, third parties may submit a notification within 30 days after the "String Confirmation Day" asserting that an applied-for string is the singular or plural version of another relevant string. If a Singular/Plural Notification is confirmed, outcomes in the AGB include:

  • placement of the strings into a singular/plural contention set; or
  • in specified cases (for example, where the applied-for string is the singular/plural version of a delegated TLD or a blocked name), the application may not proceed.[1]

Applicant Freedom and Safeguards

edit

The AGB reflects SubPro's balancing of applicant freedom of expression with safeguards related to legal rights, objection mechanisms, and program integrity. SubPro reaffirmed that the evaluation process should not infringe applicants’ freedom of expression under internationally recognized principles of law, while also requiring respect for enforceable legal rights (including intellectual property rights).[4][1]

IDNs and Variants

edit

The Final Report reaffirmed that IDN gTLDs are an integral part of the New gTLD Program and sets out requirements for compliance with RZ-LGR and IDNA2008. It also introduced policy principles for IDN variant management at the top level, including conditions under which variants may be delegated and the requirement that variant sets be operated by the same registry operator and back-end provider, anticipating further detailed implementation through the IDN EPDP and related work.[4]

According to ICANN, the Next Round will support applications for new gTLDs in any language or script that has a common and widespread use by a community, but only for scripts that are integrated into the Root Zone Label Generation Rules (RZ-LGR).[12] For the 2026 round, ICANN will use RZ-LGR version 6, which currently covers twenty-seven scripts: Arabic, Armenian, Bangla, Chinese (Han), Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Gurmukhi, Hebrew, Japanese (Hiragana, Katakana, and Kanji [Han]), Kannada, Khmer, Korean (Hangul and Hanja [Han]), Lao, Latin, Malayalam, Myanmar, Oriya, Sinhala, Tamil, Telugu, Thaana, and Thai.[12][13]

If an applicant wishes to apply for a new gTLD in a script that is not yet supported by the RZ-LGR but has common and widespread use, the application will be put on hold until the relevant script community forms a Generation Panel and develops an LGR proposal. That proposal is then reviewed by the Integration Panel and, if approved, integrated into the RZ-LGR under the "Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels".[12][14]

Closed Generics

edit

Closed generics are defined as "a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others". They were treated as a pending topic during SubPro and the Operational Design Phase, and were the subject of a 2022–2023 Facilitated Dialogue among the GAC, GNSO, and ALAC. After considering the dialogue outcomes and GAC/ALAC advice, the ICANN Board decided in January 2024 that closed generic gTLD applications will not be permitted in the 2026 round unless and until an approved methodology and criteria are developed to assess their compatibility with the public interest.[5] The AGB maintains this position.[1]

IDN Policy Dependencies

edit

The Expedited Policy Development Process on Internationalized Domain Names (IDNs) provides the detailed rules for IDN gTLDs and top-level variants in the Next Round. Phase 1 recommendations, which cover top-level IDN definitions and variant sets, were fully adopted by the ICANN Board in 2024–2025 and are being implemented through an IDN Implementation Review Team as a sub-track of the SubPro IRT. Phase 2 recommendations, focused on second-level variant management, have been approved by the GNSO Council and are currently under ICANN Board consideration following a 2024–2025 public comment proceeding.[3]

Applicant Support Program

edit

SubPro recommends an expanded and better resourced Applicant Support Program targeted at eligible applicants with limited financial means, particularly from underserved regions and communities. The policy framework envisages reduced fees, non-financial support such as pro bono services, and carefully structured mechanisms (including possible bid credits in contention resolution) designed to improve the chances that supported applicants can successfully obtain and operate a gTLD.[4]

Registry Service Provider Evaluation Program

edit

The Registry Service Provider (RSP) Evaluation Program pre-evaluates entities that provide back-end registry services to ensure that Registry Service Providers meet the technical requirements to run a TLD back-end. This enables RSPs to be evaluated just once, no matter how many TLDs they may support. The AGB and program documentation describe this as a mechanism to reduce duplicative technical review by separating assessment of registry technical operations from the gTLD string application.[1][15] [16]

The program had a pre-evaluation period from November 19, 2024 to May 20, 2025. An initial list of organizations participating in the Registry Service Provider (RSP) Evaluation Program was published by ICANN on January 30, 2026. The list includes organizations that have cleared both technical screening and technical testing, as well as those that have cleared technical screening but are still in the process of clearing technical testing. Remaining RSP, IDN Services, and additional Registry Services applications are expected to be published in early March 2026.[17]

RSPs that did not apply in the pre-evaluation window will be able to apply in parallel to the opening of the gTLD application window expected to open on April 30, 2026.[16]

The List of Evaluated RSPs will be updated on an ongoing basis as ICANN continues to test and qualify providers.[17]

Outreach and Communications

edit

ICANN's outreach and communications strategy for the Next Round includes:

  • A dedicated Next Round information portal with general information, timelines, FAQs, and links to detailed resources.[18][12]
  • The "Next Round Reports" series, which documents monthly outreach, engagement, and communications activities shared with the SubPro IRT.
  • Webinars, regional events, and presentations at ICANN Public Meetings aimed at governments, businesses, civil society, technical communities, and potential applicants.
  • Tailored materials such as slide decks and "champions toolkits" that organizations can reuse to raise awareness in their own communities.[7]

These efforts aim to increase global diversity in the DNS sector, raise awareness of the Next Round and the Applicant Support Program beyond the existing ICANN community, and encourage applications from regions and communities that have been under-represented in previous rounds.[7] [19] [5]

Applicant Support Program

edit

The Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants, particularly those from underserved regions or with limited resources.[20] Qualifying supported applicants may receive reduced evaluation fees, access to pro bono professional services, and preferential treatment in any ICANN Auction of Last Resort within defined parameters.[21]

The ASP application submission period opened on November 19, 2024 and closed for complete applications on December 19, 2025 (following a deadline extension for applicants who had entered organizational information by 19 November 2025).[22]Cite error: Closing </ref> missing for <ref> tag

The Applicant Support Program is explicitly intended to lower barriers for eligible applicants, including those proposing IDN strings or serving communities with limited prior participation in the gTLD space.[20][21] Non-financial support may include mentorship, legal and policy advice, and technical assistance provided by volunteer experts coordinated by ICANN.[9]

ICANN's outreach strategy for the Next Round includes regional engagement, multilingual materials, and partnerships with local organizations to reach potential applicants that may otherwise be unaware of the opportunity to apply for a gTLD.[7]

Registry Service Provider Evaluation Program

edit

The Registry Service Provider (RSP) Evaluation Program pre-evaluates entities that provide critical back-end registry services. The AGB and program documentation describe this as a mechanism to reduce duplicative technical review by separating assessment of registry technical operations from the gTLD string application.[1][15]

The program includes two evaluation periods: an initial pre-application period from November 19, 2024 to May 20, 2025, and a second period aligned with the 2026 application window.[23][24] RSPs that successfully complete evaluation are listed on a dedicated page for use by prospective applicants.[23] Through the program, RSPs may only need to be evaluated once for the 2026 Round regardless of the number of gTLDs they support.[1]

Systems and Tools

edit

ICANN is deploying a new "TLD Application Management System (TAMS)" to replace the 2012 TAS platform. TAMS is designed to support application submission, document management, evaluation workflows, communications between ICANN and applicants, and publication of application data.[6]

Additional tools include portals for the Applicant Support Program, the RSP Evaluation Program, and public information sites that present timelines, FAQs, and outreach materials for potential applicants.[18] [12]

Applicant Journey

edit

Pre-Submission

edit

In the pre-submission phase, prospective applicants are expected to review the Applicant Guidebook, evaluate business cases for operating a gTLD, and identify potential strings and registry service providers. ICANN supports this phase with information materials, webinars, regional engagement activities, and an outreach “toolkit” aimed at organizations that can promote awareness of the Next Round in their communities.[18][7]

Applicants requiring financial or capacity support are encouraged to apply to the Applicant Support Program sufficiently in advance of the main application window.[20][9]

Application Submission

edit

During the 2026 application window, applicants submit their gTLD applications through TAMS. Each application must provide detailed information about the applicant entity, the proposed string, registry services, technical and operational plans, financial capabilities, and policies for abuse mitigation and rights protection.[12][6] Applicants will be able to enter their string in TAMS to check whether there is a match. If a string fails one of the validations or a match is found, the applicant will receive an error or warning message in TAMS explaining the detected issues and will not be allowed to proceed and submit its application or will have to provide additional documentation.[1]

Evaluation

edit

Once the application window closes, ICANN conducts a series of evaluations, which may include:

  • Administrative completeness checks: verifying that required fields and supporting materials have been provided.
  • String similarity and DNS stability review: assessing the applied-for string for potential confusion with existing or other applied-for strings and for technical stability concerns.[25]
  • Technical and operational evaluation: reviewing the registry services architecture, DNSSEC plans, and other technical aspects; applicants using pre-evaluated RSPs may undergo a streamlined review.
  • Financial evaluation: examining whether the applicant has the financial resources to operate the registry over the long term.[6]

Additional IDN-specific checks apply to IDN gTLDs, including script rules, variant management, and consistency with Root Zone Label Generation Rules and IDN policy.[26][3]

Objections and Dispute Resolution

edit

As in the 2012 round, third parties may file objections on defined grounds, such as string confusion, legal rights, community opposition, or limited public interest.[6][4] Designated dispute resolution providers evaluate objections and issue expert determinations, which can affect whether an application proceeds or is terminated.

SubPro refined aspects of the objection process, and these refinements are reflected in the Next Round's Applicant Guidebook and procedural documentation.[4]

String Contention and Contention Resolution

edit

If multiple applications are received for the identical string, they are placed into a contention set. Contention can be resolved through community priority evaluation (for qualifying community applications), voluntary agreements among applicants, or, as a last resort, an ICANN-managed auction mechanism.[4][6]

ICANN has issued a Request for Information (RFI) regarding auction service providers specifically for the Next Round, with the aim of ensuring compliance with policy requirements and operational standards.[27]

Contracting and Delegation

edit

Successful applicants that pass evaluation, resolve any objections and contention, and meet all program requirements are invited to sign a Registry Agreement (RA) with ICANN.[6] After contracting and pre-delegation testing, the new gTLD is inserted into the DNS root zone and can begin its launch phases (such as Sunrise, Claims, and general availability) according to applicable rights protection rules.[3]

Governance and ICANN Community Dynamics

edit

The Next Round reflects input from multiple ICANN structures:

  • The GNSO Council served as the policy manager for the SubPro PDP, adopted the Final Report, and later issued a clarifying statement for recommendations the Board had marked as pending.[3][5]
  • The GAC has tracked the Next Round through a dedicated activity page and has issued advice and correspondence on topics such as closed generics, safeguards, public interest considerations, and geographic names.[5]
  • The SSAC and other advisory bodies have contributed guidance on DNS stability, name collisions, and security considerations relevant to the program.[3]

Community discussions continue on how best to incorporate DNS abuse safeguards, predictability, and public interest considerations into the Next Round's implementation, with many of these themes surfacing in public comment proceedings and ICANN meeting sessions.[21][25]

Issues and Debates

edit

Several topics have generated sustained community debate in relation to the Next Round:

  • Closed generics: whether and under what conditions single-registrant TLDs for generic terms should be allowed, and what safeguards or public interest tests would apply. This topic was the focus of a 2022–2023 Facilitated Dialogue among GAC, GNSO, and ALAC representatives and multiple rounds of GAC advice. After considering the dialogue’s Outcomes Report and community inputs, the ICANN Board decided in January 2024 that closed generic gTLD applications will not be permitted in the 2026 round unless and until an approved framework is developed to assess their compatibility with the public interest.[5][4]
  • DNS Abuse and safeguards: Expectations that Next Round applicants adopt stronger measures against DNS Abuse than those in place during the 2012 round, including more prescriptive contractual provisions, clearer obligations around monitoring and reporting, and greater transparency over how abuse is detected and mitigated. GAC advice, community comments, and ICANN's implementation updates all highlight DNS Abuse as a central concern for the design of the Applicant Guidebook and Registry Agreement for the 2026 round.[21][5]
  • Predictability and subsequent rounds: Calls from many stakeholders for more regular and predictable application opportunities beyond the 2026 round, rather than ad-hoc “one-off” large rounds separated by long gaps. The SubPro Final Report recommends adoption of a Predictability Framework and the creation of a Standing Predictability Implementation Review Team (SPIRT) to handle changes affecting the program, as well as requirements that future application procedures occur at predictable, regularly occurring intervals unless extraordinary circumstances justify a pause.[4][3]
  • Latin script diacritics: Questions about how Latin-script labels that use diacritic characters (for example, á, ç, ğ, ł, ñ, ś, ů) should be handled at the top and second levels, and what rules should govern their relationship to ASCII-only equivalents. A dedicated Policy Development Process on Latin Script Diacritics was initiated by the GNSO Council in 2024, reflecting concerns about end-user confusion, Universal Acceptance, and interoperability between ASCII and diacritic variants. Although this PDP is not a formal dependency for opening the 2026 round, its outcomes are expected to influence how future Latin-script IDN gTLDs and their second-level registrations are treated.[3] [28]

Timeline

edit
  • 2012: First New gTLD Program application round opens and closes; evaluation, objections, contention, and contracting continue over subsequent years.
  • 2015: GNSO initiates the SubPro PDP.[29]
  • February 2021: SubPro Final Report delivered; GNSO Council transmits consensus outputs to the ICANN Board.[4]
  • 2022: ICANN org completes the SubPro Operational Design Assessment (ODA).[29]
  • July 2023: ICANN publishes the Next Round Implementation Plan.[6]
  • November 19 2024: Applicant Support Program opens.[22]
  • November 19, 2024 to May 20, 2025: RSP Pre-Evaluation period runs.[15]
  • November 3, 2025: ICANN announces Board adoption of the 2026 Round Applicant Guidebook, directing publication no later than 30 December 2025.[10]
  • December 16, 2025: Final AGB (V1-2025.12.16) is published.[1][11]
  • April 30, 2026: Application submission period opens no later than 23:59 UTC (per AGB).
  • August 12, 2026: Application submission period closes at 23:59 UTC (105 days after opening).[1]

References

edit
  1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 New gTLD Program: 2026 Round Applicant Guidebook (V1-2025.12.16), ICANN, published 16 December 2025, retrieved January 30, 2026.
  2. ↑ ICANN New gTLD Program Next Round: About the Program Retrieved August 8, 2025
  3. ↑ 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 ICANN: History of the New gTLD Program Retrieved December 1, 2025
  4. ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 ICANN GNSO: Final Report on the new gTLD Subsequent Procedures Policy Development Process Retrieved December 1, 2025
  5. ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 ICANN GAC: New gTLD Program Next Round Retrieved December 1, 2025
  6. ↑ 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 ICANN: The New gTLD Program Next Round Implementation Plan Retrieved December 1, 2025
  7. ↑ 7.0 7.1 7.2 7.3 7.4 7.5 ICANN: Next Round gTLD Reports Retrieved December 2, 2025
  8. ↑ ICANN Announcements: ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch Retrieved December 2, 2025
  9. ↑ 9.0 9.1 9.2 Cite error: Invalid <ref> tag; no text was provided for refs named q1-2025
  10. ↑ 10.0 10.1 ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch, ICANN, published 3 November 2025, retrieved 30 January 2026.
  11. ↑ 11.0 11.1 A Year of Progress on the Path to Opening the 2026 Round of New gTLDs, ICANN Blog, published 22 December 2025, retrieved 30 January 2026.
  12. ↑ 12.0 12.1 12.2 12.3 12.4 12.5 ICANN New gTLD Program Next Round: Next Round FAQs Retrieved December 1, 2025.
  13. ↑ ICANN: Root Zone Label Generation Rules Retrieved December 3, 2025
  14. ↑ ICANN: Proposals for Root Zone Label Generation Ruleset, ICANN, retrieved December 3, 2025.
  15. ↑ 15.0 15.1 15.2 Registry Service Provider Evaluation Program, ICANN New gTLD Program website, retrieved January 30, 2026.
  16. ↑ 16.0 16.1 Introduction to the 2026 Round ICANN, retrived February 2, 2026
  17. ↑ 17.0 17.1 ICANN Publishes Initial List of Evaluated RSPs for 2026 Round ICANN.org, retrived February 2, 2026
  18. ↑ 18.0 18.1 18.2 ICANN: New gTLD Program: Next Round Retrieved December 2, 2025.
  19. ↑ ICANN New gTLD Next Round: Next Round Champions Toolkit Retrieved December 3, 2025.
  20. ↑ 20.0 20.1 20.2 ICANN New gTLD Program Next Round: Applicant Support Program Retrieved December 2, 2025.
  21. ↑ 21.0 21.1 21.2 21.3 Cite error: Invalid <ref> tag; no text was provided for refs named status-2024
  22. ↑ 22.0 22.1 Cite error: Invalid <ref> tag; no text was provided for refs named asp
  23. ↑ 23.0 23.1 Cite error: Invalid <ref> tag; no text was provided for refs named rsp-program
  24. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named update-2025
  25. ↑ 25.0 25.1 ICANN Public Comment: Closed - String Similarity Review Guidelines Retrieved December 2, 2025
  26. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named string-sim-data
  27. ↑ ICANN Annoucements: ICANN RFI - New gTLD Program Next Round Auctions Retrieved December 2, 2025
  28. ↑ ICANN GNSO: Final Issue Report on a Policy Development Process for Latin Script Diacritics Retrieved December 3, 2025
  29. ↑ 29.0 29.1 Cite error: Invalid <ref> tag; no text was provided for refs named history-newgtlds

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Security and Stability Advisory Committee. Advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems (ICANN Bylaws).

Retrieved from "https://staging.icannwiki.org/index.php?title=New_gTLD_Program:_Next_Round&oldid=1400802"