Registry Frequently Asked Questions (FAQs)
Please note that the English language version of all translated content and documents are the official versions and that translations in other languages are for informational purposes only.
2017 Global Amendment to the Base New gTLD Registry Agreement
The Registry Stakeholder Group (RySG) notified the ICANN organization on 16 July 2014 that it wished to negotiate proposed changes to the Registry Agreement ("RA") pursuant to Section 7.7 of the RA. Following negotiations between the ICANN organization and the RySG Working Group ("WG"), a 50-day public comment period, and analysis of the public comments by the ICANN organization and the WG, the ICANN organization submitted the proposed changes in the form of a Global Amendment for a vote by applicable registry operators according to the terms of the RA. After reaching approval by applicable registry operators on 10 April 2017, the ICANN Board approved the Global Amendment on 18 May 2017. The ICANN organization issued a 60-day notice to applicable registry operators and the 2017 Global Amendment became effective 31 July 2017.
- Global Amendment Effective Date FAQ (version: 7 June 2017) [PDF, 341 KB]
- Voting Process – FAQ (Version: 17 February 2017) [PDF, 1.005 MB]
Submission of Annual Certifications and Internal Reviews FAQ
(Updated 10 September 2018)
This Annual Certification FAQ provides answers to commonly asked questions regarding various annual certifications and internal reviews required that are required under provisions of the Registry Agreement.
Registry Operator Billing FAQ [PDF, 451 KB]
(Updated 18 November 2019)
The Billing FAQ provides answers to commonly asked questions regarding the billing and invoicing processes for Registry Operators.
Continued Operations Instrument (COI) Amendment and Obligation Release Services FAQ (Updated 13 June 2019)
The COI Amendment Service FAQ provides answers to commonly asked questions related to the COI Amendment and COI Obligation Release Services. The COI Amendment Service provides a method for Registry Operators to request permission from the ICANN organization to change the value of their COI funds to align with the domain registrations under management (DUMs) projections for the gTLD. The COI Obligation Release Service provides a mechanism for ICANN to release COI(s) that are no longer required per Specification 8 of the Registry Agreement.
Portal Data Exposure Issue FAQ [PDF, 147 KB]
(Published 20 August 2015)
This FAQ provides answers to questions about the data exposure issue that occurred in the New gTLD Applicant and GDD Portals, which the Registry Stakeholder Group posed to the ICANN organization on the 10 June 2015 at 20:00 UTC Registry Stakeholder Call. It also contains the first set of Questions & Answers about the issue that the ICANN organization published on 2 March 2015, four days after we were made aware of it.
Name Reservation, Allocation, and Registration FAQ [PDF, 513 KB] (Published 08 August 2014)
Per Specification 5 of the Registry Agreement, registry operators are required to exclude certain domain names from registration. This FAQ answers questions to commonly asked questions pertaining to name reservation, allocation and registration.
Emergency Back-end Registry Operator (EBERO) FAQ (Published 02 April 2013)
Emergency back-end registry operators are organizations that have demonstrated years of experience in operating domain name services, registration data directory services and extensible provisioning protocol services. They have entered into three to five year contracts with the ICANN organization to provide five critical registry functions in the event of a TLD registry operator failure. The EBERO FAQ provides additional information on EBERO including why it is important, how they are chosen and when they will be activated.