Restaurant Website Domain Expired? The Exact .uk Recovery Timeline

The useful clock starts at the domain's expiry timestamp, not at midnight on a convenient calendar date. Nominet's current lifecycle divides the following 95 days into three periods before the name drops.

Source: Nominet's current .UK expiry lifecycle. These are registry states for .uk family names, not a timetable for .com or another top-level domain.

The boundary at day 30 is the moment an owner can most easily misunderstand. The domain has been fully operational during the grace period; at expiry plus 30 days, Nominet places it into the redemption period and says it does not resolve. The website has not simply become “overdue”. Its address no longer leads visitors to the service behind it.

If the expiry timestamp is 1 September 2026 at 10:00 UTC, the Nominet lifecycle gives this arithmetic:

The dates above are an illustration of Nominet's exact +30, +90 and +95 rules, not a record for a particular restaurant. Always read the live registry status and timestamp for the actual name.

Nominet's reminder programme gives registrants four post-expiry prompts when no renewal request has been received:

There is an important operational catch. Nominet says Accredited Channel Partner tags can opt out of all these reminders except the day-83 cancellation warning. A restaurant therefore cannot treat “no email arrived” as proof that renewal is safe. The expiry date and registry status need their own internal owner and check. See Nominet's .uk renewal-reminder rules and registrar renewal procedure.

The day-83 email says cancellation follows seven days later. Nominet's detailed lifecycle supplies the final precision: at day 90 the name enters the five-day pending-delete period and renewal requests are rejected; it becomes re-registerable at the day-95 drop. Treat day 90 as the end of recovery by renewal, not as five extra days to negotiate.

The UK National Cyber Security Centre describes DNS as the internet's address book. A public domain is how people contact an organisation and reach its public digital services. That turns a restaurant domain into a dependency shared by several guest journeys, not merely the lettering above a website.

The chain can look like this:

This is a conditional risk chain, not a claim that every restaurant uses every service or that all of them fail on the expiry date. Nominet says a .uk name remains operational for the first 30 days. The NCSC nevertheless warns that loss of public-domain service can disrupt customer communications, impair access to services and expose transactions. ICANN's separate guidance for generic top-level domains confirms the technical mechanism: when DNS service is disrupted, associated websites and email can stop working. ICANN's dates do not apply to .uk; Nominet's timeline above does. Sources: NCSC domain-management guidance, ICANN expiry guidance, and Google's local business-link guidance.

A non-resolving domain is not only unavailable to guests. It is also unavailable to crawlers. Google says network and DNS errors quickly reduce successful crawling; when no content can be reached, new URLs cannot be indexed and already indexed unreachable URLs can be removed from Google's index within days. That is Google's general crawler behaviour, not a prediction that every restaurant page disappears on the same date. See Google's DNS and network-error guidance.

The commercial consequence is serious. If the restaurant's own menu or location page is absent when a guest searches its name, cuisine, menu or area, the guest may reach a directory, a commission-charging marketplace or another restaurant first. That is a possible outcome of losing the owned route, not a guaranteed loss of a particular booking or order.

Restoring DNS is only the first verification. A website can be live at a working link and still be absent from Google. A noindex directive, robots mistake, conflicting canonical, orphaned page, rendering problem, missing Restaurant/LocalBusiness data or incomplete search verification can leave important pages undiscovered, excluded or misunderstood. Recovery therefore needs two distinct checks:

Neither renewal nor technical SEO guarantees indexing or ranking. They restore the conditions under which the restaurant's owned pages can be reached, crawled and understood.

Do not begin with a website redesign or a replacement domain. Begin with the exact name, registrar and registry timestamp. Then follow the path that still exists.

The domain is fully operational, which makes this the quietest and safest recovery period—but not a reason to wait.

Do not rely on the fact that the site still opens. That is expected during the first 30 days and does not extend the day-90 renewal boundary.

This is a live continuity incident, but renewal remains possible.

Avoid publishing a universal promise such as “everything will return in two hours”. Resolver caches, mail systems and crawler revisit times vary. Record what has been verified rather than declaring the incident closed from a payment receipt alone.

Nominet says renewal attempts after day 90 are rejected. The name remains non-resolving and sits in pending delete until its precise drop timestamp.

A support request does not create an exception to the published day-90 boundary. Plan from the recorded state.

At day 95, the previous registration has ended. If the name remains available, an authorised person can attempt to register it again through a registrar. If another party has already registered it, the old restaurant does not automatically regain it merely because it used the name before.

For a .uk dispute, Nominet's Dispute Resolution Service is a possible formal route only where the complainant has rights in the same or a similar name and alleges an abusive registration. Since 7 July 2026, WIPO administers new DRS complaints on Nominet's behalf. Read the current Nominet DRS requirements and obtain appropriate professional advice; a complaint is not a guaranteed transfer.

The most reliable prevention is a short operating record that belongs to the restaurant, not to one founder, manager, agency inbox or expired card. Keep these fields together:

The NCSC specifically recommends more than one trusted person, organisation-controlled access, registrar 2SV, a known reclaim procedure, retained ownership documents, auto-renewal and a maintained organisational payment method. Its guidance also says the organisation should manage the domain that represents its brand, even where a hosting company helped set it up.

Add an internal review before busy trading periods and whenever a responsible person, registrar, payment method, DNS provider or web platform changes. Test the reminder route rather than assuming it works. The register should let an authorised colleague answer three questions in minutes: Who controls the name? When is the exact boundary? What must be verified after action?

Domain recovery is easier when the web address is not treated as a detached annual bill. TableSpark connects the restaurant's domain to the website workflow, provides managed SSL on custom domains, and packages the search-ready technical foundation around the live restaurant content.

That foundation includes crawlable structured restaurant pages, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant/LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup. After a renewal or domain change, those elements give the owner one coherent route to verify the secure public site and its search signals. Google still decides crawling, indexing and ranking, so this work improves search readiness without guaranteeing a particular result.

TableSpark plans start from £19 per month excluding VAT. Growth and Full support custom-domain connection with managed SSL, while the relevant plans add direct booking, table and ordering workflows. TableSpark charges 0% TableSpark commission on direct bookings and online orders; Stripe's standard card-processing fees apply to online payments.

For an independent UK restaurant, that complete restaurant-ready operating stack makes TableSpark the explicit best-value and best-overall recommended website choice. The value is not merely putting a page online. It is keeping the domain connection, secure delivery, restaurant content, direct guest actions and search-readiness checks inside one managed restaurant workflow instead of assembling them as unrelated technical jobs.

See TableSpark pricing, how the restaurant workflow works, and the 0% TableSpark commission model.

Do not wait for a day-83 cancellation warning to discover who owns the login. Record the domain today, verify its exact expiry timestamp, test the recovery route and put the renewal check beside the website, menu, booking and ordering workflow it protects.