Skip to main content
Resources

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:

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.

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.

How to Guides – How to Guides are resources available to assist registry operators with the various processes for notifying the ICANN org of updates made to approved registry services.

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 replaces the Global Domain Division (GDD) and New gTLD Applicant portals. This portal streamlines the way registry operators conduct business with the ICANN org. The Naming Services portal was built with a focus on ease-of-use and increased security. The flexible and scalable architecture allows for ongoing improvements and increased efficiencies to better serve registries and in the future, all of ICANN's contracted parties. For assistance navigating the new interface, below are some helpful tools including the Naming Services portal user guide and webinar recordings:

If you are an authorized user and are not able to log into the Naming Services portal, please email globalsupport@icann.org for assistance.

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 Services & Engagement Team – The Registry Services & Engagement Team serves several roles. With a global presence, the team collaborates with registry operators to ensure a secure, stable and resilient gTLD namespace.

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 [PDF, 573 KB] – ICANN's SLA Monitoring System API (MoSAPI) will be available to gTLDs and ccTLDs in early 2018. A pilot program is currently underway to ensure the highest quality program possible. The API will enable 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""icann.org"" is not an IDN."