6. Change Log
This page contains the Change Log for New gTLD Program: 2026 Round, as required per the Predictability Framework. The Framework can be found in Appendix 6 of the 2026 Round Applicant Guidebook.
This page includes the Change Log with the following:
These include grammatical, linguistic, term-consistency, or formatting changes to the Applicant Guidebook.
Type 1: Minor Operational Changes
A minor operational change refers to any modification during the ongoing round of the Program that can be implemented in alignment with the existing Board-approved policy recommendations and does not have a material impact on applicants.
Type 2: Non-Minor Operational Changes
A non-minor operational change is a change during the ongoing round of the Program that can be implemented in alignment with the existing Board-approved policy recommendations and has a material impact on applicants.
A policy change is a change during the ongoing round of the Program that cannot be implemented in alignment with the existing Board-approved policy recommendations. Policy changes for ongoing rounds would only occur in extraordinary circumstances where the Program’s continuation is at risk if the change were not executed.
For PDF versions of this information see here.
Type 0: Typographical Changes
Note: As per the SPIRT Charter, “the SPIRT shall review the decision through the Change Log and take no more than three (3) calendar days to provide guidance if it disagrees with the decision.”
Change # | Date Shared | Effective Date | SPIRT Guidance Due By | Description of Change | Rationale for Change |
|---|---|---|---|---|---|
39 | 11 June 2026 | TBD | 14 June 2026 | Added links to Templates and Instructions related to Financial Evaluation on Application Questions 213-219. | Added links to additional resource. No changes to any information. |
Items below this line were incorporated into the Applicant Guidebook V2-2026.04.24. | |||||
38 | 24 April 2026 | 24 April 2026 | 27 April 2026 | Updated the link in footnote 382 to the exact page on the website. | Update to exact link |
37 | 24 April 2026 | 24 April 2026 | 27 April 2026 | Removed "DRSP Page of the" | Correction. Typographical change. |
36 | 23 April 2026 | 24 April 2026 | 26 April 2026 | Changed several instances in Module 4 and Appendix 3 of “an Panel Determination” to “a Panel Determination” | Corrects typographical error only. |
35 | 23 April 2026 | 24 April 2026 | 26 April 2026 | Article 14(b) of the Objection Procedure was updated to remove "as described in Objection and Appeal Fees and Costs". | Correction. This is described in the DRSP Rules. |
34 | 23 April 2026 | 24 April 2026 | 26 April 2026 | Article 15(b) of the Objection Procedure and Art. 7(d) of the Appeal Procedure were updated to remove "ICANN and". | Correction. ICANN does not need to be in copy. |
33 | 23 April 2026 | 24 April 2026 | 26 April 2026 | Article 15(g) of the Appeal Procedure was updated to reference the correct article. | Correction. Typographical change. |
32 | 9 April 2026 | 24 April 2026 | 12 April 2026 | The link to the 2026 Base Registry agreement was added to Appendix 4; removed footnote on page 9 regarding a placeholder. | The 2026 Base Registry Agreement was adopted by the Board in March 2026. |
31 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Correct language regarding instructions for payments in Section 3.3.6: "Instructions for making a payment will be made available to applicants in TAMS." | Corrects language regarding information on how to make a payment, as this will not be in the system itself |
30 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Add link to Application Question 158: "Is the applied-for string a geographic name as defined by it being any one of the following: a) the capital city name of a country or territory listed in the ISO 3166-1 standard; b) a city name, where it is clear from statements in the application that the applying entity intends to use the gTLD for purposes associated with the city name; c) a sub-national place name listed in the ISO 3166-2 standard; or d) Strings listed as UNESCO regions or appearing on the Geographic Regions section of the “Standard country or area codes for statistical use (M49) (https://unstats.un.org/unsd/methodology/m49/)" | Adds link only for reference purposes for the applicant |
29 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Appendix 1, Question Set 8 Description: "This question set collects information specific to Geographic NamesCommunity gTLDs." | Corrects typographical error only |
28 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Question 109 "Attestations": "I have read and understood the New gTLD Program Eligibility Criteria in Applicant Guidebook Section 6.1.2.1 and declare that neither the applying entity nor any of the individuals named within the Organizational Account Record are subject to any of the above Eligibility Criteria listed in Section 6.1.2.1." | Adds link only for reference purposes for the applicant |
27 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Removed input instructions from Q180; should be yes/no confirmation only. | Corrected instructions for Q180. |
26 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Corrected language in Section 7.7.5.1 regarding the Challenge panel: "A Challenge Panel, consisting of different the same individuals responsible for the initial plan evaluation, shall conduct the challenge review." | Corrected information regarding the challenge panel as per SubPro Policy and Implementation Guidance regarding challenges. |
25 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Updated Glossary with correct definition of Geographic Name, to align with AGB Section 7.5: "A generic top-level domain and its allocatable variant label(s) is a Geographic Name if it meets any of these criteria: It is the name (in any language) of a capital city of any country or territory listed in the ISO3166-1 standard; it is the name of a city or region where the applicant declares that it intends to use the gTLD for purposes associated with that name; it is an exact match of a sub-national place name such as a county, province, or state listed in the ISO3166-2 standard; or of a name listed as a UNESCO region or appearing on the UN Geographic Regions section M49. Each category has different qualifications. See Section 7.5 Geographic Names." | Corrected definition based on AGB Section 7.5 |
24 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Article 14(d) of the Appeal Procedure was updated to specify that it will be the Panel and not the DRSP issuing an Appellate Panel Determination. | Corrected an inconsistency in nomenclature. |
23 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Added "Notes" to Question 180: Notes: | Clarification for applicant regarding a "No" response |
22 | 9 April 2026 | 24 April 2026 | 12 April 2026 | Removed "with copies to ICANN" from the Objection and Appeal Procedures in Appendix 3. | Correction/Clarification. Copies not required to be sent to ICANN. |
21 | 9 April 2026 | 24 April 2026 | 12 April 2026 | In Section A9.3, changed "date of birth" to "year of birth" to align with application questions, where only "year of birth" is required | Corrected an inconsistency. |
20 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update links/references in Application Questions 223 and 224 to the correct section number (5.2.3.1 Prohibited Communications and Activities) and removed the reference in Q223 as it is not relevant/was incorrectly referenced. | Corrects a typo/incorrect reference only. |
19 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update links/references in Section 7.2.1 re: Technical Standards to correct section number (3.1.8.3 DNS Stability Review) | Corrects a typo/incorrect reference only. |
18 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Updated link to exact location of the Data Privacy Policy in Appendix 9: https://newgtldprogram.icann.org/en/privacy-policy. | Updated link only. |
17 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.4.6 Challenges and Extended Evaluation for Code of Conduct Exemption Evaluation" to "7.4.7 Challenges and Extended Evaluation for Code of Conduct Exemption Evaluation" | Corrects a typo/incorrect reference only. |
16 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number 5.1.2 Replacement String Eligibility" to "5.1.1 Replacement String Eligibility" | Corrects a typo/incorrect reference only. |
15 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "5.1.3 Designating a Replacement String" to "5.1.2 Designating a Replacement String" | Corrects a typo/incorrect reference only. |
14 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "5.1.4 Additional Considerations for Designating a Replacement String" to "5.1.3 Additional Considerations for Designating a Replacement String" | Corrects a typo/incorrect reference only. |
13 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "5.1.5 Replacement Period" to 5.1.4 Replacement Period" | Corrects a typo/incorrect reference only. |
12 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "5.1.6 String Confirmation Day" to "5.1.5 String Confirmation Day" | Corrects a typo/incorrect reference only. |
11 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.2.2.2 Reserved Names Identification" to "7.2.2.1 Reserved Names Identification" | Corrects a typo/incorrect reference only. |
10 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.2.2.2.1 Reserved Names Identification Challenge" to "7.2.2.1.1 Reserved Names Identification Challenge | Corrects a typo/incorrect reference only. |
9 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number " 7.2.2.3 Reserved Names Review" to "7.2.2.2 Reserved Names Review" | Corrects a typo/incorrect reference only. |
8 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.2.2.3.1 Exception Process to Apply for Reserved Names" to "7.2.2.2.1 Exception Process to Apply for Reserved Names" | Corrects a typo/incorrect reference only. |
7 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.2.2.3.1.1 Verification of Submitted Documentation" to "7.2.2.2.1.1 Verification of Submitted Documentation" | Corrects a typo/incorrect reference only. |
6 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update heading number "7.2.2.3.2 Extended Evaluation for Reserved Names Review" to "7.2.2.2.2 Extended Evaluation for Reserved Names Review" | Corrects a typo/incorrect reference only. |
5 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update Section 7.7.5.1 for consistency as to deadline for filing a challenge: "To initiate an Evaluation Challenge proceeding, the applicant must file a challenge within 21 days from the date of transmission of the evaluation determination." | Corrects an inconsistency with the existing process only, which is noted in Section 7.7.5.1 as well as in Section 1.2.14.2. |
4 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Update Section 7.10.4 for consistency as to deadline for filing a challenge: "The evaluation challenge can be made within 21 days from the date of transmission of the String Similarity Evaluation determination." | Corrects an inconsistency with the existing process only, which is noted in Section 1.2.14.2. |
3 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Remove typo in Glossary: "Reserved A Names Review" | Corrects a typo/incorrect reference only. |
2 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | In glossary, fixed definition of "gTLD application fee" for accuracy: "The fee due from each applicant to obtain consideration of its application. The fee may consist of a partial deposit and payment of the full fee amount for each application submitted." | Corrects an inconsistency with Section 3.3.1 only. |
1 | 29 Jan 2026 | 24 April 2026 | 1 Feb 2026 | Updated link on Question 120: | Corrects a typo/incorrect reference only. |
Type 1: Minor Operational Changes
Note: As per the SPIRT Charter, “the SPIRT shall review the decision through the Change Log and take no more than three (3) calendar days to provide guidance if it disagrees with the decision.”
Change # | Date Shared | Effective Date | SPIRT Guidance Due By | Description of Change | Rationale for Change |
|---|---|---|---|---|---|
7 | 11 June 2026 | TBD | 14 June 2026 | Clarified instructions regarding file attachments on several application questions in Appendix 1: “File attachments should be according to acceptable file types and size limits set by TAMS.” | Clarification on file attachments in TAMS. |
6 | 11 June 2026 | TBD | 14 June 2026 | Clarified information related to Registry Agreement requirements for existing gTLDs and variants in Sections 3.1.9.2.2, 7.1.2.6, and 7.1.2.7. Example from 3.1.9.2.2: Updated language: "The existing gTLD and its successfully applied for variant strings will be allocated through one agreement (the Base Registry Agreement in Appendix 4). This means that the registry operator must transition to the Base Registry Agreement in Appendix 4 for its existing gTLD and its successfully applied for variant strings." Previous language: "The registry operator will need to transition to the 2026 Round Base Registry Agreement, and the existing gTLD and all variant strings will be allocated through one Registry Agreement." | Clarification of existing information only. No changes to requirements or procedures. |
Items below this line were incorporated into the Applicant Guidebook V2-2026.04.24. | |||||
5 | 22 April 2026 | 24 April 2026 | 25 April 2026 | Questions 164-169: Deleted "CR-2" in the "Criteria" column. | Answers to these questions will inform the Safeguard Assessment required by the AGB, but the "yes" or "no" answers themselves will not automatically be determinative of the assessment outcomes. Hence, the prior explanatory text regarding a "yes" response has been removed. |
4 | 22 April 2026 | 24 April 2026 | 25 April 2026 | Added instructions to Question 133 (Mission & Purpose) for applications for variants of an existing gTLD: "1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose." | Added instructions based on IDN EPDP Recommendation 3.5 |
3 | 22 April 2026 | 24 April 2026 | 25 April 2026 | Instructions for Application Question 145 updated to align with TAMS design: "CR-1. Attach Enter appropriate information in response to the question in text field." and "Upload U4000 character limit and/or upload no more than 10 pages, subject to acceptable file types." | Updated instructions based on TAMS design |
2 | 22 April 2026 | ||||