Renewal ops · Beginner · 10 min once, then never
How to stop a domain expiring — Monitor the Expiry Date the Way You Monitor Uptime
You do not want the first sign of a lapsed registration to be a monitoring alert telling you the whole site has stopped resolving.
The short answer
Stop relying on remembering. Turn auto-renew on, put a card on file whose expiry date is later than the domain's, route registrar mail to a monitored mailbox rather than a person, and add an expiry check to the same monitoring that already watches uptime.
An expired domain is not a billing inconvenience, it is a total outage: the delegation stops answering, so the website, every mailbox and every API integration on that name go at once. Recovery after the grace period means a registry restore fee, and the fee is the smaller half of the cost.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Skill floor
Quick
Hands-on time
5
Steps in total
24/7
Support on call
Ten minutes to set up across an account, and then it should never need your attention again. You need client area access and the card details you want on file.
Nothing here is risky. The only judgement call is which names deserve a multi-year registration, and that is a question about what an outage on each one would cost you.
The sequence after the expiry date, stage by stage
First comes the registrar's grace period, during which a straightforward renewal usually still works and the domain may or may not still resolve — many registrars park it immediately, so your outage can start on day one. Then the redemption period, where the name is held but recovering it costs a registry restore fee rather than a renewal.
After redemption comes the pending delete window, and then the name drops to the open market where anyone can register it. Exact durations vary by registry, so the practical takeaway is that your safe window is much shorter than the total, and it starts closing on the expiry date itself.
Auto-renew fails on the card, not on the calendar
Almost every lapsed domain in a support queue had auto-renew switched on. What it did not have was a working payment method: a card that expired first, a bank that declined an unfamiliar recurring charge, or a billing address that changed after a house move.
So treat the card as part of the control. Put one on file whose own expiry is later than the domain's next renewal date, and diarise the card, not the domain. If the card cannot outlive the renewal, you have a reminder to set regardless of what the auto-renew toggle says.
Monitor the date instead of trusting the notice
Registrar warning emails go to one address, and that address is usually a person. People leave, filters get aggressive, and a warning that lands in a spam folder is not a warning. Route registrar mail to a shared, monitored mailbox, and treat anything from it as an alert rather than as correspondence.
Better still, check the date programmatically. whois yourdomain.com piped through grep for the expiry field gives you a date you can compare against today in a cron job, and a check that fires at thirty days and again at seven turns an invisible deadline into something your monitoring already understands.
Which names justify a multi-year registration
Stack years on anything whose loss would be unrecoverable: the primary brand, the domain your mail runs on, anything printed on physical material, and anything an API integration or an OAuth callback depends on. Multi-year registration removes several annual renewals, and each renewal is a chance to fail.
Keep the speculative names on a single year and review them at renewal. That is also the moment to decide whether a spare name is still earning anything, rather than renewing a shelf of domains out of habit for another decade.
Why the follow-through is quick here
Guides written against imaginary hosting go stale fast. These are written against the real thing: the same panel, the same installer, the same defaults sitting in your account when you log in.
The rate you sign up at is the rate you renew at, so year two costs what year one did. There is no introductory price to unwind later.
- Expiry treated as an outage, not a bill
- The card handled as part of the control
- A check your monitoring can actually run
- Engineers on support at any hour
Why HostingFast
Standard on every plan
Framed as an outage
An expired name takes the site, the mail and every integration at once, and the page is built around that rather than around a payment reminder.
The real failure named
Auto-renew almost never fails on its own; the card behind it does, so the card gets its own step.
Monitored, not remembered
There is a whois-based check you can put in cron next to your uptime monitoring, which is what turns a deadline into an alert.
5 steps, no padding
Five actions, done once, each finishing in a setting you can verify from the client area or a shell.
Multi-year where it pays
The page says which names justify stacking years and which should stay annual, instead of recommending everything indiscriminately.
Engineers on call
If a renewal payment fails at an awkward hour, support is staffed to sort it before the grace period starts working against you.
Quick Start
From order to online
- 1
List every name you hold and its expiry date
Pull the list from the client area, and for anything registered elsewhere read the expiry from whois. You cannot protect a domain you have forgotten you own, and the forgotten ones are usually the ones with a live redirect on them.
- 2
Turn auto-renew on across the whole account
Enable it per domain rather than assuming an account-wide default applied. Take a screenshot or note the date you did it, because this is a setting that quietly reverts when a domain moves between registrars.
- 3
Put a card on file that outlives the domain
Check the card's own expiry against the next renewal date. If the card goes first, the renewal fails on a working auto-renew setting, which is the single most common way a monitored, well-run domain is lost.
- 4
Route registrar mail to a monitored mailbox
Point the registrant and billing addresses at a shared mailbox somebody reads, on a domain other than the one at risk. Add the registrar to the allow list so a filter cannot quietly discard the only warning you will get.
- 5
Add an expiry check to your monitoring
Run a cron job that reads the expiry date from whois and alerts at thirty days and again at seven. Put it beside the uptime check for the same host, so the domain and the service it serves are watched by the same thing.
Built In
Loaded onto every plan
- A renewal price identical to the one you signed up at
- Year one of the domain free when you order annually
- Support staffed by humans, every hour of the day
- Daily backups with self-service restores from the panel
- WordPress and 400+ other applications in one click
- 99.9% uptime as the target, monitored around the clock
- No setup fee on any plan, at any tier
- In-place account upgrades, with no migration to change plan
- Softaculous for one-click application installs
- Webmail in the browser plus IMAP, POP and SMTP
Frequently Asked
What people ask us most often
Can I script an expiry check from whois?
Yes, and it is the most useful ten lines you will write this month. whois yourdomain.com | grep -i 'expiry\|expiration' returns the date for most gTLDs; parse it, compare it against today, and exit non-zero inside the window you care about. Run it daily from cron and let your existing alerting do the shouting. Field names vary by registry, so test it against each TLD you hold.
Does auto-renew help if my card expires first?
No, and this is the gap that catches careful people. Auto-renew only authorises the attempt; the payment method has to succeed. A card that expires before the domain does means the charge is declined, the retry schedule runs out, and the domain lapses with the toggle still showing as on. Check the card's expiry against the renewal date, not against the calendar year.
What does recovering a domain in redemption cost?
More than a renewal, and the amount is set by the registry rather than by your registrar, so it varies by TLD. Treat the number as unknown and unpleasant, and treat redemption as a failure state rather than a fallback. The practical point is that the cheap window closes at the expiry date, not at the end of the grace period.
Does the site keep serving during the grace period?
Do not count on it. Many registrars suspend the delegation on the expiry date and park the name immediately, which means the site, the mailboxes and any API on that hostname all stop even though the domain is technically recoverable. Grace protects your ability to renew; it does not protect your uptime.
Keep reading
How to Publish a DMARC Policy
Publish a policy that tells receivers what to do with mail that fails authentication, and read the reports it produces.
How to Change Nameservers
Build the destination zone, diff it record by record, then move the delegation and watch the parent.
Domain Registrar (Glossary)
The definition this page leans on, with the registry relationship spelled out.
AI Website Builder
Describe the site you want and publish it, with no template wrangling in between.
Charity Hosting
Discounted hosting for registered charities, on the same NVMe platform as everything else.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Keep the name, and keep it quick.
NVMe behind a LiteSpeed cache, free SSL, free migration, and a renewal price identical to the one you signed up at.
View AI Website Builder plans