Thick WHOIS for .COM and .NET is officially delayed until 2020

Akram Atallah, President of ICANN’s Global Domains Division, sent a letter to Patrick Kane, Senior Vice President, Verisign, Inc., confirming the extension of the current implementation deadlines for the Thick WHOIS Consensus Policy for .COM and .NET.
Patrick Kane requested a 1-year extension from ICANN last month.

The ICANN Board reviewed this matter on 13 May 2018 and passed a resolution to extend the implementation dates with the goal of providing additional time for ICANN org and the contracted parties to more clearly understand how the Registration Directory Services (RDS) may be affected by the European Union’s General Data Protection Regulations (GDPR).

Following the ICANN Board resolution, the new implementation dates are as follows:

  • 30 November 2018: Registry operator to begin accepting Thick WHOIS data from registrars for existing registrations.
  • 30 April 2019: All registrars must send Thick WHOIS data to the registry operator for all new registrations in .COM and .NET.
  • 31 January 2020: All registrars are required to complete the transition to Thick WHOIS data for all registrations in .COM and .NET.

With the additional time ICANN will continue to facilitate discussions between Verisign and the Registrar Stakeholder Group to reach an agreement on the necessary changes to the relevant
Registry Registrar Agreement to implement the Thick WHOIS Consensus Policy for .COM and .NET.

Sold.Domains

About Konstantinos Zournas

Konstantinos studied Computer Engineering and Computer Science in London and lives in Athens, Greece. He works on domain names, websites and software development. Has been online since 1995 & domaining since 2002.

2 comments

  1. Verisign had a unique opportunity, as the .com and .net Registry, to oppose the GDPR as it applies to WHOIS.

    With ICANN being as disorganized as they are, nothing happened.

    As a side note, it’d be great to see the GDPR apply only to .eu and the ccTLDs/gTLDs in the European Union only. No cojones from ICANN.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.