Skip to main content

Thick WHOIS Transition Update

The transition from Thin to Thick WHOIS is well underway and I want to provide you with an update on the progress and recent developments.

First, I want to acknowledge the efforts of the Thick WHOIS Implementation Review Team (IRT), registries, and registrars who are working together to complete what needs to be done for the policy to become effective in accordance with the previously announced implementation timeline.

The registry operator for .COM and .NET, Verisign, met the 1 May deadline to deploy the Operational Testing & Evaluation (OT&E) environment for registrars to test the migration of Thick WHOIS data to Verisign. There are currently approximately 37 active registrars that have submitted test transactions.

In preparation to complete the deployment to accept Thick WHOIS data, Verisign proposed amendments to the Registry-Registrar Agreements (RRAs) for .COM and .NET in order to have the legal framework necessary for Verisign to begin accepting registrar transmission of Thick data to the registry.

The proposed amendments would largely bring the .COM and .NET RRAs into alignment with all other Thick generic top-level domains (gTLDs) in terms of language for registrant consent for transmission of registration information. The proposed amendments also would incorporate language similar to most other registry registrar agreements with respect to putting registrants on notice of the legal reasons why domain names could be subject to cancellation or transfer.

The ICANN organization followed its published Registry-Registrar Agreement amendment procedure and forwarded the proposed amendments to the Registrar Stakeholder Group (RrSG) for review.

The RrSG expressed concerns about agreeing to the proposed amendments based on issues relating to the European Union's General Data Protection Regulation (GDPR), which takes effect on 25 May 2018. As such, the next step outlined in the procedure is for the ICANN organization to consult with the registry operator and the RrSG to resolve these concerns.

In accordance with the procedure, we began individual discussions with both parties in mid-May. On 22 May, Verisign and the RrSG participated in a first joint call on this topic. These discussions are continuing and all parties are collaborating in good faith toward a resolution.

On 20 June 2017, Verisign wrote to ICANN requesting an extension of the 1 August 2017 deadline to Verisign to begin accepting Thick WHOIS data from registrars [PDF, 3.7 MB], because the necessary RRA amendments have not been approved and will not be in place by the 1 August 2017 deadline for the first phase of implementation. It should be noted that the 1 August 2017 date is an optional milestone for registrars to begin voluntarily submitting Thick data to the registry.

Verisign's letter stated that their test environment will remain available and they will continue to engage with ICANN and the Registrar Stakeholder Group regarding the proposed RRA. Verisign noted that they have not identified at this time, a need for an extension of either the 1 May 2018 Thick WHOIS deadline for all new .COM and .NET registrations or the 1 February 2019 deadline for the completion of the Thick WHOIS transition.

This means that while Verisign is able to meet the schedule for the technical requirements called out in the policy, the legal framework of the RRA that is necessary for Verisign to begin accepting Thick WHOIS data on 1 August 2017 has not yet been approved.

Although the ICANN organization could theoretically approve the proposed RRA amendments despite the objections of the RrSG, ICANN strives for consensus whenever possible. Therefore, we believe it is beneficial to provide Verisign, ICANN, and the RrSG with more time to continue discussions in hopes of achieving a resolution, while still taking reasonable steps to comply with the policy.

To that end, the ICANN organization approved Verisign's request for a 120-day extension of the 1 August 2017 date in the Thick WHOIS Transition Policy by which Verisign is required to deploy an Extensible Provisioning Protocol (EPP) mechanism and an alternative bulk transfer mechanism for .COM and .NET for registrars to migrate registration data for existing domain names. With this extension, the new date for Verisign's compliance with the requirement is 29 November 2017.

The ICANN organization will update the community on this subject regularly. If the consultations on the proposed RRA amendments do not show meaningful progress, the ICANN organization could seek further guidance from the ICANN Board and community on a path forward.


    secura  00:11 UTC on 13 July 2017

    Registrars and users have made a good experience with thick whois at many domain extensions. Therefore it should be used as a common standard also for .net and .com. Hans-Peter Oswald ICANN accredited Registrar Secura

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