Skip to main content

Registration Data Request Service

Simplifying Requests for Nonpublic gTLD Registration Data

Click here to access the RDRS

The Registration Data Request Service (RDRS) is a new and free service developed to provide a more consistent and standardized format for handling requests to access nonpublic registration data related to generic top-level domains (gTLDs). This two-year pilot program which launched in November 2023 is a proof-of-concept initiative for individuals and entities with a legitimate interest in nonpublic registration data. It was developed with community input and implemented at the direction of the ICANN Board to help inform policy decisions related to a System for Standardized Access/Disclosure (SSAD). RDRS usage metric reports are published monthly and provide system usage and demand data as requested by the Generic Names Supporting Organization (GNSO) Council.

To submit a request for nonpublic gTLD registration data, click here. You will need to use an ICANN Account (new or existing) to access the service.

More information about the service and monthly usage metric reports are provided below.

Latest Announcements, Blogs, and Webinars

General Information

What is the Registration Data Request Service?

The Registration Data Request Service (RDRS) is a free and global proof-of-concept service that handles requests for access to nonpublic registration data related to generic top-level domains (gTLD)s. It connects requestors seeking disclosure of nonpublic registration data for gTLDs domain names with the relevant ICANN-accredited registrars who are participating in the service. The service streamlines and standardizes the process for submitting and receiving requests through a single platform.

Important note: The Registration Data Request Service does not guarantee access to the registration data. All communication and data disclosure between the registrars and requestors takes place outside of the system.

What is nonpublic gTLD registration data?

Nonpublic registration data can include information such as a contact name, home or email address, and phone number related to a domain under a gTLD. This type of data is not necessarily published publicly anymore due to personal data protection regulations.

Why was it developed?

The pilot program gathers usage and demand data to inform the ICANN Board's consideration of the consensus policy recommendations related to a System for Standardized Access/Disclosure (SSAD) and inform ongoing consultations with the Generic Names Supporting Organization Council.

Why is it important to gather usage and demand data?

RDRS usage and demand data will be gathered for up to two years and monthly usage reports will be published on this page. These reports will inform community discussions and Board consideration of the Phase 2 Recommendations of the Expedited Policy Development Process (EPDP) relating to SSAD. Ideally, as more ICANN-accredited registrars and requestors use RDRS, the more accurate and valuable the data collected will be toward informing the ICANN Board and community. This platform and request process also benefits consumer protection advocates, cybersecurity investigators, government officials, intellectual property professions, and law enforcement authorities, who may have a legitimate interest in requesting access to nonpublic gTLD domain data.

The proof-of-concept RDRS was developed to provide insight into the estimated volume of requests a possible SSAD may elicit. In addition, it may provide other information that helps determine the costs or benefits of the SSAD recommendations and whether the community may consider updates to the existing policy recommendations.

Who can use the RDRS system?

The service is used by participating ICANN-accredited registrars and requestors seeking nonpublic gTLD registration data. It is intended for use by individuals and entities with a legitimate interest in access to nonpublic gTLD registration data including law enforcement, government agencies, intellectual property attorneys, cybersecurity professionals, and others. ICANN-accredited registrar participation in the RDRS pilot is voluntary.

How do I find registration data that is publicly available?

Prior to making a request through the Registration Data Request Service (RDRS) please use ICANN's Lookup tool available at to find publicly available registration data.

RDRS Resources

RDRS Usage Metrics Reports

  • July 2024 (Reporting period: 01 June – 30 June 2024) [PDF] [CSV]
  • June 2024 (Reporting period: 01 May – 31 May 2024) [PDF] [CSV]
  • May 2024 (Reporting period: 01 April – 30 April 2024) Updated [PDF] [CSV]
  • April 2024 (Reporting period: 01 March – 31 March 2024) Updated [PDF] [CSV]
  • March 2024 (Reporting period: 01 February – 29 February 2024) [PDF] [CSV]
  • February 2024 (Reporting period: 01 January – 31 January 2024) [PDF] [CSV]
  • January 2024 (Reporting period: 28 November – 31 December 2023) [PDF] [CSV]

RDRS Survey Reports

  • First Quarter 2024 (Reporting period 28 November 2023 - 31 March 2024) Updated [PDF]

Additional Information

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."