Registry Registration Data Directory Services Consistent Labeling and Display Policy

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

Section 1 of this policy details technology-agnostic requirements that apply to all Registration Data Directory Services.

Section 2 of this policy details implementation requirements pertaining to WHOIS (available via port 43) and web-based Whois directory services only.

1. Registry Operators, SHALL implement the following requirements:

   1.1. The URL of the ICANN RDDS Inaccuracy Complaint Form MUST be included in the RDDS output of domain name object queries:

   • URL of the ICANN RDDS Inaccuracy Complaint Form: https://www.icann.org/wicf/

   1.2. If a value is shown for the fields "Registry Admin/Tech/Billing/Registrant ID:", the value MUST be the Repository Object Identifier (ROID) for the contact object as specified in RFC 5733.

   1.3. Additional RDDS fields MAY be included in RDDS output without further approval by ICANN. The additional field MUST NOT: include browser executable code (e.g., Javascript); provide confidential information of any sort; or cause a negative impact to the security, stability, or resiliency of the Internet's DNS or other systems. Prior to deployment, Registry Operator SHALL provide the list of all additional RDDS fields to ICANN. Registry Operator SHALL provide to ICANN any changes to the list of additional RDDS fields prior to deploying such changes.

2. Registry Operators SHALL implement the following requirements in conjunction with Section 1 of Specification 4 of the "Base Registry Agreement approved on 9 January 2014" ("Base Registry Agreement") or subsequent amendments thereto in order to comply with WHOIS (available via port 43) and web-based WHOIS directory services requirements.

   2.1. In responses to domain name object queries the below fields MUST be included either (1) immediately after the "Registrar IANA ID" field or (2) immediately before the last field ("URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/") in the following order:

   • Registrar Abuse Contact Email
   • Registrar Abuse Contact Phone

   2.2. If shown, the "Reseller" field MUST appear immediately before the "Domain Status" field.

   2.3. If shown, the value of the "Reseller" field MUST be the name of the organization, in the case where the Reseller is a legal entity, or the name of a natural person.

   2.4. If shown, the "Registrar Registration Expiration Date" field MUST appear immediately after the "Registry Expiry Date" field.

   2.5. The value section (i.e., right-hand side of the colon) of the following fields MUST follow the below format specifications:

   • "Registrar Abuse Contact Email" (as defined in the EPP RFCs for email fields)
   • "Registrar Abuse Contact Phone" (as defined in the EPP RFCs for phone fields)
   • "Reseller" is defined as token (see Extensible Markup Language 1.1)
   • "Registrar Registration Expiration Date" (as defined in the EPP RFCs for date fields)

   2.6. Registry Operator MUST update the name of keys in the output of the domain name, name server, and registrar objects as follows. The following table shows keys that are renamed from their original version in Specification 4 of the Base Registry Agreement. All other specifications (e.g. format specifications of the value section) remain unchanged.

Original key in Specification 4 of the Base Registry Agreement	New key name	Object query where the key appears
Domain ID	Registry Domain ID	domain name
WHOIS Server	Registrar WHOIS Server	domain name, registrar, nameserver
Referral URL	Registrar URL	domain name, registrar, nameserver
Sponsoring Registrar	Registrar	domain name
Sponsoring Registrar IANA ID	Registrar IANA ID	domain name
Registrar Name	Registrar	registrar
Registrant ID	Registry Registrant ID	domain name
Admin ID	Registry Admin ID	domain name
Tech ID	Registry Tech ID	domain name

2.7. If the "Billing Contact" is shown, Registry Operator MUST update the name of the key in the output of the domain name as defined below. All other specifications (e.g. format specifications of the value section) continue to apply.

Original key in the WHOIS Advisory	New key name	Object query where the key appears
Billing ID	Registry Billing ID	domain name

2.8. The URL of the ICANN Whois Inaccuracy Complaint Form MUST be included before the footer ">>> Last update of Whois database: <date and time> <<<".

Effective Date: 1 August 2017

Implementation Notes

1. On 27 April 2015, ICANN published an Advisory in response to questions from both registries and registrars regarding the applicable WHOIS (available via port 43) and web-based Whois services. Registry Operators should continue to consult this Advisory to be in compliance with their registry agreement.

