Skip to main content

Registry Resources

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.

The ICANN org has various resources available for registry operators. These include Frequently Asked Questions (FAQs) and How to Guides for registry services. Below are links to such resources:

Bulk Transfers: To see list of bulk transfers resulting from registrar accreditations terminated by ICANN and the related FAQ, please visit the Bulk Transfers page.

Centralized Zone Data Service (CZDS) – CZDS provides a centralized point for interested parties to request access to Zone Files provided by participating Top Level Domain Registries. The service is the solution for scaling zone data transfer as hundreds of new gTLDs are added to the Internet.

Data Protection and Privacy - For information regarding ICANN's data protection and privacy activities, including GDPR, please visit the Data Protection and Privacy page.

Emergency Back-end Registry Operator (EBERO) – The establishment of Emergency Back-End Registry Operators, or EBEROs, are an important innovation of the New gTLD Program. The EBERO program mitigates risks to the stability and security of the Domain Name System in the event of New gTLD operator failure.

Form 6166 - U.S. Tax Residency Certification (TRC) –This is the certificate that many of ICANN's contracted parties located outside of the United States (U.S.) can use to claim income tax treaty benefits, and/or certain other tax benefits, in other countries.

Framework for Registry Operators to Respond to Security Threats – The Framework provides guidance to registry operators to respond to security threats. It is designed to assist both law enforcement and registry operators in understanding the issues and limitations faced and to provide resources and alternatives for resolving identified security threats.

Operations Handbook for Registry Operators – As a registry operator, there are many obligations at various stages throughout the life of a generic top-level domain (gTLD). The Operations Handbook for Registry Operators is intended to provide high-level information pertaining to ongoing registry operations required to fulfill the obligations specified in the base Registry Agreement and Specification 13.

GDD Accounts and Services Team – The GDD Accounts and Services Team serves several roles. With a global presence, the team collaborates with both registry operators and registrars to ensure a secure, stable and resilient gTLD namespace.

gTLDs JSON Report – The gTLDs JSON Report provides a list of all gTLDs that have signed contracts with the ICANN org, indicating specific contract attributes and the dates in which the TLDs have been included in the root zone.

List of Top-level Domains – A list of all valid top-level domains, maintained by the IANA.

Monthly Registry Reports – Per Specification 3 of the Registry Agreement, registry operators are mandated to provide ICANN with monthly transaction reports. Although these reports are published, they are withheld for three months after the end of the month to which the report relates.

Naming Services portal – The Naming Services portal (NSp) for registry operators is where registry operators communicate directly and securely with ICANN org. The secure and scalable architecture allows for ongoing improvements and increased efficiencies to better serve registry operators. The portal provides contact management, general inquiry and service request cases and contractual compliance case management.

Please see Naming Services portal for Registry Operators for more information.

New gTLD Program – The New Generic Top-level Domain (gTLD) Program is an initiative coordinated by the ICANN org that is enabling the largest expansion of the domain name system. Via the introduction of new gTLDs, the program aims to enhance innovation, competition and consumer choice. Many new safeguards to help support a secure, stable and resilient Internet were introduced as a result of the program.

New gTLD Program Case Studies – As part of the ICANN org's global efforts to raise awareness of, and interest in New gTLDs, all registry operators are invited to partner with us to develop case studies. These case studies tell the story of a gTLD, including its background and business objectives. They are intended for use as educational resources.

New gTLD Registry Operator CSV Report [CSV, 29.3 KB] – The New gTLD Registry Operator CSV Report is a downloadable comma separated value (CSV) file which provides a list of all New gTLDs that have signed a contract with the ICANN org, along with the corresponding registry operator, date of contract execution, application ID, and gTLD delegation date, where applicable.

Registration Data Access Protocol (RDAP) – RDAP enables users to access current registration data and was created as an eventual replacement for the WHOIS protocol. RDAP was developed by the technical community in the Internet Engineering Task Force (IETF).

Registry Frequently Asked Questions (FAQs) – The ICANN org publishes FAQs to provide answers to commonly asked questions pertaining to registry services and contractual obligations.

Registry Listing Page – The ICANN org has a publicly centralized directory webpage for entities interested in outreach to a specific registry operator. This contact information may be the registry's customer service department or a specific point of contact that handles general inquiries for the registry.

Registry System Testing (RST) – RST ensures that a registry operator has the capacity to operate a new gTLD in a stable and secure manner, by testing critical registry functions as described in the registry agreement. Testing requirements vary depending on the services a registry operator supports.

Service Level Agreement (SLA) Monitoring System API Specification – ICANN's SLA Monitoring System API (MoSAPI) is available to gTLDs and ccTLDs. The API enables registry operators to monitor the health of their TLDs in near real-time, take immediate corrective action should the need arise, and retrieve a list of the SLA monitoring system's probe nodes.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."