Registration Data Access Protocol: Difference between revisions

Revision as of 12:17, 31 May 2025

Revision as of 13:53, 31 May 2025

Line 94:

==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]]}}</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" />

Line 102:

== Query example ==

To query RDAP, there are several software and web clients ncluding icann-rdap (reference implementation command-line client by ICANN), OpenRDAP (independent command-line client), and rdap.dev web client.

As with WHOIS, normally the contact information of the resources assignee is returned. However, some registrars offer private registration, in which case the contact information of the registrar is shown instead.

In certain jurisdiction, RDAP redacted contact information as required by regulations such as [[General Data Protection Regulation]] (GDPR). Such contact information may be accessed with Registration Data Directory Services (RDDS).<ref name=":0" /> Non-public contact information can be accessed 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>

Some registry operators are wholesalers, meaning that they typically provide ___domain name services to a large number of retail registrars, who in turn offer them to consumers. For private registration, only the identity of the wholesale registrar may be returned. In this case, the identity of the individual as well as the retail registrar may be hidden.

Below is an example of RDAP data returned for an individual resource holder. This is the result of a RDAP query (using OpenRDAP client) of website of ''[[Final Fantasy XIV]]'', with [[Markmonitor]] as registrar:<syntaxhighlight lang="doscon" highlight="1">