Nobody decides to let a domain expire. Domains are lost because a notice went somewhere nobody reads, for a name nobody remembered registering.
Build the inventory
One list, kept anywhere you will actually find it. Per domain:
The name. The registrar. The expiry date. What it is for. Who is responsible. Whether auto-renewal is on. Where its DNS is hosted.
That last one matters more than it looks. A domain whose DNS is at a third provider has a second dependency that is invisible from the registrar.
whois example.com | grep -iE 'registrar|expiry|expiration|name server'
Building this list for the first time typically turns up two or three domains nobody knew were still being paid for, and one that expires next month.
One contact address, and not on these domains
All registrar notices should reach one monitored address.
It must not be a mailbox on any domain in the list. A domain that expires takes its own mail with it, so the notice about the expiry cannot be delivered, and the same applies to the verification message that suspends a domain fifteen days after it is ignored. Unverified contact details goes over that second failure.
A shared address that more than one person reads is better than a personal one, because people leave.
Auto-renewal is necessary and not sufficient
Turn it on everywhere. Then note what it does not cover.
It fails when the payment card expires, and it fails quietly; the attempt is made, declined, and the domain proceeds toward expiry while everyone assumes it is handled.
Card expiry dates therefore belong in the same list, and a payment failure notice deserves the same urgency as an expiry notice. Enabling domain auto-renewal walks through turning it on.
Long registrations for the ones that matter
Register the domains your business depends on for several years at a time.
Each renewal is an opportunity for something to go wrong, and reducing the number of renewals reduces the number of opportunities. It costs no more per year.
Keep the speculative and secondary names on one-year terms, which also forces an annual decision about whether they are still worth keeping.
Consolidate, with a caveat
Domains scattered across four registrars are four inventories, four sets of notices and four accounts to keep secure.
Consolidating makes the whole thing manageable, and it concentrates the risk: one account now controls everything. That account needs two-factor authentication and a password used nowhere else, without exception.
Moving domains between registrars is a transfer; moving them between accounts at the same registrar is much simpler and often what is actually needed. Moving a domain between registrar accounts explains the distinction.
Keep the locks on
Transfer lock should be on for every domain that is not currently being moved. It is the protection against a domain being transferred away without your involvement.
Domain locking goes over it, and checking the lock status across the portfolio is a two-minute annual job.
Review once a year
Read the list. For each domain ask whether it is still needed, whether its contact is still reachable, and whether the person responsible still works here.
Cancel what is genuinely unused rather than renewing it indefinitely by default, and note that a domain you release may be picked up by someone else, which matters if it ever hosted anything or received mail.
This belongs in the same annual round as certificates and backups. For the rest of it, see the yearly maintenance checklist.
Who is the registrant, actually
The most valuable field in the whole registration, and the one nobody checks until it matters.
whois example.com | grep -iE 'registrant|admin'
The registrant is the legal owner. The account holder is whoever can log in. Those are frequently different people. A developer, an agency, a former employee, and the difference only surfaces during a dispute, a departure or a sale.
If the registrant is not you or your company, that is worth correcting now, calmly, rather than during a disagreement. Note that changing it can start a sixty-day transfer lock on many registrars, so do it when no move is planned. There is more on the routes when it is somebody else's in moving a domain between registrar accounts.
Domains registered on behalf of clients
Anyone managing domains for other people faces a decision that is easier to make deliberately than to discover.
Registering in your own name is simpler to administer and means the client cannot leave without you. That is a hold you may not want, and it becomes a real problem when the relationship ends badly or your business changes hands.
Registering in the client's name with you as a technical contact is more work and is the arrangement that survives every ending. There is more on the wider version in what to do when a client leaves.
Whichever you choose, state it in writing at the start. Every dispute about domain ownership begins with two people who assumed different answers.
Check the whole portfolio in one pass
for d in $(cat domains.txt); do
e=$(whois "$d" 2>/dev/null | grep -iE 'expir' | head -1 | sed 's/.*: *//')
l=$(whois "$d" 2>/dev/null | grep -c 'clientTransferProhibited')
printf '%-28s expiry=%-24s lock=%s\n' "$d" "${e:-unknown}" "$l"
done
Run twice a year against the list. It finds three things reliably: a domain expiring sooner than anyone thought, a lock that came off for a transfer and was never restored, and a domain nobody can account for.
Rate limits mean this is slow across many domains: add a short sleep, or run it in batches.
Releasing a domain deliberately
Letting a domain lapse is not a neutral act, particularly one that has been used.
Someone else may register it, and it will still receive mail addressed to the old addresses, still be reached by old links, and still be trusted by anything that remembers it. For a domain that once hosted a business, that is a genuine exposure.
If a domain is being retired rather than sold, consider keeping it registered with the mail-refusing records in place rather than releasing it. Parking or holding a domain explains those records, and the cost of one registration is small against the alternative.