Plan the .UK registry transition as a handover of real domain states and unfinished work. A changed connection target is only one part of that handover. The team needs to know which requests completed, which require a new procedure and which records need reconciliation before ordinary automation resumes.
The date is currently scheduled for 9 February 2027. This guide does not publish a downtime estimate or live service status. Use Nominet's formal notice, current operational announcements and official status page when finalising timing.
Before cutover
Assign an operational lead, a technical lead and an escalation route appropriate to the service. Agree how support staff will identify a transition-related problem and how unresolved work will be recorded. Make the decision to resume a workflow depend on evidence rather than on a timer reaching the scheduled date.
Prepare an authorised snapshot of the relevant records: sponsoring registrar, expiry and state, pending operations, host relationships and notification progress. Store it within the organisation's normal secure systems. Compare it with your own records before cutover so that an existing discrepancy is not automatically attributed to the migration.
Confirm the intended environments and authentication using the environment guide and EPP preparation guide. The official transition instructions specify the move from the legacy EPP endpoint to the new .UK endpoint. Treat that as a scheduled cutover instruction, not a reason to redirect current production traffic early.
Review outstanding operations
List requests that are in progress, waiting for another party or uncertain after a connection failure. For each, retain the request time, domain, operation, expected outcome, latest evidence and responsible person. Distinguish “accepted for processing” from “completed”.
Nominet's transition guide says pending legacy transfers awaiting a gaining-registrar handshake will be cancelled at transition. A registrant who still wants the move will need to restart using the new procedure. Do not leave a local record permanently waiting for a legacy handshake that will not complete.
Review renewal and restoration cases with customer impact, particularly names whose remaining options may change. Use the transfer and lifecycle guides to identify the distinction involved, then apply the current official operational instructions to the actual case.
State-dependent transition checks
The following summarises selected treatment in the published transition plan. It is not an exhaustive algorithm or a substitute for the latest registry record.
| State described in the official plan | Scheduled treatment to examine | Practical check |
|---|---|---|
| Already in the final five-day pending-delete grace period | Existing purge timing continues | Preserve the actual state and time rather than recomputing from a generic formula |
| More than 75 days past expiry in the identified legacy non-renewal group | A new final five-day pending-delete period begins; restoration is unavailable | Identify affected cases before cutover and review customer expectations |
| More than 30 but less than 75 days past expiry in the described redemption group | Redemption ends at expiry plus 75 days | Reconcile the migrated end time and eligible operation |
| Less than 30 days past expiry | The described auto-renew period runs to expiry plus 45 days | Check the registrar mode and resulting state |
| Pending legacy handshake transfer | The old transfer process is cancelled | Establish whether a newly authorised transfer is still required |
These are source-defined cohorts. Do not infer an undocumented boundary case from a rounded “days expired” display; exact timestamps and current registry instructions matter. Obtain Nominet clarification if the source does not resolve a case your system must handle.
The same official guide describes subordinate-host cleanup and later restoration considerations. Identify domains that depend on nameservers beneath another affected domain. After a restore, check the relevant host objects and associations rather than assuming restored registration automatically restores every DNS dependency.
After the transition is confirmed
Verify the intended production environment, authenticated identity and supported operations before broadening normal traffic. Use authorised, proportionate checks; a customer domain should not become an improvised destructive test fixture.
Check that new and pending results are reflected accurately in the customer-facing system. Confirm that notifications are consumed and that failed actions remain visible to staff. A login success or a single successful query cannot establish that renewal handling, transfers and all reporting jobs are healthy.
Review instructions issued by support during the handover. If a customer was told to follow the old process, assign someone to determine whether a fresh authorised request is necessary. Avoid repeatedly asking the customer to complete a step that no longer belongs to the live procedure.
Reconcile registry records and internal records
Nominet publishes a post-transition synchronisation approach that prioritises records and limits concurrent reconciliation work. Follow the latest guidance rather than initiating an unbounded full-portfolio burst.
Compare the observed registrar, domain status, expiry and grace-period information with local expectations. Include contact and host dependencies where the workflow uses them. Keep the record's underlying event time separate from the time you fetched it.
An incomplete or failed data run should remain labelled incomplete. Do not delete local records because an interrupted response omitted them, or treat a timeout as confirmation that a registration disappeared. Put unexplained differences into an exception list, with the evidence, next action and owner.
For a public drop-list service, reconcile a complete, validated source generation before resuming reminders. Do not declare withdrawals from a failed import or a different coverage window. Review changed times, close superseded occurrences and skip reminders whose useful time has passed. The scheduled transition date alone must not switch a parser, source regime or sending policy. UK drop search and UK WHOIS lookup expose different observations; neither is a replacement for authorised registry reconciliation.
When to escalate
Escalate a failed connection whose cause remains unclear, an unexplained state mismatch, a transfer that appears to have completed differently from the authorised request, or a customer-impacting DNS dependency that cannot be reconciled. Provide times, environment and sanitised transaction references; omit secrets from an ordinary support report.
Use Nominet's official contacts for the relevant registrar or registrant support route and its status page for current incident information. The status link here is a destination, not a claim that systems are currently available or unavailable.
A deadline that applies only to departing registrars
The formal notice gives 10 January 2027 as the notification deadline for registrars choosing to leave under that notice. It is not a universal readiness deadline for every domain owner or registrar. The applicable termination and domain-transfer obligations should be read in the notice itself.
Return to the readiness checklist for the wider work and the transition overview for applicability. Retain the decisions and unresolved cases after cutover so the handover can be understood by the next person responsible for the service.