Afilias RDAP

This is a test implementation of RDAP (Registration Data Access Protocol) for .info domains managed by Afilias Inc.

RDAP is a proposed replacement for Whois that was developed by the WEIRDS working group of the IETF. It provides a access to information about registered domains and IP addresses, using a RESTful interface over HTTP that returns structured data, unlike the free-form data from Whois.

This implementation conforms to the following RFC specifications:
  RFC7480 HTTP Usage in the Registration Data Access Protocol (RDAP)
  RFC7481 Security Services for the Registration Data Access Protocol (RDAP)
  RFC7482 Registration Data Access Protocol (RDAP) Query Format
  RFC7483 JSON Responses for the Registration Data Access Protocol (RDAP)

Support is provided for the following objects: domain, entity, nameserver.
Examples:
  http://rdg.afilias.info/rdap/domain/dog.info
  http://rdg.afilias.info/rdap/entity/R-R171-LRMS
  http://rdg.afilias.info/rdap/nameserver/ns1.ams1.afilias-nst.info

Since Afilias is a Domain Name Registry (DNS) only, it does not support Regional Internet Registry (RIR) objects ip or autnum. Queries for such objects will return HTTP 501 Not Implemented.
Example:
  http://rdg.afilias.info/rdap/ip/192.0.2.0

Search is supported with some limitations.
1) Search for internationalized domains and nameservers is not supported and will return HTTP status 422 Unprocessable Entity.
2) Search for entities by name is restricted to Registrars only. Other Contacts can only be searched by handle.
3) A maximum of 50 names is returned. If there are more results, an entry of type "result set truncated" will be included in the notices. There is no way to continue the search for the next block of names.
Examples:
  http://rdg.afilias.info/rdap/domains?name=dog*.info
  http://rdg.afilias.info/rdap/entities?fn=go*
  http://rdg.afilias.info/rdap/entities?handle=R-R17*
  http://rdg.afilias.info/rdap/nameservers?name=ama*
  http://rdg.afilias.info/rdap/nameservers?ip=65.22.*

The following built-in test cases can be used to test some of the more complex features. Embedded links in the output generally do not work since the handles in the links are from stored data and are not current.
  DNSSEC - http://rdg.afilias.info/rdap/domain/dnssec.test
  IDNs and Variants - http://rdg.afilias.info/rdap/domain/idn.test
  Domain with Two Admin Contacts - http://rdg.afilias.info/rdap/domain/two-admins.test

IDN (Internationalized Domain Names)
Domain and nameserver object names may be either ASCII or Unicode/UTF-8.
The following return the same result:
  http://rdg.afilias.info/rdap/domain/ø-ø.info
  http://rdg.afilias.info/rdap/domain/xn--114-vm7le44f.info

Case Sensitivity
Domain, nameserver and entity object names are case insensitive.
Entity objects requested with the handle ID are case sensitive.

Media Type
The response Content-Type will be application/rdap+json if the HTTP Accept header includes application/rdap+json or application/json. Otherwise, the response Content-Type will be text/plain, and the output will be indented. This makes it easy to test and verify results using a browser.
Compare the following with a browser response.
  curl -H "Accept: application/rdap+json" http://rdg.afilias.info/rdap/domain/dog.info

Redirection
If a query is received for a domain or nameserver other than .info, it will not be redirected and HTTP status 422 Unprocessable Entity will be returned.

Authentication
No authentication is required, only public data is provided. The data returned corresponds to the Afilias Whois server for .info at whois.afilias.info

Whois
For comparison with command line Whois, replace 'rdap' with 'whois' in the url, as in
  http://rdg.afilias.info/whois/domain/dog.info

Rate Lmiting
To avoid response failures due to rate limiting, there should be less than 10 requests per minute. This is not a guarantee to avoid rate limiting, as the limit is applied to the aggregate requests from the RDAP test server, not from the individual client. A rate limited request will be returned with HTTP status 429 Too Many Requests.

Comments
For any questions or comments, please fill in the following and click Submit.

Email Address
Comment