How to Monitor Domain Expiry and Avoid Losing Your Business Name
A lapsed domain is the worst kind of outage. Every email address bounces. Every customer link 404s. Every login redirect goes nowhere. Recovery, when possible at all, takes days and costs hundreds or thousands of dollars. The cause is usually a single missed renewal email two months earlier. Domain expiry monitoring is the cheapest insurance in the industry and the most-skipped. This guide covers how the renewal process actually fails, what to monitor, and the habits that ensure your business name does not lapse.
Why auto-renewal is not enough
Most registrars offer auto-renewal. Most account holders enable it. Most lapses happen with auto-renewal enabled. The reason is that auto-renewal depends on a chain of conditions that often quietly breaks: the credit card on file has to be valid, the billing email has to be reachable, the registrar has to actually charge it, and the charge has to succeed.
Each link in the chain produces real lapses. The card expires and the holder ignores the renewal notice. The billing email goes to a former employee. The registrar's payment processor flags the charge as fraud. The card is charged but the renewal silently fails because the domain was on a restricted list. In every case, the registrar's terms of service treat the lapse as the holder's responsibility.
How registrars warn (or do not warn) you
Most registrars send renewal reminders. Most account holders do not read them. The reminder cadence varies, but a typical schedule looks like the following.
- 60 days before: a low-key reminder that auto-renewal will run in 60 days, usually buried under other notifications.
- 30 days before: a more pointed reminder, often after the first attempted charge if there was one.
- 7 days before: a serious 'your domain will expire in a week' message that nobody can miss but everyone forwards to spam.
- Expiry day: the domain stops resolving (or enters a grace period; the details depend on the TLD).
- 30 to 90 days post-expiry: redemption period. You can still recover the domain, usually with a hefty fee added.
What independent monitoring catches that the registrar does not
External WHOIS monitoring queries the registry directly, not the registrar's account. It sees the actual expiry date as recorded in the registry, not the renewal status reported in the registrar's UI.
This catches three failure modes that registrar-side reminders miss. Auto-renewal that silently fails. Manual renewal that was attempted but did not complete (clicked the button, payment failed, browser closed). A domain that was transferred away without your knowledge through a registrar lock failure. In each case, the registrar's account-level view says everything is fine; the actual registry record tells a different story.
The warning windows that work
A monitoring tool that alerts at 30, 14, and 7 days before expiry covers most recovery paths. Three windows, three escalating actions.
- 30 days: low-priority email to whoever owns billing. Time to verify the card on file is current and the renewal will actually attempt.
- 14 days: medium-priority alert to the operations channel. Time to actually log into the registrar and renew manually if auto-renewal has not fired.
- 7 days: high-priority alert to the on-call rotation. If the domain is still not renewed, something is broken and a human needs to handle it now.
- 1 day: page someone. This is the 'we are about to lose the business name' alert. Manual renewal, call the registrar's support line, do whatever it takes.
Beyond the apex domain
Monitor more than just the company's primary domain. Three other categories of domain are common forgotten ones.
Typo domains and brand-protection domains: the eight similar spellings of your name that you bought once and never renewed. Defensive domains: country code TLDs you registered when you considered expanding abroad. Vanity domains: the cute project domain you used for a launch three years ago. Any of these lapsing exposes you to typosquatting, traffic redirection, or brand attack. Monitor them all, even if you do not use them.
A starter setup for domain expiry monitoring
For your primary domain, add a WHOIS monitor with alerts at 30, 14, 7, and 1 day before expiry. Route the 30-day alert to billing, the 14-day to operations, the 7-day to on-call, and the 1-day to a phone-call channel. For each typo, brand-protection, and defensive domain, add a WHOIS monitor with a single 30-day alert. The total cost is minutes of setup time and a single line item on your monitoring bill. The cost of skipping it is the price of losing the business name.
Try MonitorAH free
Three monitors, alerts in under a minute, no credit card. Cover one website and one cron job in the time it takes to read this paragraph.
Start monitoringRelated articles
SSL Certificate Monitoring: a Practical Guide for 2026
How to monitor SSL certificate expiry, what to alert on, and the operational habits that stop browser warnings in their tracks.
Cron Job Monitoring with Heartbeats: a Practical Tutorial
How heartbeat monitoring catches the cron jobs that fail silently, with concrete examples in bash, Python, and Node.
How to Monitor a REST API for Uptime and Response Time
What to check in a REST API monitor, the right thresholds, and how to catch the silent failures that ping checks miss.