New gTLD Program: Next Round: Difference between revisions

Inf; information update
information update; general fixes
 
(14 intermediate revisions by the same user not shown)
Line 9: Line 9:
== Background ==
== Background ==


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.
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.<ref name="history-new-gtld">[https://www.icann.org/resources/pages/newgtlds-history-2023-04-05-en ICANN: History of the New gTLD Program] Retrieved December 1, 2025</ref> 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 across more than forty topics.<ref name="subpro-final">[https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf ICANN GNSO: Final Report on the new gTLD Subsequent Procedures Policy Development Process] Retrieved December 1, 2025</ref>
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.<ref name="history-new-gtld">[https://www.icann.org/resources/pages/newgtlds-history-2023-04-05-en ICANN: History of the New gTLD Program] Retrieved December 1, 2025</ref> 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.<ref name="subpro-final">[https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf ICANN GNSO: Final Report on the new gTLD Subsequent Procedures Policy Development Process] Retrieved December 1, 2025</ref>


On February 18, 2021, the GNSO Council approved all SubPro outputs that achieved "Full Consensus" or "Consensus" and transmitted them to the ICANN Board.<ref name="history-new-gtld" /> In 2023, the Board adopted ninety-eight of the recommendations and marked thirty-eight as pending while it consulted further with the GNSO and the GAC.<ref name="gac-next-round">[https://gac.icann.org/activity/new-gtld-program-next-round ICANN GAC: New gTLD Program Next Round] Retrieved December 1, 2025</ref> The Board also requested an implementation plan from ICANN org describing how a subsequent round could be operationalized.<ref name="impl-plan-2023">[https://newgtlds.icann.org/sites/default/files/new-gtld-next-round-implementation-plan-31jul23-en.pdf ICANN: The New gTLD Program Next Round Implementation Plan] Retrieved December 1, 2025</ref>  
On February 18, 2021, the GNSO Council approved all SubPro outputs that achieved "Full Consensus" or "Consensus" and transmitted them to the ICANN Board.<ref name="history-new-gtld" /> 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.<ref name="history-new-gtld" />
 
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.<ref name="gac-next-round">[https://gac.icann.org/activity/new-gtld-program-next-round ICANN GAC: New gTLD Program Next Round] Retrieved December 1, 2025</ref> 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.<ref name="impl-plan-2023">[https://newgtlds.icann.org/sites/default/files/new-gtld-next-round-implementation-plan-31jul23-en.pdf ICANN: The New gTLD Program Next Round Implementation Plan] Retrieved December 1, 2025</ref>
 
== Implementation Governance ==
 
=== SubPro Implementation Review Team ===
 
To help ensure fidelity to the policy recommendations, the GNSO Council chartered the [[Subsequent Procedures IRT|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.<ref name="impl-plan-2023" /><ref name="next-round-reports" />
 
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 [[2026 Round Applicant Guidebook|Applicant Guidebook]] text, and related implementation topics are discussed.<ref name="next-round-reports">[https://newgtldprogram.icann.org/en/reports ICANN: Next Round gTLD Reports] Retrieved December 2, 2025</ref>
 
=== ICANN Oversight ===
 
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.<ref name="board-agb-2025">[https://www.icann.org/en/announcements/details/icann-board-adopts-next-round-applicant-guidebook-clears-path-to-2026-launch-03-11-2025-en ICANN Announcements: ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch] Retrieved December 2, 2025</ref> 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.<ref name="impl-plan-2023" /> <ref name="q1-2025"></ref>
 
== Applicant Guidebook and ICANN Board Adoption ==
 
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.<ref name="agb" />
 
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).<ref name="board-agb-announcement">[https://www.icann.org/en/announcements/details/icann-board-adopts-next-round-applicant-guidebook-clears-path-to-2026-launch-03-11-2025-en ''ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch''], ICANN, published 3 November 2025, retrieved 30 January 2026.</ref> The final AGB (V1-2025.12.16) was published on 16 December 2025.<ref name="agb" /><ref name="year-progress">[https://www.icann.org/en/blogs/details/a-year-of-progress-on-the-path-to-opening-the-2026-round-of-new-gtlds-22-12-2025-en ''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.</ref>


== Policy Framework ==
== Policy Framework ==
Line 25: Line 45:
=== Applicant Types and TLD Categories ===
=== Applicant Types and TLD Categories ===


The Working Group confirms that some applications may receive differentiated treatment based on the nature of the application, the applied-for string, or the applicant. In practice, this preserves and refines the main categories from the 2012 round (standard, community-based, geographic, and .Brand TLDs) and links them to specific differences in eligibility, evaluation questions, contention rules, and contractual models. For example, community-based applications may be eligible for Community Priority Evaluation, geographic names are subject to additional questions and governmental input, .Brand TLDs may continue to use a tailored Registry Agreement, and eligible applicants may seek fee reductions and other benefits under the Applicant Support Program.<ref name="subpro-final" />
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.<ref name="subpro-final" /><ref name="agb" />


=== String Similarity ===
=== String Similarity ===


On string similarity, the Working Group reaffirms the 2007 policy that applied-for strings must not be confusingly similar to existing TLDs or reserved names. One of the most visible updates for the Next Round concerns plurals and singulars: SubPro recommends prohibiting delegation of singular and plural versions of the same word in the same language or script (for example, “.example” and “.examples”) in order to reduce the risk of user confusion.
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:


In limited cases where two applied-for strings would normally be treated as a singular/plural pair but the applicants can demonstrate genuinely different intended meanings, both applications may proceed only if each applicant accepts a mandatory Public Interest Commitment (PIC) in its Registry Agreement. That commitment must state the intended use of the TLD and require registrants to use second-level domains in line with that stated purpose (for example, distinguishing clearly between a string used for a season and one used for a manufactured object).<ref name="subpro-final" />
* 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.<ref name="agb" />


=== Applicant Freedom and Safeguards ===
=== Applicant Freedom and Safeguards ===


SubPro looked for a balance regarding to applicant freedom of expression with safeguards related to DNS Abuse, public interest commitments, and protections for specific categories of strings.
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).<ref name="subpro-final" /><ref name="agb" />
 
The Working Group reaffirmed Principle G from the 2007 policy, which states: "The string evaluation
process must not infringe the applicant’s freedom of expression rights that are protected under internationally recognized principles of law." Also, The WG further affirmed Recommendation 3: "Strings must not infringe the existing legal rights of others that are recognized or enforceable under generally accepted and internationally recognized principles of law. Examples of these legal rights that are internationally recognized include, but are not limited to, rights defined in the Paris Convention for the Protection of Industrial Property (in particular trademark rights), the Universal Declaration of Human Rights and the International Covenant on Civil and Political Rights (in
particular freedom of speech rights)." Nevertheless, it should be taken into consideration the applicant's freedom of expression rights in the TLD proposed during pre-application through delegation
stages of the process.<ref name="subpro-final" />
 
=== Applicant Support Program  ===
 
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.<ref name="subpro-final" />
 
=== Registry Service Provider Pre-evaluation ===
 
The topic of Registry Service Provider Pre-evaluation introduces a standing RSP pre-evaluation process, open to both incumbent and new back-end operators, through which providers can be assessed against technical and operational criteria prior to an application round. Pre-evaluated RSPs are then listed for use by applicants, with SubPro specifying that each round requires a fresh evaluation or streamlined reassessment, and clarifying that participation in the program does not in itself make an RSP a “contracted party” of ICANN.<ref name="subpro-final" />


=== IDNs and Variants ===
=== IDNs and Variants ===
Line 58: Line 68:
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".<ref name="next-round-faqs" /><ref name="lgr-procedure">[https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en ICANN: Proposals for Root Zone Label Generation Ruleset], ICANN, retrieved December 3, 2025.</ref>
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".<ref name="next-round-faqs" /><ref name="lgr-procedure">[https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en ICANN: Proposals for Root Zone Label Generation Ruleset], ICANN, retrieved December 3, 2025.</ref>


=== Closed Generics and IDN Policy Dependencies ===
=== Closed Generics ===
 
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.<ref name="gac-next-round" /> The AGB maintains this position.<ref name="agb" />


Closed generics 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.<ref name="gac-next-round" />
=== IDN Policy Dependencies ===


The [[EPDP on Internationalized Domain Names|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.<ref name="history-new-gtld" />
The [[EPDP on Internationalized Domain Names|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.<ref name="history-new-gtld" />


== Operational Design and Implementation Plan ==
== Applicant Support Program  ==


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 [https://www.icann.org/en/system/files/files/subpro-oda-12dec22-en.pdf Operational Design Assessment (ODA)] was delivered to the ICANN Board in late 2022.<ref name="history-new-gtld" />
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.<ref name="subpro-final" />
 
On July 31,2023, ICANN org published the [https://newgtlds.icann.org/sites/default/files/new-gtld-next-round-implementation-plan-31jul23-en.pdf New gTLD Program: Next Round Implementation Plan], which decomposes the program into multiple projects, including program foundations, systems and tools, the Applicant Support Program, the RSP Evaluation Program, application processing, evaluation, objections, contention resolution, contracting, and post-contracting operations.<ref name="impl-plan-2023" /> The plan also includes detailed timelines for each project and identifies dependencies on parallel community work, such as IDN policy and closed generics.<ref name="impl-plan-2023" />


Subsequent status updates, including a February 2024 Implementation Status Update and periodic blogs, have tracked progress against the plan, highlighting milestones such as the launch of support and RSP programs and the development of application systems.<ref name="status-2024">[https://www.icann.org/en/system/files/files/status-update-new-gtld-program-next-round-20feb24-en.pdf ICANN: Pre-ICANN79 Status Update: New gTLD Program: Next Round | February 2024] Retrieved December 1, 2025</ref> <ref name="q1-2025">[https://www.icann.org/en/blogs/details/first-quarter-update-on-the-new-gtld-program-next-round-24-02-2025-en ICANN Blogs: First Quarter Update on the New gTLD Program: Next Round] Retrieved December 1, 2025</ref> <ref name="update-2025">[https://www.icann.org/en/blogs/details/update-on-new-gtld-program-next-round-27-05-2025-en ICANN Blogs: Update on New gTLD Program: Next Round] Retrieved December 1, 2025</ref>
== Registry Service Provider Evaluation Program ==


=== SubPro Implementation Review Team ===
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.<ref name="agb" /><ref name="rsp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/rsp ''Registry Service Provider Evaluation Program''], ICANN New gTLD Program website, retrieved January 30, 2026.</ref> <ref name="introvideoone">[https://icann.zoom.us/rec/play/U5KqJzPA6hn7Gw2YNcoDpsoPFMi3TBMZa_lYy-g9XY6roINkZzyBZoDIvll77gd1Z1aya2tWtqAzM0-R.W1RJmCOidXPWcbBR?eagerLoadZvaPages=sidemenu.billing.plan_management&accessLevel=meeting&canPlayFromShare=true&from=share_recording_detail&continueMode=true&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2F-6gDqW0GyDlxscoQuyfPTY7Czs8V9iSIfmipWNSSG3TVVFHIwOFu_pVoGRp7fhQj.MxTJyhSDYk2zcqs3 ''Introduction to the 2026 Round''] ICANN, retrived February 2, 2026</ref>


To help ensure fidelity to the policy recommendations, the GNSO Council chartered the [[Subsequent Procedures IRT|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.<ref name="impl-plan-2023" /><ref name="next-round-reports" />
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.<ref name="rsp">[https://www.icann.org/en/announcements/details/icann-publishes-initial-list-of-evaluated-rsps-for-2026-round-30-01-2026-en '''ICANN Publishes Initial List of Evaluated RSPs for 2026 Round'''] ICANN.org, retrived February 2, 2026</ref>


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 [[2026 Round Applicant Guidebook|Applicant Guidebook]] text, and related implementation topics are discussed.<ref name="next-round-reports">[https://newgtldprogram.icann.org/en/reports ICANN: Next Round gTLD Reports] Retrieved December 2, 2025</ref>
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.<ref name="introvideoone"></ref>


=== ICANN Oversight ===
The List of Evaluated RSPs will be updated on an ongoing basis as ICANN continues to test and qualify providers.<ref name="rsp"></ref>
 
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.<ref name="board-agb-2025">[https://www.icann.org/en/announcements/details/icann-board-adopts-next-round-applicant-guidebook-clears-path-to-2026-launch-03-11-2025-en ICANN Announcements: ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch] Retrieved December 2, 2025</ref> 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.<ref name="impl-plan-2023" /> <ref name="q1-2025"></ref>
 
== Program Architecture ==
 
The Next Round program architecture combines multiple components and systems that together enable the application and evaluation process.
 
=== Applicant Guidebook ===
 
The "Applicant Guidebook (AGB)" sets out the detailed rules, criteria, and procedures for applying for and operating a new gTLD. For the 2026 round, the AGB is expected to incorporate the adopted SubPro recommendations, updated contractual language, revised objection and contention processes, and new material on IDNs, RSP pre-evaluation, and support mechanisms. The Applicant Guidebook for the 2026 round is being developed through the SubPro Implementation Review Team (IRT) process and iterative drafts. ICANN published a draft version of the Next Round Applicant Guidebook for Public Comment on May 30, 2025 and has indicated that it expects to publish the final version by December 2025, ahead of the projected 2026 application window.
 
The Applicant Guidebook for the 2026 round was adopted by the ICANN Board at ICANN 84 on November 3, 2025, following more than 250 hours of Implementation Review Team meetings and five Public Comment proceedings on successive drafts. As stipulated by the community, the AGB must be available at least four months before the application window opens. In its ICANN84 resolution, the Board directed ICANN org to publish the final AGB text no later than 30 December 30, 2025 and authorized only insignificant changes while org aligns Dispute Resolution Service Provider rules and performs final consistency checks.<ref name="board-agb-2025" /> <ref name="agb-home">[https://newgtldprogram.icann.org/en/application-rounds/round2/agb ICANN New gTLD Program Next Round: Applicant Guidebook Homepage] Retrieved December 2, 2025</ref>
 
=== Program Costs and Evaluation Fees ===
 
ICANN has set an expected evaluation fee of USD 227,000 for applications in the 2026 round of the New gTLD Program.<ref name="blog">[https://www.icann.org/en/blogs/details/icann-sets-expected-evaluation-fee-for-new-gtld-applications-in-the-next-round-25-09-2024-en ICANN Blogs: ICANN Sets Expected Evaluation Fee for New gTLD Applications in the Next Round] Retrieved August 8, 2025</ref> While the fee will not be formally confirmed until the ICANN Board approves the Applicant Guidebook for the Next Round, publishing the expected amount is intended to give prospective applicants a concrete basis for business planning and decision-making.
 
The expected fee level reflects program-related decisions taken at the ICANN Board workshop of September 6-8, 2024 in Los Angeles, including adoption of the remaining Internationalized Domain Names Expedited Policy Development Process Phase 1 recommendation on application fees and Security and Stability Advisory Committee advice related to Name Collision Analysis.<ref name="blog" /> Consistent with the GNSO Subsequent Procedures Final Report, the fee is set on a cost-recovery basis: it is intended to cover the full costs of running the New gTLD Program and to be revenue-neutral, so that the round is not subsidized by existing ICANN funding sources such as gTLD registry and registrar fees, ccTLD contributions, or Regional Internet Registry contributions. <ref>[https://newgtldprogram.icann.org/en/resources/gtld-evaluation-fee-faqs ICANN New gTLD Program Next Round: gTLD Evaluation Fee Frequently Asked Questions] Retrieved August 8, 2025</ref>
 
The gTLD evaluation fee does not include charges for elective conditional evaluations, which are assessed separately. Conditional evaluations are optional assessments that an applicant may request in order to obtain specific statuses or treatment, such as Community Priority Evaluation for community-based applications or eligibility for the .Brand TLD model.<ref name="blog" />
 
=== Systems and Tools ===
 
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.<ref name="impl-plan-2023" />
 
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.<ref name="next-round-landing">[https://newgtldprogram.icann.org/en/application-rounds/round2 ICANN: New gTLD Program: Next Round] Retrieved December 2, 2025.</ref> <ref name="next-round-faqs" />


== Outreach and Communications ==
== Outreach and Communications ==
Line 121: Line 105:
The Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants, particularly those from underserved regions or with limited resources.<ref name="asp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/asp ICANN New gTLD Program Next Round: Applicant Support Program] Retrieved December 2, 2025.</ref> 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.<ref name="status-2024" />
The Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants, particularly those from underserved regions or with limited resources.<ref name="asp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/asp ICANN New gTLD Program Next Round: Applicant Support Program] Retrieved December 2, 2025.</ref> 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.<ref name="status-2024" />


The ASP opened in late 2024 and accepted applications for support until November 2025.<ref name="q1-2025" /><ref name="asp-page" />
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).<ref name="asp" /><ref name="asp-extension">[https://www.icann.org/en/announcements/details/icann-extends-deadline-for-applicant-support-program-06-10-2025-en ''ICANN Extends Deadline for Applicant Support Program''], ICANN, published 6 October 2025, retrieved 30 January 2026


=== IDNs and Applicant Support ===
=== IDNs and Applicant Support ===
Line 131: Line 115:
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.<ref name="next-round-reports" />
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.<ref name="next-round-reports" />


== RSP Evaluation Program ==
== Registry Service Provider Evaluation Program ==
 
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.<ref name="agb" /><ref name="rsp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/rsp ''Registry Service Provider Evaluation Program''], ICANN New gTLD Program website, retrieved January 30, 2026.</ref>
 
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.<ref name="rsp-program" /><ref name="update-2025" /> RSPs that successfully complete evaluation are listed on a dedicated page for use by prospective applicants.<ref name="rsp-program" /> Through the program, RSPs may only need to be evaluated once for the 2026 Round regardless of the number of gTLDs they support.<ref name="agb" />
 
== Systems and Tools ==


The "Registry Service Provider (RSP) Evaluation Program" pre-evaluates registry back-end operators against technical and operational criteria so that new gTLD applicants can select from a list of approved providers rather than each undergoing a full technical review.<ref name="rsp-program">[https://www.icann.org/en/announcements/details/icann-opens-new-gtld-registry-service-provider-evaluation-program-19-11-2024-en ICANN Announcements: ICANN Opens New gTLD Registry Service Provider Evaluation Program] Retrieved December 2, 2025</ref> <ref name="impl-plan-2023" />
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.<ref name="impl-plan-2023" />


The program includes two evaluation periods: an initial pre-application period from November 2024 to May 2025, and a second period aligned with the 2026 application window.<ref name="rsp-program" /><ref name="update-2025" /> RSPs that successfully complete evaluation are listed on a dedicated page for use by prospective applicants.<ref name="rsp-program" />
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.<ref name="next-round-landing">[https://newgtldprogram.icann.org/en/application-rounds/round2 ICANN: New gTLD Program: Next Round] Retrieved December 2, 2025.</ref> <ref name="next-round-faqs" />


== Applicant Journey ==
== Applicant Journey ==


=== Pre-Application Phase ===
=== Pre-Submission ===


In the pre-application 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.<ref name="next-round-landing" /><ref name="next-round-reports" />
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.<ref name="next-round-landing" /><ref name="next-round-reports" />


Applicants requiring financial or capacity support are encouraged to apply to the Applicant Support Program sufficiently in advance of the main application window.<ref name="asp-page" /><ref name="q1-2025" />
Applicants requiring financial or capacity support are encouraged to apply to the Applicant Support Program sufficiently in advance of the main application window.<ref name="asp-page" /><ref name="q1-2025" />
Line 147: Line 137:
=== Application Submission ===
=== Application Submission ===


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.<ref name="next-round-faqs" /><ref name="impl-plan-2023" />
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.<ref name="next-round-faqs" /><ref name="impl-plan-2023" /> 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.<ref name="agb" />
 
Application fees are set on a cost-recovery basis for the program and are published in the AGB and related fee documentation.<ref name="next-round-faqs" />


=== Evaluation ===
=== Evaluation ===
Line 202: Line 190:
== Timeline ==
== Timeline ==


The following high-level milestones summarize the path toward the Next Round:
* 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.<ref name="history-newgtlds" />
* 2012: First New gTLD Program application round opens and later closes; evaluation, objections, contention, and contracting processes continue over several years.
* February 2021: SubPro Final Report delivered; GNSO Council transmits consensus outputs to the ICANN Board.<ref name="subpro-final" />
* 2015–2016: GNSO initiates the SubPro PDP; Working Group begins its deliberations.<ref name="history-new-gtld" />
* 2022: ICANN org completes the SubPro Operational Design Assessment (ODA).<ref name="history-newgtlds" />
* February 2021: SubPro Final Report delivered; GNSO Council approves its consensus outputs.<ref name="subpro-final" /><ref name="history-new-gtld" />
* July 2023: ICANN publishes the Next Round Implementation Plan.<ref name="impl-plan-2023" />
* 2022: ICANN org completes the Operational Design Assessment of the SubPro recommendations.<ref name="history-new-gtld" />
* November 19 2024: Applicant Support Program opens.<ref name="asp" />
* July 2023: ICANN publishes the New gTLD Program: Next Round Implementation Plan.<ref name="impl-plan-2023" />
* November 19, 2024 to May 20, 2025: RSP Pre-Evaluation period runs.<ref name="rsp-page" />
* 2023–2024: Implementation work continues; ICANN issues status updates, publishes draft implementation materials, and engages with the SubPro IRT.<ref name="status-2024" /><ref name="next-round-reports" />
* November 3, 2025: ICANN announces Board adoption of the 2026 Round Applicant Guidebook, directing publication no later than 30 December 2025.<ref name="board-agb-announcement" />
* Late 2024: ICANN launches the Applicant Support Program and opens the first RSP Evaluation Program window.<ref name="q1-2025" /><ref name="rsp-program" />
* December 16, 2025: Final AGB (V1-2025.12.16) is published.<ref name="agb" /><ref name="year-progress" />
* 2025: Ongoing evaluation of ASP requests and RSP applications; ICANN Board approves the Next Round Applicant Guidebook at ICANN84, to be completed in December.<ref name="q1-2025" /><ref name="board-agb-2025" />
* April 30, 2026: Application submission period opens no later than 23:59 UTC (per AGB).
* 2026: Application window for the 2026 round expected to open in April for 12–15 weeks.<ref name="2026-general">[https://newgtldprogram.icann.org/en/application-rounds/round2/2026-round-general ICANN New gTLD Program Next Round: 2026 Round General Information] Retrieved December 3, 2025</ref> <ref name="globalip-2025">[https://globalipaction.ch/news/the-next-round-new-gtld-is-expected-to-be-open-april-2026/ Global IP Action: The next round new gTLD is expected to be open April 2026] Retrieved December 3, 2025</ref>
* August 12, 2026: Application submission period closes at 23:59 UTC (105 days after opening).<ref name="agb" />


== References ==
== References ==