A UK domain drop list helps identify registrations that may become available after deletion. It is evidence about a registry process at a particular time, not a list of names already available to buy and not a guarantee that a backorder provider will obtain a name for you.
Use DomainSabre's UK drop search to explore the accepted published list, including today, tomorrow, .co.uk and direct .uk collections. This guide explains how to interpret that evidence. Read a record alongside its source specification, generation time and applicable registry procedures. In particular, keep an expiry date, a potential drop time and a completed new registration separate.
Expiry is not the same as a drop
An expired registration can still be within a stage in which renewal is possible. In the current legacy .UK process, Nominet's expiry and drop-list specification describes records that may drop as well as names in their final deletion period. A name renewed while renewal is allowed is removed from the following daily list.
Use the .UK lifecycle guide to understand the stages and exceptions. Do not turn a date from an old record into a universal expiry-plus-days calculation. The state of the registration and the procedures applicable to it still matter.
Find the official list and its specification
Nominet's public drop-list page links the compressed UK data file and its checksum. It also links the relevant technical specification. Check the official page rather than relying on a copied file whose origin and age are unclear.
The legacy specification identifies a repository object identifier, the domain and a UTC drop time. These fields answer different questions. A repository identifier helps distinguish a registry object; it is not a seller identity, valuation or proof of a purchase right.
Fictional record, explained
Illustration only. This table is not a copied registry record. “Illustrative name A” is not an actual domain or an offer, and the timestamp is invented to demonstrate notation.
| Field | Fictional value | How to interpret it |
|---|---|---|
| Repository object identifier | ILLUSTRATION-001 |
A made-up identifier representing the object's identity within this example |
| Domain | Illustrative name A | The exact name would belong here in a real record; this label is deliberately not inventory |
| Drop time | 2026-11-05T09:30:00Z |
ISO date and time; the Z denotes UTC, not an unspecified local time |
| Evidence note kept by the reader | File observed at a recorded time | Your observation record, not an additional registry field or proof that the name will be obtained |
When displaying a real timestamp in UK local time, retain the original value and identify the conversion. UK clocks change between GMT and BST; do not apply a permanent one-hour adjustment to every record. Comparing times without a timezone can create a false discrepancy.
Check freshness before drawing a conclusion
Record when the file was obtained and, where available, its publication or modification information. Keep a checksum with the file when using it for an internal review. A newly downloaded copy can still be the same published version; a later download time does not necessarily make its contents newer.
A missing row, a failed download and a name successfully registered by someone else are different observations. If a service is unavailable, record that limitation. Do not report the name as available merely because a query or file could not be read.
Recheck the appropriate current evidence before making a time-sensitive decision. A daily snapshot cannot establish everything that happened after it was produced. DomainSabre's search separates source publication, successful import and last-check information. An unchanged file does not become newer when checked again. Stale or unknown-age source data pauses new reminder creation and sending; an import failure does not prove that a listed name has been withdrawn.
A UK WHOIS lookup returns a separate observation of public registration details. Under the legacy process, Nominet explains that RDAP can still show a registration while a scheduled deletion awaits completion. A lookup is therefore not a drop clock or a substitute for the source's published time.
Distinguish current and scheduled documentation
At the source review for this guide, Nominet's .UK future-state reference identifies the existing platform as legacy and schedules the new platform for 9 February 2027. Future documentation should not be treated as proof that the transition has already happened.
| Source context | How to use it |
|---|---|
| Legacy .UK expiry and drop-list documentation | Interpret records under the current legacy process and its stated exceptions |
| Common Dragon drop-list specification | Prepare for the published platform model, while checking applicability to the actual registry and state |
| .UK transition guidance | Check whether a registration's state at cutover changes how its earlier dates should be interpreted |
The Dragon specification distinguishes redemption or restore stages from the final pending-delete period, and explains that some records can leave the list after renewal. It also describes daily files and UTC timestamps. Do not assume an old parser's interpretation remains correct simply because the replacement file is also CSV.
Follow the Nominet transition hub for the source state and the data-services guide for the role of different queries and reports.
Keep public lists and restricted reports separate
Nominet's unavailable-names report documentation limits access to registrars accredited with the relevant registry and restricts publication and use. It is not an unrestricted public dataset interchangeable with the public drop list.
Follow the conditions attached to the source you use. Public access to one report does not confer permission to republish another, and a screenshot supplied by someone else does not establish a reuse licence. DomainSabre's searchable drop list uses the public source with visible provenance; it does not reproduce the restricted report or turn public registration lookups into bulk enrichment.
What a prospective buyer can conclude
A record can justify further research into a possible drop. It does not allocate the name to you, prove a provider has caught it or settle a later sale. A provider may fail to obtain it, and a successful catch may be followed by another allocation step under that provider's rules.
Before placing a request elsewhere, read UK domain backorders, drop catching and backorders versus auctions. Identify when any charge or purchase obligation arises. An email reminder or downloaded calendar entry provides information; it does not attempt registration, and a calendar file does not automatically follow a later schedule change. Return to the guide directory for history, valuation and transfer research that remains relevant whichever acquisition route you use.