RDAP databases for assigned IP numbers are maintained by five [[Regional Internet registry|Regional Internet registries]]. [[American Registry for Internet Numbers|ARIN]] maintains a bootstrap database.<ref>{{cite web |url=https://www.arin.net/resources/registry/whois/rdap/rdap.pdf |title=RDAP at ARIN |date=September 17, 2019}}</ref> Thanks to the standard document format, tasks such as, for example, getting the abuse team address of a given IP number can be accomplished in a fully automated manner.<ref>{{cite web |title=abuserdap |url=https://savannah.nongnu.org/support/?110246}}</ref>
==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 [[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. 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>{{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" />
