Registrar query[Link]
Query[Link]
A registrar query returns data of a specific registrar. The query is of the form:
https://rdap-server/entity/id
https://rdap-server/entity/officialname
A registrar can be queried by using the full official organisation name or by its IANAid:
https://rdap.nic.brussels/entity/1234
https://rdap.nic.brussels/entity/Registrar Organization Name
Please note that the query string is handled case insensitive. So, the following examples all yield the same result:
https://rdap.nic.brussels/entity/Registrar Organization Name
https://rdap.nic.brussels/entity/registrar organization name
https://rdap.nic.brussels/entity/REGISTRAR organization name
Also note that the full organisation name must be used. So if the official organisation name is ‘DNS Belgium’, then ‘dns belgium’ will return the registrar data. ‘DNS’ or ‘dns’ will not return a result.
IANA ID is preferred over official name. If a registrar has an official organisation
name 1234 and another registrar has IANA ID 1234, the registrar with
IANA ID 1234 will be returned..
If multiple registrars have the same official organisation name, a random registrar -will be returned.
Response[Link]
The response looks like:
{
"rdapConformance": [
"rdap_level_0",
"icann_rdap_technical_implementation_guide_0",
"icann_rdap_response_profile_0"
],
"objectClassName": "entity",
"notices": [
{
"title": "Terms of Service",
"description": [
"By executing a query, in any means whatsoever, you agree to these Terms of Service."
],
"links": [
{
"href": "https://www.dnsbelgium.be/en/rdap"
}
]
}
],
"events": [
{
"eventAction": "last update of RDAP database",
"eventDate": "2019-06-26T08:15:32Z"
}
],
"handle": "1234",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Registrar Organization Name"
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+32.123456789"
],
[
"email",
{},
"text",
"official.email@registrar.tld"
],
[
"adr",
{
"cc": "BE"
},
"text",
[
"",
"",
"Street",
"City",
"",
"",
""
]
]
]
],
"roles": [
"registrar"
],
"publicIds": [
{
"type": "IANA Registrar ID",
"identifier": "1234"
}
],
"entities": [
{
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Administrative Name"
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+32.123456789"
],
[
"email",
{},
"text",
"admin@registrar.tld"
]
]
],
"roles": [
"administrative"
]
},
{
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Technical Name"
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+32.123456789"
],
[
"email",
{},
"text",
"admin@registrar.tld"
]
]
],
"roles": [
"technical"
]
}
]
}
The response is built up in different sections.
Events[Link]
last update of RDAP database: date and time the data in the RDAP backend was last updated from the registry backend. Because the data from the RDAP backend is not cached, it is equal to the date and time the response was generated
All event dates have UTC timezone and are formatted in the Internet date/time format (RFC 3339).
Example:
2019-06-20T14:58:28Z
Registrar[Link]
The response of a registrar query includes an entity with the registrar role, with the following data:
The official organisation name of the Registrar (see
fn)The IANA ID of the Registrar. The IANA ID is stored in:
handle
a publicIds element of type IANA Registrar ID
Email address, phone number and address of the Registrar.
Contacts[Link]
The administrative or technical contacts of the registrar are returned with the following date:
fn
phone
email
No other information is disclosed.
Error responses[Link]
Registrar not found[Link]
When a registrar is not found, the HTTP return code is 404:
HTTP/1.1 404 Not Found
The JSON response contains a short error message:
{
"errorCode": 404,
"title": "Entity DEMO not found"
}
Bad request[Link]
When an invalid input is requested, the HTTP return code is 400:
HTTP/1.1 400 Bad Request
The JSON response contains a short error message:
{
"errorCode": 400,
"title": "Invalid entity",
"description": [
"Entity ID too long"
]
}