Page History

...

This section covers the following:

2013 RAA Registration Data Directory Service (WHOIS) Specification

https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#WHOIS

Basic Requirements

• Registrar must operate a port 43 WHOIS service for TLDs operated by thin registry.
• Registrar must operate a web-based WHOIS service, free for public query-based access.
• Registrar is not required to provide port 43 WHOIS service for domain names that are not sponsored by the registrar.
• Both WHOIS services need to be accessible via both IPv4 and IPv6 networks.

...

WHOIS Advisory: Clarifications to the Registry Agreement, and the 2013 Registrar Accreditation Agreement (RAA) regarding applicable Registration Data Directory Service (WHOIS) Specifications
[Effective 31 January 2016]

...

• Except “Optional” fields, all other fields listed in RDDS Specification Section 1.4.2 of 2013 RAA are “Required”.
• Noteworthy requirements:

1. 1. Registrar is only REQUIRED to show WHOIS information for domain names for which the Registrar is the Sponsoring Registrar
   2. Non-US-ASCII characters SHOULD be encoded in UTF-8.
   3. IP address(es) for name servers SHOULD NOT be shown in WHOIS output.
   4. Do not add JavaScript or other client-side script code to the port 43 WHOIS output, and do not add data that could be wrongfully interpreted as markup language in web-based WHOIS.
   5. All field names are case sensitive and it MUST be shown as defined in section 1.4.2 of the RDDS specification of the 2013 RAA.

Fields may be in Different Places

• IDN Domain Name (U-Label), two acceptable places:

1. 1. Immediately following the field “Domain Name”, or
   2. As an additional field, immediately after the “URL of the ICANN WHOIS Data Problem Reporting System” field.

Example: 

• Abuse Contact, two acceptable places:

• • Registrar Abuse Contact Email
  • Registrar Abuse Contact Phone

1. 1. Following the "Registrar IANA ID" field; or
   2. Immediately before the last field ("URL of the ICANN WHOIS Data Problem Reporting System") 

Example: 

• Billing Contact, two acceptable places:

...

• A domain name can be suspended and/or canceled, if RNH meets below conditions:
  • Section 5 of WAPS:
    • Willfully provide inaccurate or unreliable information
    • Failed to respond for over fifteen (15) days to inquiries by Registrar concerning the accuracy of contact details associated with the RNH.
• Section 3.2.2 in 2013RAA:
  • Willfully failed to update information provided to Registrar within seven (7) days of any change. 

WHOIS Advisory: Clarifications to the 2013 RAA WHOIS Accuracy Specification

[Published: 16 November 2015]

...

1. Registrar is not required to validate or verify RNH (and, if different, Account Holder) contact information when a domain name is renewed solely because the registration renewed.
   • If contact information is materially changed or if another circumstance requiring validation or verification applies, the registrar must perform the required action(s).
2. In cases where a domain name is transferred to a gaining registrar, and in the course of the transfer, the gaining registrar obtains consent to the transfer via the FOA from the Registered Name Holder or Account Holder via means that would fulfill the verification requirements of section 1(f)(i) of the Specification, the gaining registrar does not need to repeat the verification process on the contact data if there are no material changes to that contact data.
3. WHOIS-related complaints that are processed by ICANN as a "data format" issues (as opposed to "data accuracy" issues) do not invoke an obligation for the registrar to validate or verify WHOIS information. In such cases, the registrar is required to correct the data formatting issue but is not required to contact the RNH to verify the formatting correction.
4. Registrars can engage third parties (e.g. Resellers) to perform data validation and verification as required, but registrars are ultimately responsible for ensuring compliance with the Specification's requirements.

...

• Registrars who include domain name registration statuses in WHOIS output:

• • must only refer to the statuses by using EPP codes, AND provide a link/URL next to the EPP code directing to an ICANN page explaining the code’s meaning
  • must include in the WHOIS output: “For more information on WHOIS status code, please visit https://icann.org/epp" Or the longer form of the link is also acceptable: https://www.icann.org/resources/pages/epp-status-codes-list-2014-06-18-en.”

• Registries must include the ICANN-issued Globally Unique Registrar Identification number (GURID or IANA ID) in their WHOIS output

...