6. Change Log
AttachmentsThis 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 |
|---|---|---|---|---|---|
44 | 7 August 2026 | 7 August 2026 | 10 August 2026 | Corrected description of deadline for filing of challenge of a Singular/Plural notification in Section 1.2.14.2 to capture both outcomes that could be challenged:
“21 days after the issuance of the notification that the application has been placed in a contention set or is ineligible to proceed based on a validated Singular/Plural Notification.” | Correction only for consistency with grounds for challenge. No change to procedures. |
43 | 7 August 2026 | 7 August 2026 | 10 August 2026 | Corrected the numbering of instructions in relation to Question 173 | Correction only. |
42 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Moved Footnote 270 related to defining "Permutations and Transpositions" to the first instance in Paragraph 6 of Section 7.5.1. | Change for clarity only. No changes to any information. |
41 | 20 July 2026 | 20 July 2026 | 24 July 2026 | On Q172, "Yes" was missing from "Public Posting" column | Missing information, no changes to any information or procedures. |
40 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Corrected section numbers related "Reserved Names Review/Identification" (7.2.2.1, 7.2.2.2) | Correction only. |
39 | 11 June 2026 | 14 June 2026 | 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 |
|---|---|---|---|---|---|
16 | 29 September 2026 | 29 September 2026 | 2 October 2026 | AGB Sections 1.2.2.5 and 3.7.2 noted that "A Prioritization Draw is expected to be held no later than 30 days after String Confirmation Day." The timeframe of the Prioritization Draw will be updated to state in all relevant sections that "A Prioritization Draw is expected to be held on a to-be-determined date in the first half of 2027.” | This minor operational adjustment moves the Prioritization Draw to the first half of 2027 to help ensure that ICANN org and applicants are appropriately prepared for the event. In the period immediately following String Confirmation Day, both ICANN org and the broader community will be focused on activities supporting the imminent String Evaluation and Application Community Input stages. The revised timing will not affect application processing, as all applied-for strings will proceed through String Evaluation concurrently and application priority numbers do not determine processing order during that stage, as noted in this FAQ. Priority numbers become relevant only at later stages of application processing (i.e., Applicant Evaluation and Application Evaluation stages, after the String Evaluation Stage concludes). ICANN will notify all applicants and publish an announcement when the precise date for Prioritization Draw is determined. |
15 | 7 August 2026 | 7 August 2026 | 10 August 2026 | The Internet Corporation for Assigned Names and Numbers (ICANN) has made an adjustment to the generic top-level domain (gTLD) evaluation fee payment timeline for New gTLD Program: 2026 Round applicants: ICANN must receive the full gTLD evaluation fee by whichever date is later:
(For example, for an invoice sent on 14 August 2026, payment must be received by 23:59 UTC on 21 August 2026.) | This adjustment ensures that for applicants that receive an invoice after the close of the application submission window (23:59 UTC on 12 August 2026) there are seven days between when the invoice is sent and when ICANN must receive payment. |
14 | 7 August 2026 | TBD (Pending further discussion; will not be included in v3 of AGB) | 10 August 2026 | Updated "255 character limit" on several application questions in Appendix 1 to say: "Input length should be according to character limits set by TAMS." | Update to reflect system requirements as they may vary by question. |
13 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Updated Flowchart A6-2 to more accurately reflect movement from Flowchart A6-1. The only change relates to the box on top, which now states: "It is determined that a change is required to the ongoing program. The change..." | Change for consistency purposes only. No changes to any information or process. |
12 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Added "Type" nomenclature to section A6.3.2 Change Execution and A6.5 Change Log | Change for consistency purposes only. No changes to any information or process. |
11 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Updated Path 3 to align with boxes in Flowchart A6-1 | Change for consistency purposes only. No changes to any information or process. |
10 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Added Type 0 in footnote 366 in Section A6.2 as a sub-category to minor operational changes (Type 1) | Added Type 0 as this has been added to the change log and helps to differentiate such changes from Type 1 changes |
9 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Added "Type" to description of changes in Section A6.2 | Added "Type" to be consistent with change log and SPIRT Charter |
8 | 20 July 2026 | 20 July 2026 | 24 July 2026 | Updated instructions related to collection of information for individuals for Q104-108 (phone number and email address), and in Appendix 9. This update ensures consistency with the system and the "Identifying Information" questions for individuals (Q55-64), which are used for Background Screening purposes. | Update for consistency, no changes to procedures. |
7 | 11 June 2026 | 14 June 2026 | 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 | 14 June 2026 | 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 | 24 April 2026 | 25 April 2026 | Added fee information for CPE to Section 3.3.2, Table 3-2 | Added fee for CPE |
1 | 22 April 2026 | 24 April 2026 | 25 April 2026 | Added "Will have access to objections as they are being filed, prior to the Administrative Review, to ensure they are able to review objections prior to the relevant deadlines. The IOs shall treat all such information as strictly confidential and shall not disclose it to any third party." to Section 4.5.4 Independent Objectors. | Added to ensure IOs have access to all objections filed to make a proper assessment of which objections should be filed. |
Type 2: Non-Minor Operational Changes
Note: As per the SPIRT Charter, “the SPIRT shall endeavor to provide guidance, if any, within seven (7) calendar days or as otherwise required to maintain the operation of the Program if it disagreed with the decision.”
Change # | Date Shared | Effective Date | SPIRT Guidance Due By | Description of Change | Rationale for Change |
|---|---|---|---|---|---|
3 |
|
|
| Implement a temporary solution with respect to the upcoming change to the EPP Extension Requirement for the RSP Evaluation Program, in accordance with Phase 1 Actions described in the ICANN proposed solution (version 28 July 2026). | The current RSP Handbook requires applicants to attest that they will not use EPP extensions that are not registered with IANA Extensions for the EPP Registry in accordance with RFC 7451. To address a request referred by the GNSO Council to SPIRT, ICANN org has determined that this attestation should not be enforced because the applicable registration criteria are expected to be updated through the anticipated publication of draft-ietf-regext-ext-registry-epp as an RFC. The temporary solution, as described in the Phase 1 Actions, intends to implement the EPP extension requirement change without disrupting RSP Evaluation Program or 2026 Round timelines. It also aims to provide clarity before the RSP application window closes on 12 August 2026 to enable RSP applicants to timely submit their applications. With respect to the permanent solution to implement permanent changes to the RSP Evaluation Program documentation, systems, and business processes as described in Phase 2 Actions, ICANN plans to provide precise implementation timeline estimate after the gTLD evaluation fee payment deadline and completion of the required level-of-effort analysis, as well as engage with SPIRT for subsequent discussion. |
2 | 26 June 2026 | 3 July 2026 | 3 July 2026 | Implement a process to close non-responsive ASP applications and remove system access at the close of the New gTLD Program: 2026 Round application submission period. | Supports formal closure of the 2026 ASP round while allowing non-responsive applicants the maximum opportunity to re-engage and complete the ASP and New gTLD application processes before the gTLD application submission period closes. |
1 | 04 May 2026 | Confirmed as “approved” on 12 May 2026 | 11 May 2026 | ICANN proposes to provide updated guidance to the Support Applicant Review Panel (SARP) on how to interpret the Financial Need criteria and indicators. This updated interpretation includes an allowance of up to 15% to the USD $5 million Financial Need threshold, helping ensure that variations in funding environments, currency exchange rates, and inflation are more fairly accounted for. | This change would provide a degree of flexibility on the SARP’s interpretation of the Financial Need criteria to: a) alleviate currency conversion volatility, while still maintaining consistent and predictable outcomes; and b) recognize some eligible entities have multi-year funding arrangements and fluctuations. |
Type 3: Policy Changes
As of 22 April 2026: None