PDF version

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 you submitted was not successful and changes were not made to the registry. 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
V001Subject Line contains unknown actionThe 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.
V002Nominet 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.
V007Unknown 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.
V008No Domain name givenThis 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. 
V009Domain <xxx> cannot be requested via this automatonOur 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.'.
V010Domains with two letters are not allowedThird 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.
V011Domains with one character are not allowedThird 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.
V012Fully-qualified domain names must be no longer than <xxx> charactersThe 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.
V013The registrant's name cannot be modifiedChanges 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.
V014The 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.
V015The 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.
V016The tag '<xxx>' is unrecognisedThis error occurs when an invalid tag is used in the 'registrar-tag' field, often due to the tag not being provided in capital letters.
V017bad 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).
V018bad 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).
V019Missing account nameThe '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.
V020Missing or invalid account identifierOperations relating to a specific registrant contact must include the account-id number.
V023Error Reading Nameserver <xxx>This error occurs when invalid information or characters are provided in the name server details.
V024Missing 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.
V025Bad 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.
V027Bad 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.
V028Invalid 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
V029Invalid 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<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.
V031Address has too many lines (%d is maximum) 
V033DATABASE ERROR 
V036Too many nameservers specified (10 is maximum)You can only provide a maximum of 10 name servers for a registration.
V040Bad 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.
V042Invalid month '%s' in list action 
V044Unrecognised PGP formatThe 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
V045Error occurred during PGP decodeThis 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.
V046Message not in Clear Text Signed FormatThis error occurs when the message received by the Automaton has either been encrypted or has not been PGP signed.
V047Signing Key not recognisedThis 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).
V048Signature did not match the text
  1. The request has been altered after PGP signing. No matter how minor, any change to the message will cause the PGP verification to fail.
  2. Your email client has applied formatting to the request and therefore corrupted the signature. Please make sure that the sending format is set to Plain Text and uuencode/US ASCII and not HTML or MIME. Also, you should either disable line wrapping or ensure that any text line does not exceed your email client’s line wrapping threshold.
  3. There should only be one or no spaces after the colon of each field.
  4. Additional spaces at the end of any lines should be removed.
  5. Tab characters and other formatting should not be used as this may corrupt the PGP signature. It is often worthwhile copying a new version of the automaton template from our web site to eliminate any possible corruption.
  6. As of GPG V1.4.8 the --force-v3-sigs option is no longer enabled by default.  Adding the --force-v3-sigs option should produce a signature compatible with the Automaton.
