Skip to main content
Resources

gTLD Registration Dataflow Matrix and Information

ICANN policies and contracts require contracted parties to collect, create, retain, escrow, and publish a variety of data elements related to registry and registrar operations, domain name registrations, and registrants. The ICANN organization is investigating whether there are potential compliance issues under its agreements with registries and registrars because of the European Union General Data Privacy Regulation. With the help from contracted parties and interested stakeholders, ICANN has collected information needed to help evaluate GDPR compliance in the context of registry, registrar, and registrant data. This information will be used to inform legal analysis, as well as to engage with data protection authorities.

User Types and Purposes

At the end of June 2017, ICANN asked contracted parties and interested stakeholders to identify user types and purposes of data elements required by ICANN policies and contracts. The individual responses received and a compilation of the responses are provided below. We encourage the public to review this information and provide any additional user types and purposes not already captured. Any additional submissions will be added to the matrix and an updated will be posted in late August.

If you have additional information you'd like to add to the matrix, please use the template below and send the completed template to globalsupport@icann.org.

Overall Summary Document

gTLD Registration Dataflow Matrix and Information - Summary of Input Received From Contracted Parties and Interested Stakeholders [PDF, 743 KB]

Data Flow Matrix Documents

Dataflow Matrix, Compilation of Responses Received – Current Version [XLSX, 113 KB]

Dataflow Template [PDF, 412 KB]

Responses Received

At-Large Advisory Committee (ALAC) [PDF, 74 KB]
Business Constituency [PDF, 191 KB]
Contracted Parties House (CPH) – amended 3 October 2017 [XLSX, 32 KB]
Intellectual Property Constituency (IPC) [PDF, 187 KB]
Individual Users [XLSX, 10 KB]
United States Internal Revenue Service (IRS) [PDF, 59 KB]
Microsoft [PDF, 88 KB]
United States Department of Justice (DOJ)/Federal Bureau of Investigation (FBI) [PDF, 68 KB]
Governmental Advisory Committee (GAC) Public Safety Working Group (PSWG) [XLSX, 10 KB]
Criminal and Consumer Protection Law Enforcement Agency [PDF, 185 KB]
EUROPOL, European Cybercrime Centre (EC3) [PDF, 91 KB]
Individual User - Ayden Férdeline [PDF, 87 KB]
Domain Tools [XLSX, 74 KB]

Archived Documents

Dataflow Matrices - Previous Versions

Version dated 2 August 2017 [XLSX, 61 KB]

Version dated 15 August 2017 [XLSX, 62 KB]

Version dated 23 August 2017 [XLSX, 64 KB]

Version dated 29 August 2017 [XLSX, 66 KB]

Dataflow Summaries - Previous Versions

Version dated 11 September 2017 [PDF, 686 KB]

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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