Continuous WHOIS-based domain expiry monitoring with email + webhook alerts before renewal. Auto-renewal isn't a guarantee — payment methods expire, registrant emails bounce, ICANN compliance locks happen. The day after expiry is the day someone else can register it.
We follow the registry referral chain (verisign → markmonitor etc.) so we catch the authoritative expiry date, not just whichever hop returns first.
Default 30 days warning, 7 days critical. Configurable per monitor — bump warning to 60+ days if your renewal needs lead time.
Weekly checks. WHOIS data is stable; daily would be wasteful and risk WHOIS rate-limiting from registries.
Email goes to your account address. Webhook posts JSON to Slack / Discord / PagerDuty / your endpoint.
Renewed your domain? You get a 'recovered' alert when the monitor sees the new expiry date — confirms the renewal landed.
Each check records the registrar name. Catches the rare but real case of an unauthorised registrar transfer.
Domain expiry stories are evergreen industry horror content — and they almost always come down to the same five failure modes. Any one of them gets caught by a working expiry monitor.
Card on file at the registrar expired. Auto-renewal silently failed. Renewal-reminder emails went to a mailbox nobody reads.
ICANN requires an active contact email. Yours stopped working when an employee left. The registrar locks the domain until you re-verify.
Some ccTLDs and premium domains can't auto-renew. They sit at the registrar waiting for a human to log in and click. The human is on holiday.
Someone got into your registrar account, changed the contact email and let the domain expire so they could grab it. The first sign is the expiry date moving without your action.
WHOIS data flagged as inaccurate. ICANN requires re-verification. Domain locked until you fix it. Clock keeps ticking toward expiry.
Registered three years ago when you were 'about to launch.' Card expired since. Nobody's watching.
Auto-renewal at the registrar isn't a guarantee. Payment methods expire, registrant emails bounce, ICANN compliance issues lock the domain, the credit card on file gets declined silently. The day after your domain expires is the day someone else can register it. Monitoring is the only way to know in time.
Anything with a WHOIS or RDAP record that exposes an expiry date — which is nearly every gTLD (.com, .net, .org, .io, .dev, .app, all the usual SaaS TLDs) and most ccTLDs. .de famously doesn't return expiry data; we'll surface that as an error so you know to track that one elsewhere.
Weekly. WHOIS data changes infrequently, and most registries rate-limit aggressive WHOIS queries — daily would be wasteful at best, blocked at worst. Weekly catches the relevant change window (30 days warning by default) with plenty of headroom.
Default is 30 days warning, 7 days critical. For domains that you control with auto-renewal enabled, those defaults are fine. For domains where renewal involves a manual process (legal review, finance approval, registrar account transfer), bump warning to 60 or 90 days.
Yes. The free tier's 3 monitors cover the essentials at no cost, and the 15-monitor Starter plan ($9/mo) covers the typical engineer's whole personal portfolio — main domain, side project, blog, GitHub Pages alt-domain, the one you registered at 2am five years ago and forgot about.
