RDAP support

The API interface, is based on the IETF WEIRDS charter group.

To query for domain names, point the RESTful client to: /rdap/domain/example.com where example.com is the TLD to query (exact match).

As described in the draft-ietf-weirds-using-http-07 document, the content negotiation is done by setting the Accept HTTP header on the client.

However, our implementation also provides a way of requesting the response type by passing an extra parameter ?content-type="desired"

Another difference with the IETF implementation, is that this system supports XML, HTML, besides the standard JSON format.

To signal the server, set the content type as described above with one the following parameters:

JSON format as described in http://tools.ietf.org/html/draft-ietf-weirds-json-response-05
XML format with a XSL stylesheet to format it for browsers.
An HTML format produced from the XSL transformation.

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.


The WHOIS information provided on this page is intended to provide you with relevant contact information for a domain name registrant and the identity of certain administrative and technical contacts associated with the domain name.

The data in this record is provided by Uniregistry for informational purposes only, and it does not guarantee its accuracy. Uniregistry is authoritative for whois information in top-level domains it operates under contract with the Internet Corporation for Assigned Names and Numbers. Whois information from other top-level domains is provided by a third-party under license to Uniregistry.

This service is intended only for query-based access. By using this service, you agree that you will use any data presented only for lawful purposes and that, under no circumstances will you use (a) data acquired for the purpose of allowing, enabling, or otherwise supporting the transmission by e-mail, telephone, facsimile or other communications mechanism of mass unsolicited, commercial advertising or solicitations to entities other than your existing customers; or (b) this service to enable high volume, automated, electronic processes that send queries or data to the systems of any Registrar or any Registry except as reasonably necessary to register domain names or modify existing domain name registrations.

Uniregistry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. All rights reserved.