Editing CO.UK (section)

= TLD specific =

=== Contact Validation Process ===
Nominet validates registrant data at the point of registration, or when the data is changed. An update of the contact will automatically trigger a re-validation.
The verification process by Nominet is described [https://registrars.nominet.uk/uk-namespace/data-quality-policy/how-does-nominet-validate-data/ on their website]
<br><br>
==== What should be checked prior to creating a contact?====
Formal requirements of valid contact data:<br>
*Registrant name/organization, value has to contain a minimum of 4 characters with at least 3 letters<br>
*Street value must contain non-numerical characters<br>
*City, country and zip code must be given to be validated<br>
*Phone number has to be in the following form +Countrycode.Area code.Subscriber number<br>
<br>
==== Email address has to meet the following requirements: ====
*Must contain an @ character<br>
*At least one character in front of the @ character<br>
*Must end with a valid TLD<br>
*No space/blank at the beginning or end<br>

==== New Validation Workflow ====
If Nominet cannot validate the information, it has to be validated by the reseller. Hexonet creates a corresponding EVENT message in this case:
<br>
Object: "domain:<domainname>.uk"<br>
Event Class/Subclass: "DOMAIN_MODIFICATION MODIFICATION_PENDING"<br>
Event Data: "Please correct or update the data, or send proof of identity to contactdata-validation@1api.net<br>
Subject: [[domainname.uk|http://domainname.uk/]: Confirming validation and document accuracy] Allowed file types: [.pdf, .jpg, .jpeg], not larger than 5MB."<br>
<br>
The registrant may either correct or update the data provided; or send appropriate documentation to allow validation of the data provided.
An update of the contact will automatically trigger a re-validation.
<br>
The client has to send proof of identity. Please make sure that the right recipient and the subject fitting the format below will be used:<br>
<br>
Recipient: '''"contactdata-validation@1api.net"'''<br>
Subject: "<domainname>.uk: Confirming validation and document accuracy"<br>
Allowed file types for attachments are: [.pdf, .jpg, .jpeg], not larger than 5MB.<br>
<br>
==== Failed validations will trigger an event for each domain related to the contact ====
Object: "domain:<domainname>.uk"<br>
Event Class/Subclass: "DOMAIN_MODIFICATION MODIFICATION_PENDING"<br>
Event Data: "Validation failed, please correct or update the data, or send proof of identity to contactdata-validation@1api.net<br>
Subject: [[domainname.uk|http://domainname.uk/]: Confirming validation and document accuracy] Allowed file types: [.pdf, .jpg, .jpeg], not larger than 5MB."<br>
<br>
The registrant has to provide appropriate proof of identity, e.g. driving license, passport, national ID card (for non-UK citizens), national insurance card (for UK citizens), official company letterhead, company stamp.
<br>
The email will be processed by Hexonet and the contact will be validated automatically. Successful validations will trigger an event for each domain related to the contact:<br>
<br>
Object: "domain:<domainname>.uk"<br>
Event Class/Subclass: "DOMAIN_MODIFICATION MODIFICATION_SUCCESSFUL"<br>
Event Data: "registrant contact validation successful"<br>
<br>

==== Domain suspension after validation failed: ====

If neither the contact is updated nor validated, a data quality lock will be applied after 29 days. Related domains will receive the property '''X-NOMINET-DATA-QUALITY-LOCK=1'''.
This will suspend the domain name and it will stop resolving.

=== Transfer In procedure ===

'''First of all, a transfer should be requested for the domain with the TransferDomain command or via the control panel.'''

Then the registrant of the domain name has to contact their current registrar and ask them to change the Registrar-Tag to '''1API-DE'''. As soon as this has been completed, the domain name transfer should succeed automatically. Please note that when a .UK domain is transferred, the remaining registration period remains unchanged. '''Please do not forget to initiate the transfer in our system, otherwise the domain can not be assigned to your account and will not be renewed.'''

=== Grandfathering ===

Nominet offers Registrants, who already own a .CO.UK domain the possibility to register the name-pendant under .UK. The HEXONET internal handling. In case that the .CO.UK domain is registered with HEXONET, the corresponding UK domain can be registered by using exactly the same registrant details, the UK domain has, in addition the client has to provide the authorization-code of the already existing .CO.UK domain. In case that the corresponding .CO.UK domain is not registered with HEXONET, the domain can only be registered by adding the identical registrant contacts. Once the order has been submitted, Nominet sends and email to the registrant, asking to validate his identity. Once validated, the domain will go active.

=== Transfer Out procedure ===

Please contact the gaining registrar to determine their Registrar-Tag and then use the PushDomain command or Control Panel to Push the domain to that new tag.
Please note that pushing a tag is irreversible and cannot be cancelled. You must either contact the registrar who it got pushed to, or the registry.

<pre>
COMMAND = PushDomain
DOMAIN = (domain)
TARGET = (tag)
</pre>

=== .SCH.UK domains ===

If a school wishes to hold a .sch.uk domain, they need to submit their request to the registry in
writing on their school letterhead.

There is one .sch.uk domain per school, and the registry enters the registrar/provider tag at the
time of registration. If the school already has a .sch.uk domain name registered, they can
have a crossover period of up to three months where both domain names can remain active.
After this period, the old domain name will be cancelled.

Once the domain has been registered with the Registry, you can request that it be assigned to us, using IPS tag '1API-DE' and you need to request a transfer in of the domain via your account.