Domain expiry monitoring
Reads the registry directly over RDAP and warns 60, 30, 14, 7 and 1 day before a domain lapses — the one event a person with a payment card actually has to act on.
Four checks, running on two different schedules, covering the four ways a client site quietly breaks: the domain lapses, the certificate stops renewing, a DNS record disappears, or outgoing email stops authenticating.
No signup. Real results in about four seconds.
Reads the registry directly over RDAP and warns 60, 30, 14, 7 and 1 day before a domain lapses — the one event a person with a payment card actually has to act on.
Doesn’t count down days. Tracks whether the renewal cycle is actually turning, and asks the certificate authority directly over ARI where it’s supported.
Snapshots A, AAAA, MX, NS, TXT, CNAME and CAA records every hour and flags what changed — including the vanished MX record that stops a client’s email while the site stays green.
SPF and DMARC checked daily alongside the rest of the DNS record set, treated with the same urgency as a vanished MX record when either one disappears.
DNS and reachability are checked every hour, because those break from one hour to the next. Domain expiry and certificates run once a day — they don’t change hourly, and judging a certificate rests on comparing two different days anyway.
This isn’t uptime monitoring running more often. It’s the same four checks, each on the schedule that actually matches how fast it can break.
Every check here works the same whether it’s watching one domain or four hundred — no per-site setup, no credentials, just a domain name added once.
For web agencies For freelancers The best domain expiry monitoring tools in 2026 Pricing