The field names shown here are used by all of our domain management tools and relate to fields stored in our registry. While only certain fields may be mandatory for an operation, we encourage registrars to provide values for as many of the fields as possible.
| Field | Description |
|---|---|
| a1-email ... a3-email | The email address for the first to third admin contacts, respectively. |
| a1-id ... a3-id | The ID that specifies the first to third administrative contact to work on, respectively. |
| a1-mobile ... a3-mobile | The mobile phone number for the first to third admin contacts, respectively. You may provide two phone numbers per contact by using this field a second time in the same template. |
| a1-name ... a3-name | The name of the first to third admin contacts, respectively. |
| a1-phone ... a3-phone | The phone number for the first to third admin contacts, respectively. You may provide two phone numbers per contact by using this field a second time in the same template. |
| account-id | The ID that specifies the account object to work on. |
| account-name | The company or individual whom the domain name is registered on behalf of. This field can only be changed after the initial registration by completing the registrant transfer process. |
| addr | The street address of the main administrative address for the account. Multiple lines can be specified either with multiple uses of this field or one field with a caret (^) character separating address lines. |
| auto-bill | Used to indicate how many days before expiry you wish to automatically renew a domain name. We strongly recommend reading about our renewal processes before setting this field. The auto-bill field is set with a value of between 1 and 182, indicating how many days before expiry you wish to renew the domain name. This field can be cleared by setting the default value of 0. Auto-bill cannot be set if next-bill, recur-bill or renew-not-required are set. |
| changed | The date and the user who last changed the domain object, formatted as: user YYYYMMDD The user could be a name and email address or the value submitted from the <clTRID> element if changed from EPP. If it is an name and email address then it may contain spaces. |
| city | The city of the main administrative address. |
| co-no | The registered company number or the DfES UK school number of the registrant. |
| contact-id | The ID that specifies the contact object to work on. |
| county | The county of the main administrative address. |
| country | The two letter ISO 3166 Country Code of the main administrative address. |
| crDate | The date the domain name was created, formatted as: YYYYMMDD |
| created | The date and the user who created the domain name, formatted as: user YYYYMMDD The user could be a name and email address or the value submitted from the <clTRID> element if created by EPP. If it is a name and email address then it may contain spaces. |
| crID | The user that created the domain name. Contains either the email address from which the original creation message was sent or the TAG if they used EPP. If it is an email address then it may contain spaces. |
| dns | The hostname of the specified nameserver object. This field can also specify the IP address of the nameserver. A space is used to separate the domain name from the IP address. For example: ns0.nserver.co.uk 121.121.121.121 |
| dns0 ... dns9 | The hostname of the first to tenth nameserver, respectively. This field can also specify the IP address of the nameserver. A space is used to separate the domain name from the IP address. For example: ns0.nserver.co.uk 121.121.121.121 |
| Email address for the specified contact. | |
| exDate | The date the domain name is due to expire on, formatted as: YYYYMMDD For some registrations this field may not be present or may be blank, which indicates that the registration has no set expiry date. |
| expiry | The date the domain name is due to expire on, formatted as: YYYYMMDD For some registrations this field may not be present or may be blank, which indicates that the registration has no set expiry date. |
| first-bill | Used to mark domain names to be billed directly by Nominet for registration fees. We strongly recommend reading about our renewal processes before setting this field. The first-bill field is set with a value of bc. This field can be cleared by setting the default value of th. |
| key | The domain name. The maximum length of a domain name that you can register (including the .co.uk, .ltd.uk, etc) is 63 characters. The only characters allowed in a domain name are the 26 letters of the alphabet, numbers 0-9 and dashes/hyphens (-). A domain name cannot begin or end with a dash. Detailed rules of registration and use of domain names are available. |
| locality | The locality of the main administrative address. |
| mobile | Mobile numbers for the specified contact. |
| name | The name for the specified contact. |
| next-bill | Used to indicate how many days before expiry you wish to automatically renew a domain name. The next-bill field will reset to 0 after a single registration period. We strongly recommend reading about our renewal processes before setting this field. The next-bill field is set with a value of between 1 and 182, indicating how many days before expiry you wish to renew the domain name. This field can be cleared by setting the default value of 0. Next-bill cannot be set if auto-bill, recur-bill or renew-not-required are set. |
| notes | A free form field for miscellaneous information relating to the domain name. |
| operation | The operation you are requesting the Automaton to perform. |
| opt-out | Used to prevent the registrant's address details from being published in our WHOIS system. The opt-out field is set with a value of y. This field can only be set if the registrant is an individual who is using the domain name for a purpose unconnected with any business, trade or profession. As such, use of the opt-out field is restricted to certain types of registrants. This field can be cleared by setting the default value of n. |
| period | This field is currently unused but is included in the EPP schemas for forward compatibility. When it can be used it will enable registrations for periods other than two years. |
| phone | Phone numbers for the specified contact. |
| postcode | The postcode field of the main administrative address. The postcode must be in uppercase with a space between the two parts of the postcode. Postcodes are validated to verify that they are formatted correctly. If you follow the postcode guidelines from GovTalk, the postcode should be accepted. |
| recur-bill | Used to mark domain names to be billed directly by Nominet for renewal. We strongly recommend reading about our renewal processes before setting this field. The recur-bill field is set with a value of bc. This field can be cleared by setting the field to the default value of th. Setting recur-bill to bc clears out the auto-bill and next-bill fields. |
| reg-status | The registration status of a domain name. Field values will be from our list of registration statuses. |
| registrar-tag | This is the tag the domain name is currently on. When used with a release or transfer operation, this is the tag of the registrar receiving the domain name. |
| renew-not-required | Used to mark domain names that the registrant does not intend to renew. The domain name will be cancelled on expiry. Setting this field will prevent Nominet from sending renewal reminders to the registrant. When set, a single email notification will be sent to the registrant to advise that the domain name will not be renewed. The renew-not-required field is set with a value of y. This field can be cleared by renewing the domain name or by the registrant using our Online Service to change registrar. This field cannot be set if either auto-bill or next-bill fields are set. |
| reseller | An optional field which can be used to associate a reseller with a domain. You must use Online Services to set values for this field. |
| trad-name | The trading name of the organisation if different to the account-name. |
| type | This describes what type of organisation the domain name has been registered for. The field value must be from our list of registrant types. |
| upDate | The date the domain name was last changed, formatted as: YYYYMMDD |
| upID | The user that last changed the domain name. The user could be a name and email address or the value submitted from the <clTRID> element if created by EPP. If it is a name and email address then it may contain spaces. |
The following table shows fields which still work, but are being phased out. Use of these fields will generate a non-fatal error but will not prevent your operation from completing. If a deprecated field is no longer held in the registry, we will not store the submitted value. If a deprecated field has been replaced by a newer field, we will store the submitted valued against the new field.
| Field | Description |
|---|---|
| a-addr | This field is will longer be held in the registry. |
| a-email | This field will no longer be held in the registry. |
| a-phone | This field will no longer be held in the registry. |
| a1-fax ... a3-fax | These fields will no longer be held in the registry. |
| admin-c | This field will no longer be held in the registry. |
| b-addr | This field will no longer be held in the registry. |
| b-city | This field will no longer be held in the registry. |
| b-country | This field will no longer be held in the registry. |
| b-county | This field will no longer be held in the registry. |
| b-locality | This field will no longer be held in the registry. |
| b-postcode | This field will no longer be held in the registry. |
| b1-email ... b3-email | These fields will no longer be held in the registry. |
| b1-fax ... b3-fax | These fields will no longer be held in the registry. |
| b1-id ... b3-id | These fields will no longer be held in the registry. |
| b1-mobile ... b3-mobile | These fields will no longer be held in the registry. |
| b1-name ... b3-name | These fields will no longer be held in the registry. |
| b1-phone ... b3-phone | These fields will no longer be held in the registry. |
| fax | This field will no longer be held in the registry. |
| for | This field has been replaced by the account-name field. |
| ips-key | This field has been replaced by the registrar-tag field. |
| reg-addr | This field has been replaced by the addr field. |
| reg-city | This field has been replaced by the city field. |
| reg-co-no | This field has been replaced by the co-no field. |
| reg-contact | This field has been replaced by the a1-name field. |
| reg-contact-id | This field has been replaced by the a1-id field. |
| reg-country | This field has been replaced by the country field. |
| reg-county | This field has been replaced by the county field. |
| reg-email | This field has been replaced by the a1-email field. |
| reg-locality | This field has been replaced by the locality field. |
| reg-mobile | This field has been replaced by the a1-mobile field. |
| reg-opt-out | This field has been replaced by the opt-out field. |
| reg-phone | This field has been replaced by the a1-phone field. |
| reg-postcode | This field has been replaced by the postcode field. |
| reg-trad-name | This field has been replaced by the trad-name field. |
| reg-type | This field has been replaced by the type field. |