Module: Registrant

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.

Example

An example record is shown below.

As stored in the DNS

This shows an example Registrant record stored minified in the DNS:

@n=1;o(n=NUM Technology Ltd;id=10097965;a[39th Floor;One Canada Square;Canary Wharf;London];p=E14 5AB;co=GB;t=+441270123456;e=domains@num.uk;c[(AD(n=Mr Admin Contact;a[Admin Department;39th Floor;One Canada Square;Canary Wharf;London];p=E14 5AB;co=GB;e=domains-admin@num.uk;t=+441270654321));(TC(n=Ms Tech Contact;a[Tech Team;39th Floor;One Canada Square;Canary Wharf;London];p=E14 5AB;t=+441270111111;e=domains-tech@num.uk;co=GB));(SC(n=Ms Security Contact;a[Tech Team;39th Floor;One Canada Square;Canary Wharf;London];p=E14 5AB;co=GB;t=+441270222222;e=domains-security@num.uk))])
An example Registrant record.

Unpacked and Developer Friendly

This shows an example Registrant record after it's been unpacked using the record configuration file:

Loading
An unpacked Registrant record.

Specification

This module has a simple specification, implementations should be built based on the example above and the information below.

Entity Types

This module does not set out to describe every possible entity type worldwide because this is a very complex area Content on another site.. The module simply specifies an organisation or individual, these are defined at the root of the record.

Fields

Organisations and individuals are described with the following fields:

Name Explanation Required
name The name of the entity, e.g. John Smith or NUM Example Ltd. Yes
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 Content on another site. 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 Content on another site. format, e.g. +441234567890. No
email 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 Organisation or Individual depending on the entity_type at the root of the object. No

Contact Types

Valid contact objects are admin, technical and 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 object_display_name, e.g. Security Contact.

Record Configuration File

All records for this module must adhere to the record configuration file shown below, this record configuration file is written in MODL Content on another site.:

The record configuration file can also be seen here Content on another site.