How to Avoid Losing Your Domain to an Expired Registration
Losing a domain to an expired registration is almost always avoidable, and it is almost always painful. A business can lose its website, its email and years of search visibility in a few weeks, and the name may end up in the hands of someone who bought it for the traffic it still attracts. A few habits remove nearly all of the risk.
How domains get lost
Most losses are boring. A credit card expires, the renewal email goes to an old address, the person who registered the name leaves the company, or two people each assume the other is handling it. Nobody decides to let the domain lapse, and by the time anyone notices, the site is down.
The quickest way to check if domain is expired is to read its registration record, which shows the expiry date, the registrar and the status codes. The SEO.Domains guide on the subject covers registrar dashboards, WHOIS, RDAP, status codes and monitoring tools, and notes that the registry expiry date is the figure that counts.
Make that check a routine for every name you own. A two minute look each quarter finds problems while they are still cheap to fix, and a record of what you found keeps the habit honest.
Treat every domain as infrastructure, in the same category as hosting or payroll, and give it a named owner.
Know the rules that protect you
ICANN's guide for domain owners states that registrars must send two renewal reminders, roughly one month and one week before expiration, and that after a registrar deletes a name the owner has only 30 days to restore it, a period called the Redemption Grace Period. It also notes that the registrar may offer an auto renew grace period of between one and 45 days after expiration.
The rules protect people who pay attention. Reminders only help if they reach someone who reads them, and the grace periods only help if the owner acts inside them. The guide also advises that anyone transferring a name to another registrar should finish the transfer well before the expiration date.
Read your registrar's terms as well. Fees for late renewal and restoration are set by the registrar, not by ICANN, and they can be large enough to make the difference between rescuing a name and abandoning it.
Print the key dates from your registrar and keep them somewhere visible.
Build renewal safeguards
Turn on automatic renewal wherever it is offered, and keep a payment method on file that will not expire soon. Auto renew fails when a card is cancelled or a limit is reached, so a second layer is needed. Add the expiry date to a shared calendar with reminders at sixty, thirty and seven days.
Register for several years at once when the price allows. A multi year term pushes the deadline far out and reduces the number of chances for something to go wrong, though it does not remove the need to check. Lock the domain against unauthorized transfers while you are there.
Write down where each domain is registered and who has access. A short sheet listing the name, registrar, expiry date and responsible person takes minutes to build and saves hours in an emergency.
Test the safeguards once a year by simulating a failure, for example by removing the card on file for a day and confirming that the alerts fire.
Keep contact details and access current
Renewal notices go to the contact address on the registration. If that address belongs to a former employee or an old domain that no longer receives mail, the warnings vanish. Use a shared role address, not a personal one, and make sure at least two people can read it.
Limit account access sensibly, but never to one person. Two people with login rights, plus recovery options that do not depend on a single phone number, keep the account usable when someone is on leave or leaves the company. Review who has access whenever the team changes.
Separate the registrant from the individual. Registering a company's domain in an employee's name creates a dependency on that person, and disputes over ownership are slow and expensive. Register in the name of the organization, with a role based contact, and document who is authorized to change settings.
Protect the registrar account with strong, unique credentials and two factor authentication. An attacker who takes over the account can transfer a domain or let it lapse, which has the same effect as an oversight. Store recovery codes where more than one trusted person can find them.
Record changes. A short log of who altered contact details or settings, and when, helps resolve questions later and shows whether an expiry problem began with a change nobody remembered.
If the domain has already lapsed
Act the same day. Log into the registrar and look at the status. If the name is in the early grace period, renewing is simple and usually costs the standard fee. If it has been deleted and is in redemption, restoring it is still possible, although a restoration fee normally applies.
If the window has closed, check whether the name was captured by someone else and what they are asking. Buying back a name is often cheaper than rebuilding what you lost, and in the meantime put a notice on any other channel that customers use, so that they know where to find you.
Gather evidence while you work. Screenshots of the registrar status, the dates of every notice and a note of what you tried help if you need to file a renewal complaint with ICANN, which it accepts in certain cases, or to negotiate with a new owner.