RDAP provides access to information about Internet resources: domain names, autonomous systems, and IP addresses.
RDAP.org aims to support users and developers of RDAP clients by providing a 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.
If you are developing an RDAP client, configure it to send HTTP requests to http://rdap.org/<type>/<object>, where <type> is the object type (one of domain, nameserver, ip, autnum etc) and <object> is the object identifier (eg example.com, 192.168.0.1, 64496, etc).
If RDAP.org knows of an RDAP service which is authoritative for this resource, your client will receive a 301 redirect to the appropriate URI. If no resource is known, you will receive a 404 error.
The rdapper client uses RDAP.org by default, and can be used to verify the behaviour of the RDAP.org service.
If you are implementing an RDAP service, you can redirect queries for unknown objects to rdap.org, and we will dispatch the client to the appropriate authority (if we know it).
Note that the responses returned by the above services may not conform to the current draft specifications for RDAP.
If you would like to submit feedback, or operate an RDAP service that you would like to be added to RDAP.org, please click here (apologies for the captcha, but I get a lot of spam).
RDAP.org is proudly brought to you by Tau.