The Registration Data Access Protocol (RDAP) is the successor to WHOIS. Like WHOIS, RDAP provides access to information about Internet resources (domain names, autonomous system numbers, and IP addresses). Unlike WHOIS, RDAP provides:

• A machine-readable representation of registration data;
• Differentiated access;
• Structured request and response semantics;
• Internationalisation;
• Extensibility.

RDAP.org aims to support users and developers of RDAP clients by providing a "bootstrap server", i.e. single end point for RDAP queries. RDAP.org aggregates information about all known RDAP servers. RDAP clients can send RDAP queries to RDAP.org, which will then redirect requests to the appropriate RDAP service.

Note: RDAP.org is not affiliated with ICANN or IANA.

How To Use RDAP.org

Client Implementers

If you are developing an RDAP client, configure it to send HTTP requests to https://rdap.org/<type>/<object>, where <type> is the object type (one of domain, ip, autnum, entity etc) and <object> is the object identifier (eg example.com, 192.168.0.1, 64496, etc).

HTTP Status Codes

• 302 – occurs when RDAP.org knows of an RDAP service which is authoritative for the requested resource. Follow the URL listed in the Location header.
• 400 – occurs when RDAP.org receives an invalid request (malformed path, unsupported object type, invalid IP address, etc).
• 404 – occurs when RDAP.org doesn’t know of an RDAP service which is authoritative for the requested resource.
• 500 – occurs when RDAP.org is broken in some way.

Additional Resources

Apart from the DNS, ASN and IP registries which are listed in the IANA registry, RDAP.ORG also provides the following unofficial RDAP server endpoints:

• Top-level domains – each TLD has its own RDAP record at https://root.rdap.org/domain/{TLD}. You can also get an RDAP search result for all TLDs using https://root.rdap.org/domains. This data is generated from the IANA whois (Git repository).
• ICANN-accredited registrars – you can obtain RDAP records for ICANN-accredited registrars at https://registrars.rdap.org/entity/{NNNN}-iana where {NNNN} is the numeric IANA ID. These records are synthesised from data published by IANA and ICANN (Git repository).

References

These are the authoritative references for the RDAP protocol specifications:

• RFC7480: HTTP Usage in the Registration Data Access Protocol (RDAP)
• RFC7481: Security Services for the Registration Data Access Protocol (RDAP)
• RFC9082: Registration Data Access Protocol (RDAP) Query Format
• RFC9083: JSON Responses for the Registration Data Access Protocol (RDAP)
• RFC7484: Finding the Authoritative Registration Data (RDAP) Service
• RFC8056: Registration Data Access Protocol (RDAP) Object Tagging
• All generic TLDs (and some ccTLDs) are compliant with the gTLD RDAP Profile
  • Technical Implementation Guide (PDF)
  • RDAP Response Profile (PDF)
• The Number Resource Organization (NRO) developed the NRO RDAP profile for RIR RDAP services.

Privacy Considerations

If you use RDAP.org to perform RDAP queries, your queries will be logged, alongside your IP address. These logs are not disclosed to anyone and are deleted within a few days. RDAP.org will not set any cookies in your browser.

Submit Feedback

If you would like to submit feedback please click here.

About RDAP.org

RDAP.org is maintained by Gavin Brown.

You can review the code which RDAP.org uses on GitHub.

Supporting RDAP.ORG

If your organisation depends on RDAP.org, then please consider supporting it, since it's not free to operate and requires ongoing maintenance and management.

If youd would like to support this service, please email support@rdap.org to dicuss options.