Registration Data Access Protocol: Difference between revisions

Content deleted Content added
Number resources: random capitalization
WHOIS replacement: hyphen missing from compound modifier
 
(6 intermediate revisions by the same user not shown)
Line 110:
 
==Name resources==
RDAP databases for registered names are maintained after ICANN agreement.<ref name="icann2013"/> Name resources are much slower, as the number of registries under ICANN is huge. In addition, as the [[General Data Protection Regulation|GDPR]] became enforceable, in May 2018, the problem of personal data divulged via WHOIS or RDAP slowed adoption further.<ref>{{cite web |title=Haunted by Europe's GDPR, ICANN sharpens wooden stake to finally slay the Whois vampire |author=Kieren McCarthy |date=October 23, 2019 |url=https://www.theregister.com/2019/10/23/icann_kills_whois/ |work=[[The Register]] |access-date=June 8, 2020 |archive-date=May 25, 2023 |archive-url=https://web.archive.org/web/20230525235553/https://www.theregister.com/2019/10/23/icann_kills_whois/ |url-status=live }}</ref> To solve the conflict between GDPR and ICANN policies ICANN published a temporary specification according to which all contact details need to be redacted for privacy reasons if they fall under the GDPR, unless the contact explicitly allows publication. This includes email addresses, however the registrar has to offer an anonymized email address or a web form to allow forwarding of information to contacts. The registry RDAP/WHOIS response has to contain a notice that these options to contact the contacts are only available in the registrar RDAP/WHOIS.<ref name=":0">{{Cite web |title=Temporary Specification for gTLD Registration Data - ICANN |url=https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#appendixA |access-date=2023-04-08 |website=www.icann.org}}</ref>
 
To keep RDAP information accurate, registrars have to send a yearly Whois Data Reminder Policy (WDRP) notice to the registrant contact. This is commonly done via email containing all the RDAP information the registrar has and asking the registrant to update it immediately if it is incorrect, while at the same time reminding the registrant that incorrect RDAP information can lead to the deletion of the ___domain name.<ref>{{Cite web |title=Whois Data Reminder Policy - ICANN |url=https://www.icann.org/resources/pages/registrars/consensus-policies/wdrp-en |access-date=2023-04-08 |website=www.icann.org}}</ref> Additionally each registrar has to offer an abuse contact and after being informed about incorrect RDAP information has to make sure that it is corrected quickly or suspend the ___domain.<ref name="icann2013" />
 
== WHOIS replacement ==
On January 19, 2023 ICANN opened voting on a global amendment to all its registry and registrar agreements. In it they defined a RDAP Ramp-Up Period of 180 days starting with the effectiveness of this amendment. 360 days after this period is defined as the WHOIS Services Sunset Date, after which it is not a requirement for registries and registrars to offer a WHOIS service and instead only a RDAP service is required. All voting thresholds were met within the 60 -day voting period and the amendment will be submitted to the ICANN Board for approval and implementation.<ref>{{Cite web |title=2023 Global Amendments to the Base gTLD Registry Agreement (RA), Specification 13, and 2013 Registrar Accreditation Agreement (RAA) - ICANN |url=https://www.icann.org/resources/pages/global-amendment-2023-en |access-date=2023-04-07 |website=www.icann.org |archive-date=2023-04-07 |archive-url=https://web.archive.org/web/20230407062429/https://www.icann.org/resources/pages/global-amendment-2023-en |url-status=live }}</ref>
 
== Query example ==
To query RDAP, there are several software and web clients including icann-rdap (reference implementation command-line client by ICANN), OpenRDAP (independent command-line client), and rdap.dev web client.
 
In certain jurisdictions, RDAP redacted contact information as required by regulations such as [[General Data Protection Regulation]] (GDPR). Contact information for RDAP may be accessed with Registration Data Directory Services (RDDS) such as ICANN Lookup.<ref name=":0" /><ref>{{Cite web |title=ICANN Lookup |url=https://lookup.icann.org/en/lookup |access-date=2025-06-04 |website=lookup.icann.org |archive-date=2025-05-31 |archive-url=https://web.archive.org/web/20250531085849/https://lookup.icann.org/en/lookup |url-status=live }}</ref> Non-public contact information can be requested with Registration Data Request Service (RDRS).<ref>{{Cite web |title=Home - Registration Data Request Service |url=https://rdrs.icann.org/ |access-date=2025-05-31 |website=rdrs.icann.org}}</ref>
 
Below is an example of RDAP data returned for an individual resource holder. This is the result of a RDAP query in raw format (using OpenRDAP client) for the website of ''[[Final Fantasy XIV]]'', with [[Markmonitor]] as registrar:<syntaxhighlight lang="doscon" highlight="1">
Line 189:
 
== Extensions ==
The RDAP protocol allows for extensions and IANA is maintaining a list of known RDAP extensions. Some of these extensions are defined by RFCs, such as likefor sorting and paging, others are just for specific TLDs.<ref>{{Cite web |title=RDAP Extensions |url=https://www.iana.org/assignments/rdap-extensions/rdap-extensions.xhtml |access-date=2023-04-08 |website=www.iana.org}}</ref>
 
==Related standards==
Line 212:
* [[Domain name registry]]
* [[Domain name registrar]]
* [[Extensible Provisioning Protocol]] - Standard{{dash}}standard for changing the ___domain data that is displayed by RDAP
 
==References==
Line 221:
* [https://www.iana.org/assignments/rdap-extensions/rdap-extensions.xhtml IANA RDAP Extensions]
* [https://www.iana.org/assignments/rdap-json-values/rdap-json-values.xhtml IANA RDAP JSON Values]
* {{Github|icann/icann-rdap}} - {{dash}}A command line RDAP client by [[ICANN]]
* {{Github|openrdap/rdap}} - {{dash}}An alternative command line RDAP client by OpenRDAP, written in [[Go (programming language)|Go]]
* [https://rdap.dev/ rdap.dev] - {{dash}}A simplified web-based RDAP client
* [https://about.rdap.org/ rdap.org] - {{dash}}An end point for RDAP queries
* [https://www.apnic.net/apnic-info/whois_search/about/rdap RDAP page at APNIC]
* [https://www.arin.net/resources/rdap.html RDAP page at ARIN]