Error messages
If there is problem with a command or an operation submitted to EPP or the Web Domain Manager, you will receive one of these types of error message:
- Fatal error
A fatal error means that the command you submitted was not successful and changes were not made to the registry. Fatal errors are identified by the letter “V” followed by three numbers; for example: V028. Fatal errors can often be addressed by making a minor change to your request. Fatal errors are listed below.
- Non-fatal error
Non-fatal errors are warning messages 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 other commands or operations.
Fatal errors
| Error Code | EPP Response Code | Issue | Description |
|---|---|---|---|
| V001 | 2002 | Subject Line contains unknown action | Each message’s subject line is checked 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 | 2104 | 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) 330 236 9480 for further information. |
| V007 | 2001 | Unknown field ‘<xxx>’ | A template is given for each request in the documentation for the operation type. Any fields given which do not appear in the template will not be recognised and request processing will be abandoned. |
| V008 | 2003 | 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 | 2306 | 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.’. |
| V012 | 2005 | 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 | 2201 | The registrant’s name 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 | 2104 | 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) 330 236 9480 for further information. |
| V015 | 2104 | 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) 330 236 9480 for further information. |
| V016 | 2306 | 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. |
| V020 | 2003 | Missing or invalid account identifier | Operations relating to a specific registrant contact must include the account-id number. |
| V023 | 2005 | Error Reading Nameserver <xxx> | This error occurs when invalid information or characters are provided in the name server details. |
| V024 | 2003 | 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 | 2005 | 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 | 2005 | 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 | 2005 | 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 | 2005 | Invalid postcode: <xxx> | Postcodes are validated to verify that they are formatted correctly. A postcode consists of two parts, separated by a single space, examples below:Format Example Postcode AN NAA M1 1AA ANN NAA M60 1NW AAN NAA CR2 6XH AANN NAA DN55 1PT ANA NAA W1A 1HQ AANA NAA EC1A 1BB |
| V030 | 2005 | <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. |
| V031 | 2306 | Address has too many lines (%d is maximum) | |
| V033 | 2500 | DATABASE ERROR | |
| V036 | 2306 | Too many nameservers specified (10 is maximum) | You can only provide a maximum of 10 name servers for a registration. |
| V040 | 2005 | 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. |
| V053 | 2306 | Duplicate Nameserver found in list | Duplicate name servers cannot be provided for the same registration. |
| V056 | 2002 | Multiple Key Fields found | |
| V057 | 2005 | 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 | 2004 | 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 | 2001 | Message contained no requests | Occurs if no fields are present in a request after any invalid text has been removed. |
| V061 | 2005 | 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 | 2001 | 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 | 2003 | 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 | 2003 | 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 | 2003 | ‘<xxx>’ field missing or empty | No data has been provided for a mandatory field in a registration request. |
| V071 | 2003 | Missing admin contact | No data has been provided for the mandatory primary administrative contact in a registration request |
| V073 | 2005 | 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 | 2003 | 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. |
| V077 | 2003 | 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 | 2003 | 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 | 2005 | 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 | 2201 | 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 | 2306 | 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 | 2306 | 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. |
| V086 | 2005 | 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. |
| V087 | 2001 | Contacts cannot be removed and edited at the same time | |
| V088 | 2104 | 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 Payments line on +44 (0) 330 236 9476 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. |
| V094 | 2302 | Domain name exists already | This error occurs if you attempt to register a domain that is already registered. |
| V096 | 2201 | 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 | 2304 | Domain names cannot be detagged in the first month of registration. If you wish to cancel this domain name please refer to Automaton operations – Delete operation | |
| V102 | 2304 | Domain names can only be deleted before the initial registration invoice is generated. Only the registrant can now cancel the domain name. | Domain names can only be cancelled in the first registration period. |
| V105 | 2304 | Current and registering tag different. | Domain names cannot be cancelled if there has been a registrar change. |
| V107 | 0 | Tag missing from subject line | |
| V108 | 0 | Tag in subject line does not match PGP signatory. | |
| V109 | 0 | Invalid bulk operation | |
| V110 | 2005 | Field ‘<xxx>’ cannot be modified using a bulk modification query. | |
| V111 | 2304 | Domain name is subject of tag change | |
| V113 | 0 | Old nserver must be non-blank for bulk n-server replacement. | |
| V114 | 0 | Nserver replacements and update bulk requests are not-compatible | |
| V116 | 0 | Field <xxx> appears more than once in update clause for bulk request. | |
| V117 | 0 | Field <xxx> empty | |
| V120 | 2306 | Invalid date <xxx> | |
| V121 | 2306 | Invalid tag field | |
| V122 | 2306 | You cannot filter by tag | |
| V123 | 2201 | You have exceeded usage limits for registration attempts on existing domain names. You will be blocked for 24 hours. | |
| V124 | 2201 | 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 | 2306 | Domain names may not begin xn-- | |
| V128 | 2105 | Domain name is not within its renewal period or cannot be renewed | |
| V129 | 2105 | 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’. |
| V133 | 2003 | <xxxx> address must have city field present | The <xxxx> will be replaced with the country code in the address. E.g. UK, JE etc. “ |
| V134 | 2004 | 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 | 2306 | Domain name contravenes naming rules | See Nominet’s registration rules. |
| V140 | 2304 | ‘<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 | 2303 | Account <xxx> does not exist | |
| V142 | 2201 | Account <xxx> is not on your tag | |
| V143 | 2303 | Nameserver <xxx> does not exist | |
| V144 | 2201 | Nameserver <xxx> is not on your tag | |
| V145 | 2304 | <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. |
| V147 | 2201 | Contact <xxx> is not on your tag | |
| V148 | 2001 | Both in-line and ? objects present. | |
| V149 | 2005 | Bad IPV6 address for server <xxx> : <xxx> | |
| V150 | 2005 | Domain name labels must not be longer than 63 characters | |
| V154 | 0 | Invalid registrant identifier <xxx> | |
| V156 | 2105 | Domain name has already been renewed. | |
| V157 | 2306 | Auto-bill and next-bill cannot both be set. | |
| V158 | 2001 | 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 | 0 | Signature has a timestamp more than 3 days in the past | The current time is compared 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 | 2306 | More than one ipv<xxx> address given for name-server | |
| V167 | 2306 | Message id %s has not been sent to you | |
| V169 | 2003 | Missing ‘operation’ field | |
| V171 | 2005 | Name server is more than 255 characters | |
| V172 | 2005 | Name server <xxx> is invalid – label has invalid length | |
| V173 | 2005 | Name server <xxx> is invalid | |
| V174 | 2105 | 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 | 2201 | You have exceeded cancellation usage limits | |
| V178 | 2304 | next-bill or auto-bill cannot be set when recur-bill is ‘bc’ | |
| V180 | 2001 | 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 | 2201 | 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 | 2306 | Attempt to ‘like’ a numeric field. | You have tried to do a bulk ‘like’ filter using account-id, auto-bill or next-bill. |
| V183 | 2306 | Reg type must be SCH for .sch.uk domain name | |
| V184 | 2003 | Missing identifier for contact modification | |
| V185 | 2003 | Missing identifier for account modification | |
| V186 | 2003 | Missing identifier for nameserver modification | |
| V187 | 2308 | Unable to have no main billing contact when there are other billing contacts | |
| V188 | 2201 | You cannot transfer to the account <xxx> | The domain names on the account are not on your tag. |
| V189 | 2201 | Account names do not match for the following domain names: | |
| V190 | 2001 | Invalid operation <xxx>: <xxx> | |
| V191 | 2005 | Invalid ID prefix ‘<xxx>’, expecting ‘<xxx>’ | An invalid contact, nameserver or account identifier has been provided. |
| V192 | 2303 | Reference %s made to non-existant contact | |
| V193 | 2001 | Contact has both data and external reference %s | |
| V194 | 2304 | 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 – The domain is scheduled for cancellation. Please visit our registrar renewals procedure for further information. Following this if you have any queries please contact our customer services team on +44(0) 330 236 9480 or by email to [email protected]. |
| V195 | 2304 | 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. |
| V197 | 2201 | Tag <xxx> do not accept registrar changes | |
| V198 | 2201 | Account <xxx> is not on tag <xxx> | |
| V199 | 0 | A target account may not be provided for an account release | |
| V200 | 2201 | Contact <xxx> is not on account <xxx>. | |
| V201 | 2001 | Too many lines in request: Maximum is 500 | |
| V202 | 2308 | Cannot have multiple admin contacts with id %s. | |
| V203 | 2308 | Cannot have multiple billing contacts with id %s. | |
| V204 | 2001 | Cannot change registrar-tag with modify operation; use release operation instead. | |
| V205 | 2001 | Too many <xxx> numbers in request: Maximum is 10 | |
| V206 | 2005 | Invalid ID suffix <xxx>, expecting ‘-UK’. | |
| V207 | 2304 | The following domains do not have account names that match that of the account specified:<xxx> | |
| V208 | 2201 | The following domain names are not registered to your tag: <xxx> | |
| V209 | 2201 | The set of domain names given could not be modified. | |
| V210 | 2005 | Period format is invalid | |
| V211 | 2005 | Period is outside acceptable range | |
| V212 | 2201 | You are too close to your abuse limit to complete this operation | |
| V213 | 0 | Length of %s must not exceed %s. | |
| V216 | 2003 | Missing nameserver name or ip address. | |
| V217 | 0 | DNS data out of sequence. | |
| V218 | 2304 | The following domains are not on the account specified:%s | |
| V219 | 2304 | The following accounts do not have account names that match that of the account specified:%s | |
| V220 | 2201 | The following accounts are not registered to your tag: %s | |
| V221 | 2001 | Cannot use different versions of XML schema ‘%s’ | |
| V223 | 2304 | Domains are not all on the same account. | |
| V224 | 2500 | %s | |
| V225 | 2201 | Registrar is not a member. | |
| V226 | 2304 | First bill cannot be ‘bc’ for non 2 year registrations. | |
| V227 | 2004 | 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 | 2304 | ‘<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. |
| V229 | 0 | Cannot combine ‘month’, ‘expiry’ and ‘validated’ fields. | |
| V230 | 2306 | Enumber range invalid | The lastE164Number provided is smaller than the E164Number. |
| V231 | 2306 | <xxx> format invalid | A date specified has not been provided in RFC 3339 format. |
| V232 | 2306 | Execution date is in the future | The execution date on the ENUM token is in the future. |
| V233 | 2306 | 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 | 2201 | 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 | 2306 | <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 | 2201 | 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 | 2304 | Enumber has already been renewed. | Occurs if a renew operation would not increase the expiry date by at least one day. |
| V238 | 2304 | 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 | 2302 | Part or all of Enumber range exists. | Occurs if a create command fails due to it overlapping with an existing registration. |
| V241 | 2306 | 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. |
| V242 | 0 | Nameserver objects could not be merged. | |
| V243 | 2304 | <xxx> requires referral for manual intervention. Please send a separate request for this domain. | This message indicates that a request has been made to create more than one domain and at least one of these is a domain requiring manual referral (ltd.uk, plc.uk or net.uk). Any request to register a domain which requires manual referral must only contain a single domain name. |
| V244 | 2304 | ‘test dummy’ domain names may not appear in requests with multiple keys. | This message will occur if a request has been received to create or transfer “test” domains and the request contains more than one domain name. A “test” domain is one whose name matches the pattern “automaton-test-[any characters].[sld].uk” and is used for testing purposes only. |
| V245 | 2302 | Domain name %s exists already. | |
| V246 | 2306 | Only 100 multiple registrations are permitted in a single request | |
| V247 | 2306 | Only %s multiple tag changes are permitted in a single request | |
| V260 | 2005 | Invalid value ‘%s: %s’. | |
| V261 | 0 | PGP signature expired. | |
| V262 | 2005 | Bad renew-not-required field. | |
| V263 | 2005 | Renew-not-required field can only be unset by renewal of the domain. | |
| V264 | 2306 | Only 100 renewal reversals are permitted in a single request. | |
| V265 | 2304 | The following domain names do not have a renewal request being processed: | |
| V266 | 2201 | The account-id %ld does not correspond to a valid registrant account. | |
| V267 | 2304 | A destination account-id may not be specified for this case. | |
| V268 | 2304 | The destination account name does not match that of the domains associated with case %ld. | |
| V269 | 2004 | This request will have no effect. | |
| V270 | 2304 | Domain name already unrenewed in this registration period. | |
| V271 | 2304 | Auto-bill/next-bill cannot be set when renew_not_required is set | |
| V272 | 2304 | Company number and registrant type cannot be modified for registrar accounts.. | |
| V273 | 2304 | Renewals cannot be undone when auto.next billing fields are set. | |
| V274 | 2001 | Schema %s not specified at login | |
| V275 | 2002 | Domain is not locked | |
| V276 | 2201 | Account is locked. | |
| V277 | 2001 | Account id and domain name cannot both be specified | |
| V278 | 2002 | Account is not locked. | |
| V279 | 2302 | Account % exists already. | |
| V280 | 2302 | A contact of order % already exists. | |
| V281 | 2302 | Registration of domain %s has been blocked | |
| V282 | 2001 | Invalid or missing lock type. | Generated if you specify a incorrect ‘lock-type’ for a operation |
| V283 | 2306 | Cannot add IPVs address to nameserver; nameservers should only have a maximum of one IPV4 and one IPV6 address. | |
| V284 | 2302 | Account exists already. | |
| V285 | 2302 | Contact-id %s exists already | |
| V286 | 2302 | Nameserver already exists on your tag. | |
| V287 | 2303 | Superordinate domain is not on your tag. | |
| V288 | 2306 | Cannot link nameserver to superordinate domain, domain has no free nameserver slots (%d is maximum). | |
| V289 | 2302 | Nameserver already exists | A host with that name already exists therefore cannot be created with that name/ |
| V290 | 2304 | 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 | 2306 | 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 | 2303 | Domain <xxxx> does not exist | The domain name specified does not exist in our registry. |
| V293 | 2303 | Name server ‘<xxxx>’ is invalid – parent domain does not exist | This error occurs when the parent domain used for a host name should occur in our registry but does not. |
| V294 | 2306 | 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. |
| V295 | 2500 | The request was successful but there was an internal error while generating the reply | |
| V296 | 2500 | The request was unsuccessful but there was an internal error while generating the reply | |
| V297 | 2201 | 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 |
| V298 | 2201 | Domain check limit of %ld has been reached | |
| V299 | 2201 | You have exceeded usage limits for operations which fail due to the non-existence of superordinate domains. You will be blocked for 24 hours. | |
| V300 | 2003 | 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 | 2005 | Reseller references may only contain upper case letters A-Z, digits 0-9 and hyphens | |
| V302 | 2302 | 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 | 2005 | A well-formed email address must be provided | |
| V304 | 2306 | Too many domains specified(<xxxx> is maximum) | No more than 100 domain names can be supplied in a Check command |
| V305 | 2201 | 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 | 2306 | Too many dsData records specified (8 is maximum) | You can only provide a maximum of 8 DS records for a domain. |
| V307 | 2102 | Unsupported secDNS attribute ‘urgent’ found. | We do not support the “urgent” attribute from RFC-5910 |
| V308 | 2102 | Unsupported secDNS element ‘maxSigLife’ found. | We do not support the “maxSigLife” element from RFC-5910 |
| V309 | 2306 | Unsupported secDNS interface ‘keyData’ found. | We do not support the “keyData” interface described in RFC-5910 |
| V310 | 2004 | Unsupported algorithm ‘<nnn>’ found. | The algorithm specified for the DS record is not supported by our systems |
| V311 | 2004 | Unsupported digest type ‘<nnn>’ found. | The digest type specified for the DS record is not supported by our systems |
| V312 | 2004 | Bad digest ‘<xxxx>’ found. | The digest specified does not match the expected format for the digest type specified |
| V313 | 2304 | 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 | 2005 | Bad value found for dsdata: ‘<xxxx>’. | This error occurs when invalid information or characters are provided in the DS Record details |
| V315 | 2004 | 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 | 2306 | Duplicate DS record found in list | The request attempted to add the same DS record two or more times to a domain |
| V317 | 2304 | 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 | 2005 | You have not signed up for the DNSSEC Signing Service. | Obsolete |
| V319 | 2306 | Too many %s records specified (%s is maximum) | |
| V320 | 2302 | Zone ‘%s’ already exists on your tag | |
| V321 | 2201 | Zone ‘%s’ is not on your tag | |
| V322 | 2005 | Duplicate IP address ‘%s’ found for server | |
| V323 | 2306 | The ‘%s’ operation cannot be used for zone ‘%s’ | |
| V324 | 2306 | Cannot add DS records to parent for zone %s until zone is signed | |
| V325 | 2005 | Unsupported value ‘%s’ found for field ‘%s’ | |
| V327 | 0 | 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 | 2005 | 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. |
| V329 | 2304 | Cannot undo multiple renewals for domain ‘%s’ | |
| V330 | 2305 | Host ‘%s’ cannot be deleted as it is linked to one or more domains | Before deleting a host you must first modify all domains using the host so that they use other hosts |
| V331 | 2201 | You do not have permission to delete the host ‘%s’ | If the parent domain for a host is registered with Nominet the host can only be deleted by the owner of the parent domain |
| V332 | 2305 | Contact ‘%s’ cannot be deleted as it is linked to one or more domains | Before deleting a contact you must first transfer all domains on that contact to another contact |
| V333 | 2201 | You do not have permission to delete the contact ‘%s’ | You may only delete a contact which you created and which has never been linked to any domains |
| V334 | 2201 | Your request for domain <xxxx> has failed because the <xxxx> for the registrant does not fully match any registrant which has rights for this domain | |
| V335 | 2304 | Your request includes the domain <xxxx>. | Please send a separate request for this domain. |
| V341 | 2306 | Too many domains specified for check with second level rights (1 is maximum) | |
| V342 | 2201 | Your request for domain ‘%s’ has failed because this domain has been reserved by Nominet | |
| V343 | 2005 | All email addresses must have a valid TLD | |
| V348 | 2306 | Contact address cannot be changed to a PO Box because it is the registrant of a second level domain | |
| V349 | 2306 | Contact address cannot be changed to a PO Box because it is the service address of a domain | |
| V350 | 2201 | The operation would exceed the number of domains allowed on a self managed tag | |
| V351 | 2201 | Contact <xxxxxxx> cannot be locked as it has good quality data | Generated if you attempt to lock a domain name that has been validated. |
| V352 | 2201 | Domain registrant cannot be locked as it has good quality data | Generated when lock specified using a domain name |
| V353 | 2201 | Must be an Accredited Channel Partner tag to perform this operation | |
| V354 | 2306 | Your request for domain ‘%s’ has failed because the registrant with second level rights has no email address | |
| V355 | 2305 | Operation blocked due to restrictions applied to the third level domain name with rights | |
| V356 | 2306 | Phone number must start with a ‘+’ followed by the country code | Generated when a phone number is provided during account modification or creation that does not comply with Data Quality policy. Format must be +44.3302369475 |
| V357 | 2306 | First line of address must contain at least 1 non-numeric character | Generated when street1 is provided during account modification or creation that does not comply with Data Quality policy. |
| V358 | 2306 | Contact with type <xxxx> cannot have trading name | Generated when type id set IND or FIND and a trading name is present during account modification or creation. |
| V359 | 2002 | Your request to modify domain ‘%s’ failed because it was modified by another session | |
| V360 | 2102 | Unsupported domain element ‘hostAttr’ found | |
| V361 | 2306 | Contact cannot be validated while modifying other fields | |
| V362 | 2005 | The validated field may only contain ‘Y’ or ‘N’ | |
| V363 | 2304 | Operation blocked by Nominet process | This request cannot be made due to a Nominet process. This can occur for a number of reasons. If you have questions about this, please contact our Compliance team by telephone on +44 (0) 330 236 9480 or by email to [email protected]. |
| V367 | 2304 | Operation blocked due to restrictions applied to domains with suffix ‘%s’ | |
| V368 | 2304 | Operation blocked due to restrictions applied to one of the contact’s domains | |
| V369 | 2400 | Transient data error | |
| V370 | 2306 | No Privacy Service | |
| V371 | 2308 | Domain Status Associated with Domain | Status is already associated with domain |
| V372 | 2308 | Domain Status Value Not Associated | Status is not associated with domain |
| V373 | 2304 | Status Prohibits Operation | Object status prohibits operation You will need to remove ‘clientUpdateProhibited’ before you can remove any other EPP statuses. |
| V374 | 2308 | Contact Status Value Already Associated | Status is already associated with contact |
| V375 | 2308 | Contact Status Value Not Associated | Status is not associated with contact |
| V376 | 2101 | Value Not Implemented | Status ‘%s’ is not implemented |
| V377 | 2308 | Host Status Value Already Associated | Status is already associated with host |
| V378 | 2308 | Host Status Value Not Associated | Status is not associated with host |
| V379 | 2302 | DS Record Already Exists | |
| V380 | 2304 | Domain is already released |
Minerva House, Edmund Halley Road, Oxford Science Park, OX4 4DQ, United Kingdom