2026 Round Applicant Guidebook: Difference between revisions

Line 13:

In this stage, applicants confirm eligibility, understand applicable fees, agree to program terms and conditions. ICANN will not accept or advance an application unless the applicant is legally eligible, has paid all required fees on time, and can demonstrate the financial and operational capability to run a stable and secure registry.<ref name="video">[https://icann.zoom.us/rec/play/h8aCQ554RhMAuTw9-kn9Wq2o3v7x4ZLzvgCcx2PHsXPhHgpXNi8qJYc-vgN6giBMXUPOsF0--afJeHp1.M9V0kfumFMdN6sZT?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%2FRBAqLTxkxwItfcV2c1h4ynF5YJj7aEYzcQ5-_08We4eO6LrN1zF_6OzZHD9mgU3s.en_L-K4VBYVh3iVy ICANN: 2026 Round Applicant Journey Overview] Retrieved February 4, 2026</ref> Also, applications must be submitted with a ''bona fide'' intent to operate the gTLD.

The applicant must create an ICANN account, gather required documentation, and prepare the technical, operational, and financial information needed for the application.<ref name="video"></ref> The application than must be submitted electronically through the TLD Application Management System (TAMS).<ref name="agb" />

The applicant must create an ICANN account, gather required documentation, and prepare the technical, operational, and financial information needed for the application.<ref name="video"></ref> The application than must be submitted electronically through the TLD Application Management System (TAMS).<ref name="agb" /> TAMS is a secure online system used by applicants, ICANN, and evaluation panels to submit and manage niche utility applications, monitor application progress, track payment information, communicate about a specific application, provide clarifications, request changes to application content, and receive critical notifications related to applications.<ref name="video"></ref>

===== Fees =====

Line 48:

The different types of applications include the following: General, Community, Geographic Name, Reserved Name, .Brand TLD, Internationalized Domain Name (IDN), Variant of Existing gTLD, Primary IDN TLD including one or more Variants, Category 1 Safeguard, and applications from governments, IGOs, and supported applicants (Government/IGO Applicant and Applicant Support application types).

Each application is for one ~~applied-~~for ~~gTLD~~ string. For IDN strings, an application may also include one or more allocatable variant strings (where such variants exist under the [[Root Zone Label Generation Rules]]). The AGB also allows the registry operator of an existing gTLD to apply for one or more allocatable variant strings of that existing gTLD. ~~For details, see [[#IDNs and variant strings|IDNs and variant strings]].<ref name="agb" />~~

Each application is for one gTLD string.<ref name="agb" /> In order to potentially reduce the instances for contention, applicants can designate a replacement string alongside their original choice. The replacement string may contain different characteristics than the original string.<ref name="video"></ref> For IDN strings, an application may also include one or more allocatable variant strings (where such variants exist under the [[Root Zone Label Generation Rules]]). The AGB also allows the registry operator of an existing gTLD to apply for one or more allocatable variant strings of that existing gTLD.

Geographic Names, IDN TLDs, Reserved Names, and Strings Subject to Category 1 Safeguards strings will initiate specific processing and evaluation procedures. In the AGB, Category 1 Safeguards are implemented through mandatory Safeguard Public Interest Commitments (Safeguard PICs) assigned based on the applied-for string's safeguard group and incorporated into Specification 11 of the Base Registry Agreement.~~<ref name="agb" />~~

Geographic Names, IDN TLDs, Reserved Names, and Strings Subject to Category 1 Safeguards strings will initiate specific processing and evaluation procedures. In the AGB, Category 1 Safeguards are implemented through mandatory Safeguard Public Interest Commitments (Safeguard PICs) assigned based on the applied-for string's safeguard group and incorporated into Specification 11 of the Base Registry Agreement.

At the moment, Closed Generics, 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", are not accepted.

At the moment, Closed Generics, 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", are not accepted.<ref name="agb" />

=== Pre-Submission String Validations ===

Line 67:

Applicants can submit their application without selecting an RSP, although it is engouraged they do. However, they will need to provide that information later through application change requests before Application Evaluation.<ref name="agb" /><ref name="video"></ref>

=== Pre-Evaluation Processes ===

Following the close of the application submission period, ICANN will review the list of submitted applications and place applications for identical strings into contention sets in preparation for Reveal Day. The administrative check is expected to be completed for all applications in a period of approximately eight weeks, subject to the overall application volume.

ICANN expects to publish the list of all applications that have passed the Administrative Check on Reveal Day no later than nine weeks following the close of the application submission period. This list, which will be posted on the New gTLD Program website, will include the relevant applied-for strings and any variant and replacement strings, if applicable. The public portions of each application will also be made available. A list of contention sets containing applications for identical strings will also be published on the website.

==== Replacement Period ====

Once applicants have access to the full list of applied-for strings, as well as any variant strings and replacement strings, they will have the opportunity to replace their applied-for string with their replacement string. Applicants that have selected an eligible replacement string will have a 14-day Replacement Period to notify ICANN via TAMS of their intention to replace their original applied-for string with the replacement string identified in their application.

==== String Confirmation Day ====

On String Confirmation Day, ICANN will post an updated list of applications and their chosen strings, whether original or replacement.

==== Prioritization Draw ====

A Prioritization Draw is expected to be held no later than 30 days after String Confirmation Day. The Draw will determine the Priority Number of an application and the general order in which it will be processed by ICANN.

==== Community Input ====

Starting on String Confirmation Day, the community will have the opportunity to provide input. Comments shall be posted on the Application Comment Forum (ACF), allowing all interested parties, including applicants, to review and comment on the applications.

To submit a comment, commenters will need to have an ICANN Account. They will also be asked to indicate their affiliation and whether they have a relationship with any applicants or applications. In addition, commenters will be required to specify the applications, strings, and specific evaluations and processes to which their comments relate.

If commenters believe they have information related to confidential portions of an application that may not be appropriate to submit publicly, they can opt to submit a confidential comment. This confidential comment will only be visible to ICANN, the applicant, and evaluators. To ensure transparency, this option can only be used for comments related to confidential portions of the application.

== References ==

@@ Line 13: / Line 13: @@
 In this stage, applicants confirm eligibility, understand applicable fees, agree to program terms and conditions. ICANN will not accept or advance an application unless the applicant is legally eligible, has paid all required fees on time, and can demonstrate the financial and operational capability to run a stable and secure registry.<ref name="video">[https://icann.zoom.us/rec/play/h8aCQ554RhMAuTw9-kn9Wq2o3v7x4ZLzvgCcx2PHsXPhHgpXNi8qJYc-vgN6giBMXUPOsF0--afJeHp1.M9V0kfumFMdN6sZT?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%2FRBAqLTxkxwItfcV2c1h4ynF5YJj7aEYzcQ5-_08We4eO6LrN1zF_6OzZHD9mgU3s.en_L-K4VBYVh3iVy ICANN: 2026 Round Applicant Journey Overview] Retrieved February 4, 2026</ref> Also, applications must be submitted with a ''bona fide'' intent to operate the gTLD.
-The applicant must create an ICANN account, gather required documentation, and prepare the technical, operational, and financial information needed for the application.<ref name="video"></ref> The application than must be submitted electronically through the TLD Application Management System (TAMS).<ref name="agb" />
+The applicant must create an ICANN account, gather required documentation, and prepare the technical, operational, and financial information needed for the application.<ref name="video"></ref> The application than must be submitted electronically through the TLD Application Management System (TAMS).<ref name="agb" /> TAMS is a secure online system used by applicants, ICANN, and evaluation panels to submit and manage niche utility applications, monitor application progress, track payment information, communicate about a specific application, provide clarifications, request changes to application content, and receive critical notifications related to applications.<ref name="video"></ref>
 ===== Fees =====
@@ Line 48: / Line 48: @@
 The different types of applications include the following: General, Community, Geographic Name, Reserved Name, .Brand TLD, Internationalized Domain Name (IDN), Variant of Existing gTLD, Primary IDN TLD including one or more Variants, Category 1 Safeguard, and applications from governments, IGOs, and supported applicants (Government/IGO Applicant and Applicant Support application types).
-Each application is for one applied-for gTLD string. For IDN strings, an application may also include one or more allocatable variant strings (where such variants exist under the [[Root Zone Label Generation Rules]]). The AGB also allows the registry operator of an existing gTLD to apply for one or more allocatable variant strings of that existing gTLD. For details, see [[#IDNs and variant strings|IDNs and variant strings]].<ref name="agb" />
+Each application is for one gTLD string.<ref name="agb" /> In order to potentially reduce the instances for contention, applicants can designate a replacement string alongside their original choice. The replacement string may contain different characteristics than the original string.<ref name="video"></ref> For IDN strings, an application may also include one or more allocatable variant strings (where such variants exist under the [[Root Zone Label Generation Rules]]). The AGB also allows the registry operator of an existing gTLD to apply for one or more allocatable variant strings of that existing gTLD.
-Geographic Names, IDN TLDs, Reserved Names, and Strings Subject to Category 1 Safeguards strings will initiate specific processing and evaluation procedures. In the AGB, Category 1 Safeguards are implemented through mandatory Safeguard Public Interest Commitments (Safeguard PICs) assigned based on the applied-for string's safeguard group and incorporated into Specification 11 of the Base Registry Agreement.<ref name="agb" />
+Geographic Names, IDN TLDs, Reserved Names, and Strings Subject to Category 1 Safeguards strings will initiate specific processing and evaluation procedures. In the AGB, Category 1 Safeguards are implemented through mandatory Safeguard Public Interest Commitments (Safeguard PICs) assigned based on the applied-for string's safeguard group and incorporated into Specification 11 of the Base Registry Agreement.
-At the moment, Closed Generics, 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", are not accepted.
+At the moment, Closed Generics, 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", are not accepted.<ref name="agb" />
 === Pre-Submission String Validations ===
@@ Line 67: / Line 67: @@
 Applicants can submit their application without selecting an RSP, although it is engouraged they do. However, they will need to provide that information later through application change requests before Application Evaluation.<ref name="agb" /><ref name="video"></ref>
+=== Pre-Evaluation Processes ===
+Following the close of the application submission period, ICANN will review the list of submitted applications and place applications for identical strings into contention sets in preparation for Reveal Day. The administrative check is expected to be completed for all applications in a period of approximately eight weeks, subject to the overall application volume.
+ICANN expects to publish the list of all applications that have passed the Administrative Check on Reveal Day no later than nine weeks following the close of the application submission period. This list, which will be posted on the New gTLD Program website, will include the relevant applied-for strings and any variant and replacement strings, if applicable. The public portions of each application will also be made available. A list of contention sets containing applications for identical strings will also be published on the website.
+==== Replacement Period ====
+Once applicants have access to the full list of applied-for strings, as well as any variant strings and replacement strings, they will have the opportunity to replace their applied-for string with their replacement string. Applicants that have selected an eligible replacement string will have a 14-day Replacement Period to notify ICANN via TAMS of their intention to replace their original applied-for string with the replacement string identified in their application.
+==== String Confirmation Day ====
+On String Confirmation Day, ICANN will post an updated list of applications and their chosen strings, whether original or replacement.
+==== Prioritization Draw ====
+A Prioritization Draw is expected to be held no later than 30 days after String Confirmation Day. The Draw will determine the Priority Number of an application and the general order in which it will be processed by ICANN.
+==== Community Input ====
+Starting on String Confirmation Day, the community will have the opportunity to provide input. Comments shall be posted on the Application Comment Forum (ACF), allowing all interested parties, including applicants, to review and comment on the applications.
+To submit a comment, commenters will need to have an ICANN Account. They will also be asked to indicate their affiliation and whether they have a relationship with any applicants or applications. In addition, commenters will be required to specify the applications, strings, and specific evaluations and processes to which their comments relate.
+If commenters believe they have information related to confidential portions of an application that may not be appropriate to submit publicly, they can opt to submit a confidential comment. This confidential comment will only be visible to ICANN, the applicant, and evaluators. To ensure transparency, this option can only be used for comments related to confidential portions of the application.
 == References ==