2. The following section describes example outputs for WHOIS (available via port 43) and web-based directory services query objects:

   The examples below show how the data elements may appear in Whois (port 43) and web-based Whois, when required by ICANN Agreement or Policy.

   1. Domain Name Data: Full transfer, not subject to redaction and showing a key with an empty value for non-available data

      The following example has been generated using the following assumptions:

      • Contact information is being transferred from the Registrar to Registry pursuant section 7.3 and 7.4 of the Registration Data Policy.
      • The values are not subject to the redaction requirements in section 9.2 of the Registration Data Policy.
      • Registry Operator does not support Registrar Registration Expiration Date or Reseller data elements; therefore, there is no data in the Registry database for these two data elements.
      • Registry Operator is including the key for data elements where no data is available for the data elements pursuant to section 1 of Addendum I of the Registration Data Policy.

      • Domain name is delegated, DNSSEC-signed, and glue records exist.

        • Query format: whois EXAMPLE.TLD
        • Response :
          Domain Name: EXAMPLE.TLD
          Registry Domain ID: D1234567-EXAMPLE
          Registrar WHOIS Server: whois.example-registrar.tld
          Registrar URL: http://www.example-registrar.tld
          Updated Date: 2009-05-29T20:13:00Z
          Creation Date: 2000-10-08T00:45:00Z
          Registry Expiry Date: 2010-10-08T00:44:59Z
          Registrar Registration Expiration Date:
          Registrar: EXAMPLE REGISTRAR LLC
          Registrar IANA ID: 5555555
          Registrar Abuse Contact Email: email@registrar.tld
          Registrar Abuse Contact Phone: +1.1235551234
          Reseller:
          Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
          Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
          Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
          Registry Registrant ID: 5372808-EXAMPLE
          Registrant Name: EXAMPLE REGISTRANT
          Registrant Organization: EXAMPLE ORGANIZATION
          Registrant Street: 123 EXAMPLE STREET
          Registrant City: ANYTOWN
          Registrant State/Province: AP
          Registrant Postal Code: A1A1A16
          Registrant Country: AA
          Registrant Phone: +1.5555551212
          Registrant Phone Ext: 12347
          Registrant Fax: +1.5555551213
          Registrant Fax Ext: 4321
          Registrant Email: EMAIL@EXAMPLE.TLD
          Registry Tech ID: 5372811-EXAMPLE
          Tech Name: EXAMPLE REGISTRANT TECHNICAL
          Tech Phone: +1.1235551234
          Tech Email: EMAIL@EXAMPLE.TLD
          Name Server: NS01.EXAMPLE-REGISTRAR.TLD
          Name Server: NS02.EXAMPLE-REGISTRAR.TLD
          Name Server IP Address: 192.0.2.123
          Name Server IP Address: 2001:0DB8::1
          DNSSEC: signedDelegation
          URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
          >>> Last update of RDDS database: 2009-05-29T20:15:00Z <<<

   2. Domain Name Data: Full transfer, subject to redaction

      The following example has been generated using the following assumptions:

      • Contact information is being transferred from the Registrar to the Registry pursuant section 7.3 and 7.4 of the Registration Data Policy.
      • The values are subject to the redaction requirements in section 9.2 of the Registration Data Policy.
      • Registry Operator does not support Registrar Registration Expiration Date or Reseller data elements; therefore, there is no data in the Registry database for these two data elements.
      • Registry Operator is not showing the field for data elements where no data is available for the data elements pursuant to section 1 of Addendum I of the Registration Data Policy.
      • Domain name is delegated, DNSSEC-signed, and glue records exist.
        • Query: whois EXAMPLE.TLD
        • Response:
          Domain Name: EXAMPLE.TLD
          Registry Domain ID: REDACTED
          Registrar WHOIS Server: whois.example-registrar.tld
          Registrar URL: http://www.example-registrar.tld
          Updated Date: 2009-05-29T20:13:00Z
          Creation Date: 2000-10-08T00:45:00Z
          Registry Expiry Date: 2010-10-08T00:44:59Z
          Registrar: EXAMPLE REGISTRAR LLC
          Registrar IANA ID: 5555555
          Registrar Abuse Contact Email: email@registrar.tld
          Registrar Abuse Contact Phone: +1.1235551234
          Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
          Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
          Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
          Registry Registrant ID: REDACTED
          Registrant Name: REDACTED
          Registrant Organization: REDACTED
          Registrant Street: REDACTED
          Registrant City: REDACTED
          Registrant State/Province: AP
          Registrant Postal Code: REDACTED
          Registrant Country: AA
          Registrant Phone: REDACTED
          Registrant Phone Ext: REDACTED
          Registrant Fax: REDACTED
          Registrant Fax Ext: REDACTED
          Registrant Email: REDACTED
          Registry Tech ID: REDACTED
          Tech Name: REDACTED
          Tech Phone: REDACTED
          Tech Email: REDACTED
          Name Server: NS01.EXAMPLE-REGISTRAR.TLD
          Name Server: NS02.EXAMPLE-REGISTRAR.TLD
          Name Server IP Address: 192.0.2.123
          Name Server IP Address: 2001:0DB8::1
          DNSSEC: signedDelegation
          URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
          >>> Last update of RDDS database: 2009-05-29T20:15:00Z <<<
          …

   3. Domain Name Data: minimum required output

      The following example has been generated using the following assumptions:

      • Contact information is not being transferred from the Registrar to Registry pursuant section 7.3 and 7.4 of the Registration Data Policy.
      • Registry Operator does not support Registrar Registration Expiration Date or Reseller data elements; therefore, there is no data in the Registry database for these two data elements.
      • Registry Operator is not showing the field for data elements where no data is available for the data elements pursuant to section 1 of Addendum I of the Registration Data Policy.
      • Domain name is delegated, DNSSEC-signed, and glue records exist.
        • Query: whois EXAMPLE.TLD

        • Response:
          Domain Name: EXAMPLE.TLD
          Registry Domain ID: REDACTED
          Registrar WHOIS Server: whois.example-registrar.tld
          Registrar URL: http://www.example-registrar.tld
          Updated Date: 2009-05-29T20:13:00Z
          Creation Date: 2000-10-08T00:45:00Z
          Registry Expiry Date: 2010-10-08T00:44:59Z
          Registrar: EXAMPLE REGISTRAR LLC
          Registrar IANA ID: 5555555
          Registrar Abuse Contact Email: email@registrar.tld
          Registrar Abuse Contact Phone: +1.1235551234
          Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
          Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
          Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
          Name Server: NS01.EXAMPLE-REGISTRAR.TLD
          Name Server: NS02.EXAMPLE-REGISTRAR.TLD
          Name Server IP Address: 192.0.2.123
          Name Server IP Address: 2001:0DB8::1
          DNSSEC: signedDelegation
          URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
          >>> Last update of RDDS database: 2009-05-29T20:15:00Z <<<
          …

