JPRS WHOIS/JPRS RDAP's Compliance with Temporary Specification for gTLD Registration Data of ICANN |
---|
Upon enforcement of the General Data Protection Regulation (GDPR*1) in the European Union (EU), ICANN*2 adopted and published "Temporary Specification for gTLD Registration Data"*3 (hereinafter "Temp Spec") which established the obligations of gTLD Registries / Registrars.
As an ICANN-Accredited Registrar, JPRS operates JPRS WHOIS/JPRS RDAP for gTLD (hereinafter "JPRS WHOIS/RDAP") in compliance with Temp Spec as described in this document.*4
*1 | A uniform rule in the EU that came into effect on May 25, 2018 to protect personal data of data subjects who are in the EU. |
*2 | Acronym for "Internet Corporation for Assigned Names and Numbers", which is a private, non-profit corporation founded in the United States in 1998 to coordinate the Internet resources such as domain name, IP address, Internet protocol, root DNS servers, etc. |
*3 | https://www.icann.org/resources/pages/gtld-registration-data-specs-en |
*4 | Temp Spec does not apply to JP domain names (.jp). |
JPRS implements the followings to comply with Temp Spec in gTLD registration.
1) Some of gTLD Contact information fields being "REDACTED FOR PRIVACY" in JPRS WHOIS/RDAP
When the address of gTLD Contact (Registrant, Admin Contact or Tech Contact) is located within the European Economic Area (EEA*1), gTLD Contact information fields designated by Temp Spec are redacted for privacy: therefore, gTLD Contact information for such fields is not published.
For more details, please refer to "3. gTLD Contact Information Display on the JPRS WHOIS/RDAP".
*1 | The EEA includes the EU Countries, Iceland, Liechtenstein and Norway. |
2) Provisioning of the Contact Request Forwarding Form
JPRS provides a web form ("Contact Request Forwarding Form") for forwarding contact request or inquiry to the redacted gTLD Contact(s).
For more details, please refer to "Contact Request Forwarding Form".
3. gTLD Contact Information Display on the JPRS WHOIS/RDAP
JPRS WHOIS displays gTLD Contact information subject to Temp Spec in the following manner.
Note: The display of gTLD contact information of JPRS RDAP is same as the display of JPRS WHOIS described below.
[Affected WHOIS Interfaces] | |||
- Web-based WHOIS (https://whois.jprs.jp) | |||
- Command-line WHOIS (in case of querying whois.jprs.jp with OS built-in 'whois' command) |
[Affected gTLD Contacts] | |||
- gTLD Contact of which the Country ("Registrant Country", "Admin Country" or "Tech Country") is inside the EEA |
[Affected Fields of the Contacts] | ||||||||||||||||||||||||||||||||||||||||
- the "Inside EEA" fields of the following tables, in the manner of: | ||||||||||||||||||||||||||||||||||||||||
(a) Displayed field; the original data of the gTLD Contact being displayed; | ||||||||||||||||||||||||||||||||||||||||
(b) Redacted field; the "REDACTED FOR PRIVACY" string instead of the original data being displayed; or | ||||||||||||||||||||||||||||||||||||||||
(c) Redacted field; URL of the Contact Request Forwarding Form instead of the original data being displayed | ||||||||||||||||||||||||||||||||||||||||
Table 3-1. "Registrant" Display | ||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
Note: The following fields will be disclosed even if the Country of the Registrant is inside EEA. - Registrant State/Province - Registrant Country |
||||||||||||||||||||||||||||||||||||||||
Table 3-2. "Admin Contact" Display | ||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
Table 3-3. "Tech Contact" Display | ||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
For more details, please refer to "4. Display Examples".
When you search for 'example.com',
- on the web page, https://whois.jprs.jp/en/; or
- with whois command, '% whois -h whois.jprs.jp example.com/e';
JPRS WHOIS will return the result as follows, according to the Country field of gTLD Contact information.
Copyright© Japan Registry Services Co., Ltd. |