Specification: nominet_profile_0
Nominet operates a number of registries that are not subject to ICANN’s consensus policies which drive key differences in the definition of the data we make available via RDAP. Nominet has based our own profile on ICANN 2024 gTLD Registry profile.
Key differences from ICANN standard RDAP for gTLDs
| Item | ICANN 2024 gTLD Registry profile | nominet_profile_0 |
|---|---|---|
| Conformance declaration | icann_rdap_technical_implementation_guide_1 icann_rdap_response_profile_1 | nominet_profile_0 |
| Registrar identifier | Registrars are required to be ICANN accredited. The registrar ‘handle’ is the IANA registrar ID. | Not all registrars are ICANN accredited and therefore some do not have an IANA registrar ID. Nominet utilise the ‘CLID’ from Extensible Provisioning Protocol (EPP) as the unique identifier of the registrar accreditation for registries conforming to this profile. |
| Registrar RDAP links | ICANN operates a distributed registration model where elements of authoritative data is held at the registry and at the registrar. Registrars are required to operate their own RDAP servers and serve accurate data. Referral links exists from the registry RDAP to the registrar RDAP server. | The registry is the sole source of authoritative data for the registry. Registrars are not required to operate an RDAP server. No links exist from the registry RDAP response to a registrar RDAP. |
| Complaints URL | https://icann.org/wicf | https://www.nominet.uk/ complaints/#complaining-about-incorrect-whois-data |
This profile allows RDAP clients to recognise that the response should be interpreted according to Nominet’s registry-specific behaviour.
Minerva House, Edmund Halley Road, Oxford Science Park, OX4 4DQ, United Kingdom