Registrar Data:

• Query format: whois "registrar Example Registrar, Inc."
• Response format:
  Registrar: Example Registrar, Inc.
  Street: 1234 Admiralty Way
  City: Marina del Rey
  State/Province: CA
  Postal Code: 90292
  Country: US
  Phone Number: +1.3105551212
  Fax Number: +1.3105551213
  Email: registrar@example.tld
  Registrar WHOIS Server: whois.example-registrar.tld
  Registrar URL: http://www.example-registrar.tld
  Admin Contact: Joe Registrar
  Phone Number: +1.3105551213
  Fax Number: +1.3105551213
  Email: joeregistrar@example-registrar.tld
  Admin Contact: Jane Registrar
  Phone Number: +1.3105551214
  Fax Number: +1.3105551213
  Email: janeregistrar@example-registrar.tld
  Technical Contact: John Geek
  Phone Number: +1.3105551215
  Fax Number: +1.3105551216
  Email: johngeek@example-registrar.tld
  >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<
  …

Nameserver Data:

• Query format: whois "nameserver (nameserver name)", or whois "nameserver (IP Address)"
• Response format:
  Server Name: NS1.EXAMPLE.TLD
  IP Address: 192.0.2.123
  IP Address: 2001:0DB8::1
  Registrar: Example Registrar, Inc.
  Registrar WHOIS Server: whois.example-registrar.tld
  Registrar URL: http://www.example-registrar.tld
  >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<
  …

Background:

This Consensus Policy is a product of policy implementation directed by ICANN Board resolutions 2014.02.07.08 - 2014.02.07.09, which adopted the GNSO Council Policy Recommendations for a new Consensus Policy on Thick Whois.

Recommendation #1 of the Thick Whois Policy Development Process (PDP) Working Group (WG), adopted by the GNSO Council on 31 October 2013, states: "The provision of thick Whois services, with a consistent labelling and display as per the model outlined in specification 3 of the 2013 RAA, should become a requirement for all gTLD registries, both existing and future."

The Final Report [PDF, 1.23 MB] of the Thick Whois Policy PDP WG further included in its Section 7.2 'Implementation Considerations' guidance related to the timeline and requirements for implementing the transition from thin to thick Whois. It specifically notes that "The WG does emphasize that implementation of one part of the recommendation (for example, transition of existing thin gTLD registries to thick model) should not unnecessarily delay the implementation of another part of the recommendation (for example, the consistent labeling and display of such data)".

As a consequence, ICANN staff and the Implementation Review Team (IRT) agreed that consistent labeling and display could be decoupled from the implementation of the transition from thin to thick.

ICANN submitted a draft proposal for implementation of the consistent labeling and display requirement for Public Comment on 3 December 2015. After considering the community's feedback and in collaboration with the Thick Whois IRT, ICANN revised its proposal as reflected in this Consensus Policy.

It should be noted that ICANN's objective in implementing the GNSO Policy recommendations has been to minimize the impact to registrants, end users, contracted parties and to the overall Registration Data Directory Services (RDDS) systems by seeking to synchronize, where appropriate, this implementation with other related initiatives such as the adoption of the Registration Data Access Protocol (RDAP).