The Registrant module can be used to store ownership data for a domain name, email address or any asset represented by a domain name. It's focus is on the legal entity name, type and address.
It does not include any other contact information. Contact information should be provided in the Contacts module.
An example record is shown below.
As stored in the DNS
This shows an example Registrant record stored minified in the DNS:
Unpacked and Developer Friendly
This shows an example Registrant record after it's been unpacked using the record configuration file:
This module has a simple specification, implementations should be built based on the example above and the information below.
This module does not set out to describe every possible entity type worldwide because this is a very complex area . The module simply specifies an
individual, these are defined at the root of the record.
Organisations and individuals are described with the following fields:
|name||The name of the entity, e.g.
|identifier||An identifier that is unique to the entity in their country of registration (e.g. company registration number).||No|
|address||The address, not including the postcode / zip or country. Address is an array of strings.||No|
|postcode_zip||A postal code, the name varies by country but is often known as post code or zip code.||No|
|country||The country code in ISO 3166-1 alpha 2 format. For an individual this should be their country of residence, for companies it should be the country the company is registered in.||Yes|
|telephone||A telephone number in E.164 format, e.g. +441234567890.||No|
|An email address.||No|
|contacts||An array of further contact objects, options are detailed in the following section.||No|
|object_display_name||For display purposes. Either
Valid contact objects are
security. Each object can include the fields listed above with the exception of
identifier which can only be listed in the parent object. Each contact type has an