Nominet

Home Registrants Registrars Governance .uk Policy Disputes/Legal News About Us Intelligence Technology ENUM Other Services

Skip All Secondary and Tertiary Navigation

Become a Registrar Registrar Agreement Fees Renewals Registrar Systems DNSSEC Reseller Data Anti-abuse Registrar Resources Working Groups FAQ

Home › Registrars › Registrar Systems › Automaton › Error Messages

Print this page | Contact Us

Error messages

If there is an issue with a command or an operation submitted to one of our domain management tools, you will receive an error message. There are several types of error messages that you may receive:

Fatal error
Receiving a fatal error means that the command (or operation) you submitted was not successful and changes were not made to the registry. The Automaton, EPP and the Web Domain Manager can produce fatal errors which can be identified by the letter "V" followed by three numbers. e.g. V028. Fatal errors can often be addressed by making a minor change to your request.
Non-fatal error
These are warning messages and can be appended to successful commands and operations. Even though your command or operation was successful, a non-fatal error warns you that there is an issue that could prevent you from performing future commands or operations.

Fatal errors

Error Code		Description
V001	Subject Line contains unknown action	The Automaton checks each message's subject line to determine what action to take with the request. If this does not correspond to one of the possible actions it returns this error. Details of the correct subject line can be found in the documentation for each operation.
V002	Nominet have notified you that any further applications to register new domain names will be refused.	The tag you have used is not currently active. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information.
V007	Unknown field '<xxx>'	A template is given for each of the Automaton requests in the documentation for the operation type. Any fields given which do not appear in the template will not be recognised and will cause the Automaton to abandon processing the request with this error.
V008	No Domain name given	This error occurs if you perform an operation on a domain, such as renew, but either do not include the 'key' field or a value within it.
V009	Domain <xxx> cannot be requested via this automaton	Our systems will only accept requests for .uk domains under our defined second levels. This error will occur if you request a domain that we either do not administer or includes an additional prefix such as 'www.'.
V010	Domains with two letters are not allowed	Third level domains under co.uk, me.uk, net.uk and org.uk cannot consist of two letters. For further information please see clause 5.6 of our registration rules.
V011	Domains with one character are not allowed	Third level domains under co.uk, me.uk, net.uk and org.uk cannot consist of just one character. For further information please see clause 5.5 of our registration rules.
V012	Fully-qualified domain names must be no longer than <xxx> characters	The maximum length of a registration up to and including .uk is 64 characters. For further information please see clause 5.7 of our registration rules.
V013	The account name field cannot be modified	Changes to the organisation name on a registrant contact (the registrant for the domain name) can only be made by a registrant transfer or by our support staff in the case of minor corrections.
V014	The tag '<xxx>' has been barred from creating or retagging domains.	The tag used is currently barred from performing this action. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information.
V015	The tag '<xxx>' has been barred.	The tag used is currently barred from performing any actions. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information.
V016	The tag '<xxx>' is unrecognised	This error occurs when an invalid tag is used in the 'registrar-tag' field, often due to the tag not being provided in capital letters.
V017	bad value for `first-bill' field (must be either `th' or `bc')	The 'first-bill' field can only be set to either 'th' or 'bc' ('NULL' to clear).
V018	bad value for `recur-bill' field (must be either `th' or `bc')	The 'recur-bill' field can only be set to either 'th' or 'bc' ('NULL' to clear).
V019	Missing account name	The 'account-name' field is mandatory when creating a new account. It specifies whom the registrant contact (and domain names) is registered for and cannot be modified by the registrar at a later date.
V020	Missing or invalid account identifier	Operations relating to a specific registrant contact must include the account-id number.
V023	Error Reading Nameserver <xxx>	This error occurs when invalid information or characters are provided in the name server details.
V024	Missing glue record for server <xxx>	When a name server is provided that is the child of the domain supplied in the request, it is necessary to create a glue record by including its IP address.
V025	Bad IP address for server <xxx> : <xxx>	An IP address will be treated as invalid if it: Starts with 0, 10, 127, 192.168. Starts within 172.16 to 172.32.
V027	Bad value for `type' (must be one of LTD, PLC, PTNR, LLP, STRA, IND, OTHER, FCORP, FOTHER, RCHAR)	Please see our registrant types page for full details regarding the 'type' field.
V028	Invalid country code for <xxx> (must be the two-letter ISO 3166 country code)	The country code used in the 'country' field must be a valid two-letter country code from ISO 3166.
V029	Invalid postcode: <xxx>	Postcodes are validated to verify that they are formatted correctly. If you follow the postcode guidelines from GovTalk, the postcode should be accepted.
V030	<xxx> field is too long (<xxx> is maximum)	Most fields have a limit of 200 characters, the exceptions being: 'co-no' up to 50 characters. 'addr' up to 3 lines of 255 characters. 'notes' up to 15 lines of 256 characters.
V036	Too many nameservers specified (10 is maximum)	You can only provide a maximum of 10 name servers for a registration.
V040	Bad month '<xxx>' specified for list action (Must be of form CCYY-MM)	The format of the month field must be Year-Month, for example March 2007 is 2007-03.
V044	Unrecognised PGP format	The most common reason for this error is sending an automaton request in MIME/HTML format. This causes a duplicate message to be sent in the Automaton request. This error can also happen when: The Automaton request has been PGP signed more than once There is corruption to the ASCII armor that surrounds the PGP message and signature
V045	Error occurred during PGP decode	This error can be caused by a corruption of the PGP signature or the surrounding ASCII armor lines, these being: -----BEGIN PGP SIGNED MESSAGE----- -----BEGIN PGP SIGNATURE---- -----END PGP SIGNATURE---- This may be due to the wrong method being used when signing the message, errors copying the message to an email after generation, or by the email client modifying the message. If using PGP 9 or above, please also check that the Hash algorithm is set to SHA-1. The hash setting should be displayed at the top of a signed message and can changed within the PGP program by double clicking on your key and selecting edit from the hash drop down menu.
V046	Message not in Clear Text Signed Format	This error occurs when the message received by the Automaton has either been encrypted or has not been PGP signed.
V047	Signing Key not recognised	This error occurs where the key used to sign the request has not been registered with our system. It is not possible to determine either the validity of the message or the requestor’s identity. Details on how to add a new key can be found on our PGP registration page. You may also receive this error if you sign an Automaton request with a PGP key recently added to our system. The Automaton's key update occurs daily around 8pm (GMT).
V048	Signature did not match the text	view full description
V049	Key has been revoked	The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page.
V050	Key has been disabled	The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page.
V051	Key has expired	The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page.
V052	Signature has a timestamp in the future	The Automaton compares the current time with time found in the sender’s PGP timestamp. The error will occur if the timestamp is more than five minutes fast. In most cases this issue can be resolved by correcting the system time, date and time zone of the computer used to PGP sign the message.
V053	Duplicate Nameserver found in list	Duplicate name servers cannot be provided for the same registration.
V055	You may not retag to NOMINET.	The NOMINET tag is reserved for situations where a host has name servers but does not have a tag. This change can only be made directly by us at the request of the registrant.
V057	Invalid field '<xxx>' for <xxx> operation	Occurs if a field name is not valid for the stated operation. This is very commonly caused by the field name starting with a capital letter.
V058	This Request will have no effect	The request does not contain any information to act upon. Often this is caused by lines being ignored due to incorrect field names or a problem with their formatting such as the use of capital letters.
V060	Message contained no requests	Occurs if no fields are present in a request after any invalid text has been removed.
V061	Nameserver '<xxx>' appears to be an IP address	An IP address can accompany the name server's host name in cases where a glue record is required, but our systems do not allow the IP address to be provided on its own.
V063	Multiple Instances of Field '<xxx>' found	This error will occur if a field, other than 'addr' or 'notes', is used more than once in a single request.
V064	ISO 3166 Country Code required for <xxx> country.	The mandatory value for 'country' field has been omitted. For a list of valid two-letter country codes, please refer to ISO 3166.
V065	postcode required for GB, GG, JE and IM Country codes for <xxx> address	The 'postcode' fields are mandatory if the country codes GB, GG, JE or IM are used in the 'country' field.
V069	'<xxx>' field missing or empty	No data has been provided for a mandatory field in a registration request.
V070	Missing admin address	No data has been provided for the mandatory 'addr' address field in a registration request.
V071	Missing admin contact	No data has been provided for the mandatory primary administrative contact in a registration request
V073	Invalid Company Number	For registrations where the LTD or PLC registrant types are used, the company number provided must consist of one or more numbers, and may be preceded by SC, NI, FC, BR, SF or NF. For registrations where the LLP registrant type is used, the company number provided must consist of one or more numbers, and may be preceded by LP, NL, SO, OC or SL. For registrations where the SCH registrant type is used, the DfES school number provided must consist of seven numbers. For English school numbers, you should also separate the third digit from the fourth with a hyphen.
V074	Company Number required for UK Limited and Public Limited Companies	For registrations where the LTD or PLC registrant types are used, the company number provided in the 'co-no' field must consist or one or more numbers, possibly preceded by SC, NI, FC, BR, SF or NF.
V076	Only 100 requests permitted in a single email	A maximum of 100 requests can be submitted to the Automaton in a single PGP signed email. Mass modifications can also be made using the Automaton’s bulk operation.
V077	Company Number required for LLP reg-types	For registrations where the LLP registrant type is used, the company number provided in the 'co-no' field must consist or one or more numbers, possibly preceded by LP, NL, SO, OC or SL.
V078	School Number required for schools	For registrations where the SCH registrant type is used, the DfES school number provided in the 'co-no' field must consist of seven numbers. For English school numbers, you should also separate the third digit from the fourth with a hyphen.
V079	Company Number not required for <xxx> reg-types	No information should be provided in the 'co-no' field unless the registrant type listed in the 'type' field is LTD, PLC, LLP, SCH, RCHAR.
V080	The 'co-no' field cannot be modified for an sch.uk domain name	Please contact our support department to inform us of any update to a school's DfES number.
V081	Reg type must be LTD for .ltd.uk domain name	The registrant type 'LTD' must be set in the 'type' field when making a ltd.uk domain registration.
V082	Reg type must be PLC for .plc.uk domain name	The registrant type 'PLC' must be set in the 'type' field when making a plc.uk domain registration.
V083	Invalid 'opt-out' field	The 'opt-out' field can only be set to either 'y' or 'n' ('NULL' to clear).
V084	No registrant type is specified for this registration. The registrant type must be specified either as a UK individual ('IND') or non-UK individual ('FIND') before the registrant may be permitted to opt-out of having their address details listed in the public register.	Only individuals may opt-out of having their address details listed in the WHOIS. The setting can only be made if the registrant type in the 'type' field is set to be 'IND' for UK individuals or 'FIND' for non UK individuals.
V085	Only individuals may opt-out of having their address details listed in the public register.	Only individuals may opt-out of having their address details listed in the WHOIS. The setting can only be made if the registrant type in the 'type' field is set to be 'IND' for UK individuals or 'FIND' for non UK individuals.
V086	Contents of field <xxx> cannot be removed	This occurs if an attempt is made to remove the contents of a field that is either mandatory or required by other existing fields.
V088	You have exceeded your credit limit and any tags associated with your account are now suspended pending further payment. Please contact our Customer Support team to pay money into your account or any overdue invoices.	This request would cause you to exceed your advised credit limit and any tags associated with your account are now suspended until further payments have been received. Therefore, you are no longer able to make any new registrations or renewals. Please contact our Member and Registrar Support team on +44 (0)1865 332233 as a matter of urgency to place an amount of money on your account or log on to your online account to pay any overdue invoices.
V089	Incorrect PGP constructs	The Automaton expects a single instance of each of the three PGP construct lines. This error can occur if your message is sent in MIME/HTML format or if there is an attachment in your message.
V094	Domain name exists already	This error occurs if you attempt to register a domain that is already registered.
V096	Domain name is not registered to your tag	This error will occur if you attempt to make changes to a domain that is either not on your tag or not registered.
V101	Domain names cannot be detagged in the first month of registration. If you wish to cancel this domain name please refer to http://www.nominet.org.uk/go/automaton - "Cancelling a Registration"
V102	Domain name not registered in the last 2 years.	Domain names can only be cancelled in the first registration period.
V105	Current and registering tag different.	Domain names cannot be cancelled if there has been a registrar change.
V107	Tag missing from subject line
V108	Tag in subject line does not match PGP signatory.
V109	Invalid bulk operation
V110	Field '<xxx>' cannot be modified using a bulk modification query.
V113	Old nserver must be non-blank for bulk n-server replacement.
V114	Nserver replacements and update bulk requests are not-compatible
V116	Field <xxx> appears more than once in update clause for bulk request.
V117	Field <xxx> empty
V120	Invalid date <xxx>
V121	Invalid tag field
V122	You cannot filter by tag
V123	You have exceeded usage limits for registration attempts on existing domain names. You will be blocked for 24 hours.
V124	You have been blocked from registering/checking domain names.	This error occurs if you have exceeded the acceptable use limits for registering domains which already exist.
V127	Domain names may not begin xn--
V128	Domain name is not within its renewal period or cannot be renewed.	A domain name can only be positively renewed up to 6 months in advance of the expiry date. This message will be returned if you send a positive renewal request outside of this 6 month period. This error can also occur due to a number of Nominet processes,including: - The registrant of a 'ltd.uk' or 'plc.uk' domain has changed their name - The registrant has been dissolved - Domain is scheduled for cancellation If you have questions about this, please contact our Member and Registrar Support Team.
V129	Domain names may not be renewed when recur-bill is set to 'bc'	When the recur-bill field is set to 'bc', it indicates that you wish Nominet to bill the registrant directly. In order to positively renew a domain name the recur-bill field needs to be set to 'th'.
V134	Bad value for <xxx> field (must be between 0 and 182)	The auto-bill field is used to indicate how many days before expiry you wish to renew a domain name. You can set an auto-bill field on a domain name with a value between 1 and 182 where the value indicates the number of days before expiry that a domain name will be renewed.
V138	Domain name contravenes naming rules
V140	'<xxx>' field may not currently be changed	This error will occur when either a modify or bulk operation updating the auto-bill or next-bill fields cannot be processed for all the domain names requested. For the bulk operation, the domain names that cannot be processed are listed. There are three reasons why the operation would fail for a particular domain name: 1. The recur-bill field is set to 'bc'. Auto-bill and next-bill cannot be set in this circumstance. 2. The domain name has expired. 3. The auto-bill or next-bill field must be set more than 1 day before it is due to be processed. For example you cannot set auto-bill or next-bill to 1 if the domain name expires in 2 day.
V141	Account <xxx> does not exist
V142	Account <xxx> is not on your tag
V143	Nameserver <xxx> does not exist
V144	Nameserver <xxx> is not on your tag
V145	<xxx> may not be set retrospectively	This error can occur if you attempt to set the auto-bill or next-bill fields to a date in the past. The value in these fields must be a date in the future. If the expiry date has passed but you wish to renew the domain name, then you can submit a renewal request.
V146	Contact <xxx> does not exist
V147	Contact <xxx> is not on your tag
V148	Both in-line and ? objects present.
V149	Bad IPV6 address for server <xxx> : <xxx>
V150	Domain name labels must not be longer than 63 characters
V151	Domain name has been paid for
V154	Invalid registrant identifier <xxx>
V156	Domain name has already been renewed.
V157	Auto-bill and next-bill cannot both be set.
V158	operation: field does not match subject	This error occurs if the operation in the subject line of the email and the 'operation' field do not match. This error can also occur if you use capital letters in the 'operation' field.
V159	Signature has a timestamp more than 3 days in the past	The Automaton compares the current time with the message sender’s time found in the PGP timestamp. The error will occur if the timestamp is more than 72 hours slow. This can usually be resolved by correcting the system time, date and time zone of the computer used to PGP sign the message.
V166	More than one ipv<xxx> address given for name-server
V169	Missing 'operation' field
V171	Name server is more than 255 characters
V172	Name server <xxx> is invalid - label has invalid length
V173	Name server <xxx> is invalid
V174	Domain name has already been renewed once in the last 24 hours	This error message occurs if there is an attempt to renew a domain more than once within a 24 hour period without specifying the current expiry date for the domain.
V175	You have exceeded cancellation usage limits
V178	next-bill or auto-bill cannot be set when recur-bill is 'bc'
V180	You must accept or reject the registrar change authorisation request	This error occurs if an invalid response is given to a registrar change authorisation request. Please refer to the registrar change authorisation request for possible valid responses.
V181	You cannot accept or reject the registrar change case-id <xxx>	You have tried to accept a case-id that doesn't exist or has expired.
V182	Attempt to 'like' a numeric field.	You have tried to do a bulk 'like' filter using account-id, auto-bill or next-bill.
V184	Missing identifier for contact modification
V185	Missing identifier for account modification
V186	Missing identifier for nameserver modification
V188	You cannot transfer to the account <xxx>	The domain names on the account are not on your tag.
V189	Account names do not match for the following domain names:
V190	Invalid operation <xxx>: <xxx>
V191	Invalid ID prefix '<xxx>', expecting '<xxx>'	An invalid contact, nameserver or account identifier has been provided.
V194	Operation blocked by Nominet process	This request cannot be made due to a Nominet process. This can occur for a number of reasons, including: - The registrant of a 'ltd.uk' or 'plc.uk' domain has changed - The registrant has been dissolved - Domain is scheduled for cancellation If you have questions about this, please contact our Member and Registrar Support Team.
V195	The following domain names may not be released due to a Nominet process:<xxx>	The listed domain names cannot be released due to other processes on them.
V196	Invalid registrar change case <xxx>
V197	Tag <xxx> do not accept registrar changes
V198	Account <xxx> is not on tag <xxx>
V199	A target account may not be provided for an account release
V200	Contact <xxx> is not on account <xxx>.
V204	Cannot change registrar-tag with modify operation; use release operation instead.
V205	Too many <xxx> numbers in request: Maximum is 10
V206	Invalid ID suffix <xxx>, expecting '-UK'.
V207	The following domains do not have account names that match that of the account specified:<xxx>
V208	The following domain names are not registered to your tag: <xxx>
V209	The set of domain names given could not be modified.
V210	Period format is invalid
V211	Period is outside acceptable range
V213	Length of %s must not exceed %s.
V217	DNS data out of sequence.
V227	Bad '<xxx>' field (must be between 1 and 9).	The auto-period and next-period fields can only have values between 1 and 9.
V228	'<xxx>' must be set for domains with a positive '<yyy>' field.	This error will occur if the auto-period field is set without the auto-bill field being set or if the next-period field is set without the next-bill field being set.
V230	Enumber range invalid	The lastE164Number provided is smaller than the E164Number.
V231	<xxx> format invalid	A date specified has not been provided in RFC 3339 format.
V232	Execution date is in the future	The execution date on the ENUM token is in the future.
V233	Expiration date is in the past	The expiration date on the ENUM token provided is in the past, it is advisable that you contact your validation agency to resolve this.
V234	RegistrarID in token is not your tag.	Occurs if a registrar sends an ENUM create when the tag specified upon login differs from the tag specified in the registrarID of the token.
V235	<xxx> invalid	Invalid number provided for E164Number or LastE164Number, for example if the number is too long or starts with a non-UK prefix.
V236	Enumber not on your tag.	Occurs if a request is made to modify or renew a registration if not on your tag and without a valid token.
V237	Enumber has already been renewed.	Occurs if a renew operation would not increase the expiry date by at least one day.
V238	Token is older than the current one	This is returned when the ENUM token provided has an older execution date than the current one stored.
V239	Part or all of Enumber range exists.	Occurs if a create command fails due to it overlapping with an existing registration.
V241	Token expires before registration	Occurs in a create operation where the expiry date of the token is less than a year in the future, or in a modify where a new token does not cover the remaining registration period.
V245	Domain name %s exists already.
V261	PGP signature expired.
V262	Bad renew-not-required field.
V263	Renew-not-required field can only be unset by renewal of the domain.
V264	Only 100 renewal reversals are permitted in a single request.
V265	The following domain names do not have a renewal request being processed:
V266	The account-id %ld does not correspond to a valid registrant account.
V267	A destination account-id may not be specified for this case.
V268	The destination account name does not match that of the domains associated with case %ld.
V269	This request will have no effect.
V270	Domain name already unrenewed in this registration period.
V271	Auto-bill/next-bill cannot be set when renew_not_required is set
V272	Company number and registrant type cannot be modified for registrar accounts..
V273	Renewals cannot be undone when auto.next billing fields are set.
V274	Schema %s not specified at login
V275	Domain is not locked
V276	Account is locked.
V277	Account id and domain name cannot both be specified
V278	Account is not locked.
V279	Account % exists already.
V280	A contact of order % already exists.
V281	Registration of domain %s has been blocked
V282	Invalid or missing lock type.
V283	Cannot add IPVs address to nameserver; nameservers should only have a maximum of one IPV4 and one IPV6 address.
V284	Account exists already.
V285	Contact-id %s exists already
V286	Nameserver already exists on your tag.
V289	Nameserver already exists	A host with that name already exists therefore cannot be created with that name/
V290	Too many domains for full-detail domain list operation	For performance reasons, the EPP list only returns up to 5000 domains with full details. There is no restriction for a list of domain names only.
V291	Glue record not allowed for the server <xxxx>	The IP address supplied is never required when the host's superordinate domain is not held in the registry.
V292	Domain <xxxx> does not exist	The domain name specified does not exist in our registry.
V293	Superordinate domain does not exist	This error occurs when the superordinate domain used for a host name should occur in our registry but does not.
V294	You do not have permission to modify the nameserver '<xxxx>'	To modify a nameserver object, the tag must be associated with either the superordinate domain name or all domain names linked to that nameserver.
V297	Reseller '<xxxx>' is not on your tag	To add reseller details to a domain name you must first add information regarding the reseller to your online service account. Reseller details can also be added or modified using the EPP Reseller commands
V300	An email address or a telephone number must be provided	This error occurs if you have attempted to create or modify a reseller without setting either an email address or a telephone number.
V301	Reseller references may only contain upper case letters A-Z, digits 0-9 and hyphens
V302	Reseller already exists on your tag using the same <xxxx>	This error occurs if a request is made to create or modify a reseller which would use the same reference or tradingName as an existing reseller on your tag.
V303	A well-formed email address must be provided
V304	Too many domains specified(<xxxx> is maximum)	No more than 100 domain names can be supplied in a Check command
V305	Your tag is not registered as DNSSEC enabled.	This error occurs if a request attempts to add or remove DS Records and you have not registered with us in Online Services to indicate that you support DNSSEC
V306	Too many dsData records specified (8 is maximum)	You can only provide a maximum of 8 DS records for a domain.
V307	Unsupported secDNS attribute 'urgent' found.	We do not support the "urgent" attribute from RFC-5910
V308	Unsupported secDNS element 'maxSigLife' found.	We do not support the "maxSigLife" element from RFC-5910
V309	Unsupported secDNS interface 'keyData' found.	We do not support the "keyData" interface described in RFC-5910
V310	Unsupported algorithm '<nnn>' found.	The algorithm specified for the DS record is not supported by our systems
V311	Unsupported digest type '<nnn>' found.	The digest type specified for the DS record is not supported by our systems
V312	Bad digest '<xxxx>' found.	The digest specified does not match the expected format for the digest type specified
V313	Domain <xxxx>.uk is available as part of our release of reserved domains. Please send a separate request for this domain.	Applications for reserved domains must be made individually, no other domain name applications can be included in the same request.
V314	Bad value found for dsdata: '<xxxx>'.	This error occurs when invalid information or characters are provided in the DS Record details
V315	Request cannot specify "dsdata: NULL" and add new records	The request attempted to remove all DS records on the domain using "NULL" and also attempted to add DS records
V316	Duplicate DS record found in list	The request attempted to add the same DS record two or more times to a domain
V317	The target account for a reserved domain request must have a contact email address	The operation attempted to request a reserved domain on an existing account which does not have a contact email address
V318	You have not signed up for the DNSSEC Signing Service.
V327	Signature did not match the text (message contains tabs in trailing whitespace)	Similar to V048, but the validation code detected tabs within trailing whitespace for the message: view full description
V328	Registrant name does not meet minimum requirements as this field must contain at least 4 characters and of these 3 or more must be letters	The company or individual who the domain name is to be registered on behalf of must contain at least 4 or more characters and of these 3 or more must be letters.

Related contacts

For questions from our members and registrars Telephone: 01865 332233 Email: support@nominet.org.uk To make a payment Telephone: 01865 332348 Email: payments@nominet.org.uk Emergency out of hours support for registrars Telephone: 01606 866663

If you need any more advice, request a call back and discuss your query with one of our advisors. Request call back ›