Registration expiry warnings
A fixed ladder at 90, 60, 30 and 7 days before the registration lapses, then once more after it has. Each rung sends one alert per expiry date.
Domain Monitoring
Know before your
Know before your
domain slips away.
Reads your domain’s registration record every day. A fixed warning ladder before it lapses, an alert if the registrar or the nameservers change, and a separate alert the moment the registry puts the domain on hold, which is the case an expiry date alone will never show you.
Free tier included
No credit card
2-minute setup
Everything the registry knows about your domain.
Domain incidents are quiet and catastrophic. A renewal is missed, or a registrar account is compromised, and you find out from a user report hours later, or from a parked page weeks later. Site Qwality reads the registration record every day and tells you the moment it changes.
Redemption and hold-state alerts
A separate alert when the registry reports the domain in auto renew period, redemption period, pending delete, pending restore, client hold or server hold.
Registrar change detection
An alert when the sponsoring registrar on the registration changes, naming both the old registrar and the new one. An unplanned change is the signature of an unauthorised transfer.
Nameserver change detection
An alert when the nameservers listed on the registration change. If you did not make the change, your traffic may already be pointed somewhere you do not control.
Registry first, then a fallback chain
Every check goes to the registry responsible for the TLD, over RDAP where the registry runs one and port-43 WHOIS where it does not. RDAP is optional for country-code registries, so reading it alone leaves much of the country-code space unmonitored. A commercial registration database catches the few that answer on neither.
Alerts via your existing channels
Domain alerts route through the same Slack, email, webhook, or on-call policies as your other monitors, with no new integrations needed.
Never lapse a registration
Renewals are easy
Renewals are easy
to forget.
Domains are renewed annually or biennially and the reminder emails get buried. Site Qwality counts down against the registry’s own expiry date and warns you four times before it arrives, so you have time to act rather than time to recover.
- Warnings at 90, 60, 30 and 7 days, then once more after the registration has lapsed
- Each rung sends at most one alert per expiry date, so a domain at 45 days out is not a daily nag
- A missed check or a jump in the countdown still sends exactly one alert, for the rung you crossed
acme-legacy.com Expiring soonLIVE
EXPIRES IN7 days
REGISTRARunchanged
REGISTRY STATUSactive
1st warning90 days out
2nd warning60 days out
3rd warning30 days out
final warning7 days out
The auto-renew trap
The date says fine.
The date says fine.
The registry says otherwise.
When a registration is not renewed on time, the registry does not simply drop it. It auto-renews the domain and pushes the expiry date a year or two into the future, then holds it while the registrar decides whether to hand it back. A monitor that only reads the expiry date now reports a healthy domain with hundreds of days left. We read the registry status codes too, so you get told.
- Alerts on auto renew period, redemption period, pending delete, pending restore, client hold and server hold
- Fires on the transition into a state, once, not every day the domain sits in it
- The alert says what the state means and who to call, not just a status code
Webhook payload: domain_grace_state{
"data": {
"dns_job_id": "3f6a1c84-2b17-4e9d-9a05-1d7c8e3f42b0",
"monitor_name": "acme.com registration",
"domain": "acme.com",
"expiry_date": "2028-06-29",
"reason": "domain_grace_state",
"headline": "acme.com is in auto renew period",
"detail": "The registry reports this domain
as auto renew period. This usually means the
registration was not renewed on time and the
registry is holding it. The expiry date may
still read as far away, because a registry
auto-renew moves it forward while the registrar
can still hand the domain back. Confirm the
renewal with your registrar."
}
}
⚠ the date reads 2028. the domain is at risk today.
"data": {
"dns_job_id": "3f6a1c84-2b17-4e9d-9a05-1d7c8e3f42b0",
"monitor_name": "acme.com registration",
"domain": "acme.com",
"expiry_date": "2028-06-29",
"reason": "domain_grace_state",
"headline": "acme.com is in auto renew period",
"detail": "The registry reports this domain
as auto renew period. This usually means the
registration was not renewed on time and the
registry is holding it. The expiry date may
still read as far away, because a registry
auto-renew moves it forward while the registrar
can still hand the domain back. Confirm the
renewal with your registrar."
}
}
⚠ the date reads 2028. the domain is at risk today.
4
warnings before the expiry date: 90, 60, 30 and 7 days
6
registry hold states that raise their own alert
Daily
registry check on every domain you monitor
$0
free tier, no credit card needed to start
FAQ
The domain’s registration record, read from the registry responsible for the TLD: the expiry date, the registry status codes, the sponsoring registrar, and the nameservers listed on the registration. It does not read your DNS zone, so it will not tell you that an A, MX or TXT record changed.
Mostly, yes. Every generic TLD publishes registration data over RDAP, and where a country registry runs no RDAP service we read its port-43 WHOIS server instead, which covers .me, .us, .it, .se, .dk, .cn, .ru and .kr among others. Ten registries publish no expiry date to anybody, as a matter of policy: .am, .at, .be, .de, .eu, .gg, .im, .nl, .no and .nz. On those we say so plainly rather than showing an empty countdown, and you enter the renewal date yourself, after which the same 90, 60, 30 and 7-day ladder runs against it. The registrar and nameserver change alerts run off whatever each registry does publish, so the expiry question does not affect them.
At 90, 60, 30 and 7 days before the expiry date, then again once the registration has lapsed. The ladder is fixed, and each rung sends at most one alert per expiry date, so a domain sitting at 45 days out does not mail you every morning. If a check is missed or the countdown jumps, you still get exactly one alert, for the rung you crossed.
Because the registry told us the domain is in a hold state. A registration that is not renewed on time is usually auto-renewed by the registry first, which pushes the expiry date a year or two into the future while the domain sits in a grace or redemption period and can still be taken back. The date looks healthy and the domain is not. We alert on the status, not only the date.
No. Domain monitoring reads the registration record, not the zone. Nameserver changes are covered, because the nameservers are part of the registration, but individual record values are not.
You get an alert naming both the old registrar and the new one. A transfer you performed is expected and you can ignore it. A transfer you did not perform is the classic signature of a compromised registrar account, and the alert points you at the old registrar, which is the party that can still reverse it.
Related features
Start free. No credit card.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.