V049Key has been revokedThe 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.
V050Key has been disabledThe 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.
V051Key has expiredThe 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.
V052Signature has a timestamp in the futureThe 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.
V053Duplicate Nameserver found in listDuplicate name servers cannot be provided for the same registration.
V055You 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.
V056Multiple Key Fields found 
V057Invalid field '<xxx>' for <xxx> operationOccurs 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.
V058This Request will have no effectThe 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.
V060Message contained no requestsOccurs if no fields are present in a request after any invalid text has been removed.
V061Nameserver '<xxx>' appears to be an IP addressAn 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.
V063Multiple Instances of Field '<xxx>' foundThis error will occur if a field, other than 'addr' or 'notes', is used more than once in a single request.
V064ISO 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.
V065postcode required for GB, GG, JE and IM Country codes for <xxx> addressThe 'postcode' fields are mandatory if the country codes GB, GG, JE or IM are used in the 'country' field. 
V069'<xxx>' field missing or emptyNo data has been provided for a mandatory field in a registration request.
V070Missing admin addressNo data has been provided for the mandatory 'addr' address field in a registration request.
V071Missing admin contactNo data has been provided for the mandatory primary administrative contact in a registration request
V073Invalid Company NumberFor 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.
V074Company Number required for UK Limited and Public Limited CompaniesFor 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.
V076Only 100 requests permitted in a single emailA 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.
V077Company Number required for LLP reg-typesFor 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.
V078School 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.
V079Company Number not required for <xxx> reg-typesNo information should be provided in the 'co-no' field unless the registrant type listed in the 'type' field is LTD, PLC, LLP, SCH, RCHAR.
V080The 'co-no' field cannot be modified for an sch.uk domain namePlease contact our support department to inform us of any update to a school's DfES number.
V081Reg type must be LTD for .ltd.uk domain nameThe registrant type 'LTD' must be set in the 'type' field when making a ltd.uk domain registration.
V082Reg type must be PLC for .plc.uk domain nameThe registrant type 'PLC' must be set in the 'type' field when making a plc.uk domain registration.
V083Invalid 'opt-out' fieldThe 'opt-out' field can only be set to either 'y' or 'n' ('NULL' to clear).
V084No 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.
V085Only 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.
V086Contents of field <xxx> cannot be removedThis occurs if an attempt is made to remove the contents of a field that is either mandatory or required by other existing fields.
V087Contacts cannot be removed and edited at the same time 
V088You 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)1865 3322348 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.
V089Incorrect PGP constructsThe 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.
V094Domain name exists alreadyThis error occurs if you attempt to register a domain that is already registered. 
V096Domain name is not registered to your tagThis error will occur if you attempt to make changes to a domain that is either not on your tag or not registered.
V101Domain 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 
V102Domain 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.
V103Domain name is in legal dispute 
V105Current and registering tag different.Domain names cannot be cancelled if there has been a registrar change.
V107Tag missing from subject line 
V108Tag in subject line does not match PGP signatory. 
V109Invalid bulk operation  
V110Field '<xxx>' cannot be modified using a bulk modification query. 
V111Domain name is subject of tag change 
V113Old nserver must be non-blank for bulk n-server replacement. 
V114Nserver replacements and update bulk requests are not-compatible 
V115Glue record required for name server %s 
V116Field <xxx> appears more than once in update clause for bulk request. 
V117Field <xxx> empty 
V120Invalid date <xxx> 
V121Invalid tag field 
V122You cannot filter by tag   
V123You have exceeded usage limits for registration attempts on existing domain names. You will be blocked for 24 hours. 
V124You 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.
V127Domain names may not begin xn-- 
V128Domain name is not within its renewal period or cannot be renewed 
V129Domain 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<xxxx> address must have city field presentThe <xxxx> will be replaced with the country code in the address. E.g. UK, JE etc. "
V134Bad 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.
V138Domain name contravenes naming rules 
V140'<xxx>' field may not currently be changedThis 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.
V141Account <xxx> does not exist 
V142Account <xxx> is not on your tag 
V143Nameserver <xxx> does not exist 
V144Nameserver <xxx> is not on your tag  
V145<xxx> may not be set retrospectivelyThis 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.
V146Contact <xxx> does not exist 
V147Contact <xxx> is not on your tag 
V148Both in-line and ? objects present. 
V149Bad IPV6 address for server <xxx> : <xxx> 
V150Domain name labels must not be longer than 63 characters 
V154Invalid registrant identifier <xxx> 
V156Domain name has already been renewed. 
V157Auto-bill and next-bill cannot both be set. 
V158operation: field does not match subjectThis 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.
V159Signature has a timestamp more than 3 days in the pastThe 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.
V166More than one ipv<xxx> address given for name-server 
V167Message id %s has not been sent to you 
V169Missing 'operation' field 
V171Name server is more than 255 characters 
V172Name server <xxx> is invalid - label has invalid length 
V173Name server <xxx> is invalid 
V174Domain name has already been renewed once in the last 24 hoursThis 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.
V175You have exceeded cancellation usage limits 
V177Field '%s' is no longer allowable 
V178next-bill or auto-bill cannot be set when recur-bill is 'bc' 
V180You must accept or reject the registrar change authorisation requestThis 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.
V181You 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.
V182Attempt to 'like' a numeric field.You have tried to do a bulk 'like' filter using account-id, auto-bill or next-bill.
V183Reg type must be SCH for .sch.uk domain name 
V184Missing identifier for contact modification 
V185Missing identifier for account modification 
V186Missing identifier for nameserver modification 
V187Unable to have no main billing contact when there are other billing contacts 
V188You cannot transfer to the account <xxx>The domain names on the account are not on your tag.
V189Account names do not match for the following domain names: 
V190Invalid operation <xxx>: <xxx> 
V191Invalid ID prefix '<xxx>', expecting '<xxx>'An invalid contact, nameserver or account identifier has been provided.
V192Reference %s made to non-existant contact 
V193Contact has both data and external reference %s 
V194Operation blocked by Nominet processThis 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 Customer Services Team by telephone on 01865 332233 or by email to support@nominet.org.uk.
V195The 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.
V196Invalid registrar change case <xxx> 
V197Tag <xxx> do not accept registrar changes 
V198Account <xxx> is not on tag <xxx> 
V199A target account may not be provided for an account release 
V200Contact <xxx> is not on account <xxx>. 
V201Too many lines in request: Maximum is 500 
V202Cannot have multiple admin contacts with id %s. 
V203Cannot have multiple billing contacts with id %s. 
V204Cannot change registrar-tag with modify operation; use release operation instead. 
V205Too many <xxx> numbers in request: Maximum is 10 
V206Invalid ID suffix <xxx>, expecting '-UK'. 
V207The following domains do not have account names that match that of the account specified:<xxx> 
V208The following domain names are not registered to your tag: <xxx> 
V209The set of domain names given could not be modified. 
V210Period format is invalid 
V211Period is outside acceptable range 
V212You are too close to your abuse limit to complete this operation 
V213Length of %s must not exceed %s. 
V216Missing nameserver name or ip address. 
V217DNS data out of sequence. 
V218The following domains are not on the account specified:%s 
V219The following accounts do not have account names that match that of the account specified:%s 
V220The following accounts are not registered to your tag: %s 
V221Cannot use different versions of XML schema '%s' 
V222Cannot use XML schema '%s' version %s with schema '%s' version %s 
V223Domains are not all on the same account. 
V224%s 
V225Registrar is not a member. 
V226First bill cannot be 'bc' for non 2 year registrations. 
V227Bad '<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.
V229Cannot combine 'month', 'expiry' and 'validated' fields. 
V230Enumber range invalidThe lastE164Number provided is smaller than the E164Number.
V231<xxx> format invalidA date specified has not been provided in RFC 3339 format.
V232Execution date is in the futureThe execution date on the ENUM token is in the future.
V233Expiration date is in the pastThe expiration date on the ENUM token provided is in the past, it is advisable that you contact your validation agency to resolve this.
V234RegistrarID 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> invalidInvalid number provided for E164Number or LastE164Number, for example if the number is too long or starts with a non-UK prefix.
V236Enumber 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.
V237Enumber has already been renewed.Occurs if a renew operation would not increase the expiry date by at least one day.
V238Token is older than the current oneThis is returned when the ENUM token provided has an older execution date than the current one stored.
V239Part or all of Enumber range exists.Occurs if a create command fails due to it overlapping with an existing registration.
V241Token expires before registrationOccurs 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.
V242Nameserver objects could not be merged. 
V243<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'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.
V245Domain name %s exists already. 
V246Only 100 multiple registrations are permitted in a single request 
V247Only %s multiple tag changes are permitted in a single request 
V260Invalid value '%s: %s'. 
V261PGP signature expired. 
V262Bad renew-not-required field. 
V263Renew-not-required field can only be unset by renewal of the domain. 
V264Only 100 renewal reversals are permitted in a single request. 
V265The following domain names do not have a renewal request being processed: 
V266The account-id %ld does not correspond to a valid registrant account. 
V267A destination account-id may not be specified for this case. 
V268The destination account name does not match that of the domains associated with case %ld. 
V269This request will have no effect. 
V270Domain name already unrenewed in this registration period. 
V271Auto-bill/next-bill cannot be set when renew_not_required is set 
V272Company number and registrant type cannot be modified for registrar accounts.. 
V273Renewals cannot be undone when auto.next billing fields are set. 
V274Schema %s not specified at login 
V275Domain is not locked 
V276Account is locked. 
V277Account id and domain name cannot both be specified 
V278Account is not locked. 
V279Account % exists already. 
V280A contact of order % already exists. 
V281Registration of domain %s has been blocked 
V282Invalid or missing lock type.Generated if you specify a incorrect ‘lock-type’ for a operation
V283Cannot add IPVs address to nameserver; nameservers should only have a maximum of one IPV4 and one IPV6 address. 
V284Account exists already. 
V285Contact-id %s exists already 
V286Nameserver already exists on your tag. 
V287Superordinate domain is not on your tag. 
V288Cannot link nameserver to superordinate domain, domain has no free nameserver slots (%d is maximum). 
V289Nameserver already existsA host with that name already exists therefore cannot be created with that name/
V290Too many domains for full-detail domain list operationFor 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.
V291Glue 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.
V292Domain <xxxx> does not existThe domain name specified does not exist in our registry.
V293Name server '<xxxx>' is invalid - parent domain does not existThis error occurs when the parent domain used for a host name should occur in our registry but does not.
V294You 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.
V295The request was successful but there was an internal error while generating the reply 
V296The request was unsuccessful but there was an internal error while generating the reply 
V297Reseller '<xxxx>' is not on your tagTo 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
V298Domain check limit of %ld has been reached 
V299You have exceeded usage limits for operations which fail due to the non-existence of superordinate domains. You will be blocked for 24 hours. 
V300An email address or a telephone number must be providedThis error occurs if you have attempted to create or modify a reseller without setting either an email address or a telephone number.
V301Reseller references may only contain upper case letters A-Z, digits 0-9 and hyphens 
V302Reseller 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.
V303A well-formed email address must be provided 
V304Too many domains specified(<xxxx> is maximum)No more than 100 domain names can be supplied in a Check command
V305Your 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
V306Too many dsData records specified (8 is maximum)You can only provide a maximum of 8 DS records for a domain.
V307Unsupported secDNS attribute 'urgent' found.We do not support the "urgent" attribute from RFC-5910
V308Unsupported secDNS element 'maxSigLife' found.We do not support the "maxSigLife" element from RFC-5910
V309Unsupported secDNS interface 'keyData' found.We do not support the "keyData" interface described in RFC-5910
V310Unsupported algorithm '<nnn>' found.The algorithm specified for the DS record is not supported by our systems
V311Unsupported digest type '<nnn>' found.The digest type specified for the DS record is not supported by our systems
V312Bad digest '<xxxx>' found.The digest specified does not match the expected format for the digest type specified
V313Domain <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.
V314Bad value found for dsdata: '<xxxx>'.This error occurs when invalid information or characters are provided in the DS Record details
V315Request cannot specify "dsdata: NULL" and add new recordsThe request attempted to remove all DS records on the domain using "NULL" and also attempted to add DS records
V316Duplicate DS record found in listThe request attempted to add the same DS record two or more times to a domain
V317The target account for a reserved domain request must have a contact email addressThe operation attempted to request a reserved domain on an existing account which does not have a contact email address
V318You have not signed up for the DNSSEC Signing Service. 
V319Too many %s records specified (%s is maximum) 
V320Zone '%s' already exists on your tag 
V321Zone '%s' is not on your tag 
V322Duplicate IP address '%s' found for server 
V323The '%s' operation cannot be used for zone '%s' 
V324Cannot add DS records to parent for zone %s until zone is signed 
V325Unsupported value '%s' found for field '%s' 
V326You have not signed up for the DNSSEC Signing Service. 
V327Signature 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
V328Registrant name does not meet minimum requirements as this field must contain at least 4 characters and of these 3 or more must be lettersThe 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.
V329Cannot undo multiple renewals for domain '%s' 
V330Host '%s' cannot be deleted as it is linked to one or more domainsBefore deleting a host you must first modify all domains using the host so that they use other hosts
V331You 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
V332Contact '%s' cannot be deleted as it is linked to one or more domainsBefore deleting a contact you must first transfer all domains on that contact to another contact
V333You 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
V334Your request for domain <xxxx> has failed because the <xxxx> for the registrant does not fully match any registrant which has rights for this domain 
V335Your request includes the domain <xxxx>.Please send a separate request for this domain.
V336The address for service for a domain must have a country code of GB, GG, JE or IM 
V337Either the registrant or the address for service for domain <xxxx> must have a country code of GB, GG, JE or IM 
V338Too many <xxxx> contacts specified (<xxxx> is maximum) will occur if an attempt is made to add 2 admin contacts to a domain (max=1) 
V339Contact <xxxx> cannot be used as the registrant for a domain 
V340Contact <xxxx> cannot be used as the service address for a domainWhere <xxxx> is either the registrant ID or the EPP ID for the contact
V341Too many domains specified for check with second level rights (1 is maximum) 
V342Your request for domain '%s' has failed because this domain has been reserved by Nominet 
V343All email addresses must have a valid TLD 
V344A service address cannot be opted out 
V345Contact <xxxx> cannot be used as the service address for a domain because it has been set to opt-out 
V346Contact cannot be used as the registrant for a second level domain because it is registered to a PO Box 
V347Contact cannot be used as the service address for a second level domain because it is registered to a PO Box 
V348Contact address cannot be changed to a PO Box because it is the registrant of a second level domain 
V349Contact address cannot be changed to a PO Box because it is the service address of a domain 
V350The operation would exceed the number of domains allowed on a self managed tag 
V351Contact <xxxxxxx> cannot be locked as it has good quality dataGenerated if you attempt to lock a domain name that has been validated.
V352Domain registrant cannot be locked as it has good quality dataGenerated when lock specified using a domain name
V353Must be an  Accredited Channel Partner tag to perform this operation 
V354Your request for domain '%s' has failed because the registrant with second level rights has no email address 
V355Operation blocked due to restrictions applied to the third level domain name with rights 
V356Phone number must start with a '+' followed by the country codeGenerated when a phone number is provided during account modification or creation that does not comply with Data Quality policy. Format must be +44.1865332211
V357First line of address must contain at least 1 non-numeric characterGenerated when street1 is provided during account modification or creation that does not comply with Data Quality policy.
V358Contact with type <xxxx> cannot have trading nameGenerated when type id set IND or FIND and a trading name is present during account modification or creation.
V359Your request to modify domain '%s' failed because it was modified by another session 
V360Unsupported domain element 'hostAttr' found 
V361Contact cannot be validated while modifying other fields 
V362The validated field may only contain 'Y' or 'N' 
V363Operation blocked by Nominet processThis 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 01865 332450 or by email to compliance@nominet.org.uk.
V367Operation blocked due to restrictions applied to domains with suffix '%s' 
V368Operation blocked due to restrictions applied to one of the contact's domains 
V369Transient data error 
V370Disclose fields cannot be set without a registrar privacy service