A website can look healthy on Monday and disappear from view after a missed domain renewal. Email using that domain may be affected too. The page design is still there, but the address that takes people to it is no longer doing its job.
The risk is easy to miss when a business has several brands, redirects and old project names. One person remembers the main website. A different person receives the renewal email. The payment card belongs to somebody who is not involved in the website at all.
MightyGroupUK currently has a parent website and four current brands, each with its own specialist website. That makes domain renewal a sensible parent-level check. The brand teams can manage their own websites, while a shared register shows whether every important domain has a clear owner and enough time left to act.
List the domains that still have a job
Start with every domain the portfolio relies on. Include the obvious websites, then look for addresses that are easier to forget:
- domains used for business email;
- redirects from an old name or previous web address;
- domains held for a project that is paused or still in development;
- addresses used to verify another service;
- domains kept to protect a current name or preserve a piece of business history.
Do not assume that a domain with no visible website is unused. Check what it points to and whether email, sign-in or verification records depend on it. If nobody can explain why the business still holds it, record that question rather than quietly allowing it to expire.
The MightyGroupUK story separates current ventures from earlier projects. A domain register needs the same honesty. Mark each entry as current, redirect, held for a defined reason, under review or approved for retirement.
Record enough information to act
A useful register is not a password list. It should tell an authorised person where to go, who can make the decision and what needs checking.
| Field | What to record |
|---|---|
| Domain | The full domain name and the brand or project it supports. |
| Purpose | Website, email, redirect, service verification, name protection or another defined use. |
| Registrar | The company through which the domain is registered. |
| Renewal date | The confirmed expiry date and the date the business plans to review it. |
| Responsible owner | The person or role accountable for deciding whether it should be renewed. |
| Renewal contact | The monitored inbox that receives notices from the registrar. |
| Payment route | A reference to the approved payment method and who can update it, without recording card details. |
| Access route | The approved password manager or secret-store entry, never the password itself. |
| Dependencies | Websites, email addresses, forms, redirects and services likely to be affected by a change. |
| Last check | When the registrar record, renewal settings and dependencies were last confirmed. |
Keep evidence with the record where practical. A receipt or registrar confirmation can show that a renewal completed, but the register should still be updated with the new expiry date after somebody checks it in the registrar account.
Do not leave reminders with one person
Renewal messages only help if they reach an inbox that somebody reads. Check the registrar’s contact details and make sure the address will survive a staff, supplier or role change. A monitored business inbox is usually easier to hand over than a personal address.
ICANN’s renewal guidance for registrants advises domain holders to keep contact information current, track expiry dates and understand their registrar’s renewal terms. It also notes that payment information needs to stay current when auto-renewal is used.
Auto-renewal is a useful backstop. It is not proof that the next renewal will succeed. A card can expire, an account can be locked or a notice can go to an abandoned address. The register gives the business another route to spot the problem.
Plan before the expiry date
The expiry date is the last boundary, not the best date for a decision. Set an earlier review point that leaves time to confirm the business still needs the domain, update payment details and resolve an access problem.
Rules after expiry vary by domain type and registrar. Nominet’s current .uk renewal reminder information shows that an unrenewed .uk domain moves through notices, suspension and eventual cancellation. ICANN likewise tells registrants to read their own registrar’s terms because renewal options and fees can vary.
Those recovery periods should not become the plan. A domain that stops resolving can affect a website and services connected to it before the business finally loses the registration.
Check the services behind the name
Renewing the domain is only part of the check. Confirm that its name servers still belong to the intended provider and that the expected website and email routes work. Record who manages the DNS, even when that is a different supplier from the registrar.
GOV.UK’s domain security guidance is written for .gov.uk technical contacts, so its specific controls do not automatically apply to every business. Its broader point is relevant: domains are business assets, and renewal, name-server configuration and recovery information need active management.
When a website moves to a new host, check whether the registrar, DNS provider and email provider changed too. A successful site launch can hide an old account that still controls part of the route.
Give retirement the same care as renewal
Some domains should not be renewed forever. An old address may have no remaining audience, no useful redirect and no continuing business reason. Letting it expire without a decision is still poor record keeping.
Before retiring a domain, check whether it receives email, appears in printed material, redirects visitors or verifies another account. Decide whether a notice or longer redirect period is needed. Record who approved the retirement and when the business will review any remaining references.
This connects with the wider project closure checklist. Public information, accounts and records do not all disappear at the same time. The domain decision should sit inside that larger close rather than happen by accident months later.
Finish each review with named actions
Sort the register by the earliest planned review date. Deal first with entries that have unclear ownership, an unmonitored contact address, an uncertain payment route or an expiry date that has not been confirmed.
Every open item needs an owner and a check date. That action may be confirming the registrar, moving notices to a monitored inbox, updating the payment route, testing a redirect or preparing a documented retirement decision.
Put the earliest review date in the shared calendar before closing the register. A document nobody revisits will not prevent a missed renewal. The working version should help an authorised person find the registrar, understand what depends on the domain and act before expiry.