Welcome to UKRNAMES.COM RDAP Server!
The Registration Data Access Protocol (RDAP) is the successor to WHOIS
If you are developing an RDAP client, configure it to send HTTP requests to https://rdap.ukrnames.com/domain/[domain-name], where [domain-name] is the requested domain
(For example:
https://rdap.ukrnames.com/domain/dotukr.com).
HTTP Status Codes
- 302 – occurs when rdap.ukrnames.com knows of an RDAP service which is authoritative for the requested resource. Follow the URL listed in the Location header.
- 400 – occurs when rdap.ukrnames.com receives an invalid request (malformed path, unsupported object type, invalid domain, etc).
- 404 – occurs when rdap.ukrnames.com doesn’t know of an RDAP service which is authoritative for the requested resource.
- 500 – occurs when rdap.ukrnames.com is broken in some way.
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
- The Number Resource Organization (NRO) developed the NRO RDAP profile for RIR RDAP services.