Domain expiration monitoring watches a single date: when your registrar contract runs out. Not the SSL certificate (that's a different clock), not DNS resolution, not whether the site is up. Just the registration itself. WatchCron queries WHOIS directly, twice a day, for every domain you add, and alerts you when the expiry date gets close enough to worry about. Domain monitors are counted separately from checks: 5 on Free, 20 on Starter, 100 on Pro, unlimited on Business.
01 — Nobody owns the renewal calendar#
Domains pile up. A company registers the .com and the .io, the country variants, a couple of campaign domains, the obvious typo bought defensively, and they end up spread across Cloudflare, Namecheap, and GoDaddy depending on what was cheapest that year. Each registrar emails its own renewal notice to whatever address registered the domain: sometimes a shared inbox nobody reads, sometimes someone who left two years ago. No single place shows every domain and the day it expires. That's how a domain goes quiet that nobody meant to drop.
WatchCron puts them all in one list: expiry date, days left, and registrar side by side, so the .com with three weeks on it isn't hiding behind the dozen that are fine.

02 — What you'd see if you checked yourself#
Any domain can be checked from a terminal:
$ whois example.com | grep -i "expir"
Registry Expiry Date: 2027-08-13T04:00:00Z
One line, one date. That's enough. The problem is the same as with SSL certificates: you'd have to remember to run it, for every domain, on a schedule. And the domain that lapses is always the one nobody remembered to check.
Registrars send renewal reminders, but trusting them entirely is a bet you'll eventually lose. GoDaddy sends to the domain's contact email, which may be outdated. Cloudflare reminds you 30 days out. Others give you 60. Some have auto-renew on, but the card attached expired six months ago. Third-party monitoring removes that dependency on someone else's notification chain.
03 — Straight from WHOIS, no middleman#
To find an expiry date, WatchCron queries WHOIS directly. It opens a connection to the registry's WHOIS server on port 43 and reads the response itself, with no third-party lookup service in between. The list of domains you care about isn't being handed off to someone else's API. From the response it pulls the expiry date and the registrar, and it keeps the full raw WHOIS record (up to ten thousand characters), so you can read exactly what the registry returned rather than trusting a parsed summary.
Paste a domain however you have it: with https://, a www, or a trailing path. It gets trimmed to the bare domain before the lookup runs.

04 — Five states and two alerts that matter#
A domain monitor sits in one of five states:

State | When | How it reads |
|---|---|---|
OK | More days left than your warning window | Green |
Expiring Soon | Inside the warning window | Amber |
Expired | Past the expiry date | Red |
Error | The WHOIS lookup failed | Red |
Unknown | Not checked yet, or the response couldn't be parsed | Grey |
The line between OK and Expiring Soon is a warning window you set: anywhere from 1 to 365 days, defaulting to 30. A policy of "renew ninety days out" is a single number.
Two separate alerts fire on the way down: one the moment a domain crosses into Expiring Soon, another if it actually expires. Each goes through the channels that monitor uses. Free includes 3 channels (pick from email, Slack, Telegram, webhooks, or any other supported type); Starter raises that to 10, Pro to 25, Business removes the cap. SMS opens on Pro, voice calls and WhatsApp on Business.
05 — What teams actually track#
The most common case: an agency with 20-50 client domains scattered across 3-4 registrars. One list in WatchCron replaces checking each registrar separately. When a client's domain crosses into Expiring Soon, the alert goes to the right account manager through a separate project with per-client channels.
Companies with defensive registrations: typo domains, country variants, old brands. These often get forgotten because they don't point at any live site. They never show up in uptime monitoring. The only way to know exanple.com is expiring is a dedicated check.
E-commerce, where the domain is the brand: losing yourstore.com means losing the business. Auto-renew is usually on, but the credit card is tied to a finance director who left last quarter. Third-party monitoring catches that gap.
Startups after a pivot: the old domain still takes traffic from backlinks, but it's registered under a departed founder's email. Nobody remembers the registrar password. Doesn't matter while monitoring says 200 days left. Starts to matter at 5.
06 — Where the check stops#
The check answers one question: when does the registration expire. It reads the date and the registrar, and deliberately stops there.
It won't tell you a domain has been put on clientHold or slipped into a redemption period. It doesn't track nameserver changes or ownership transfers. It keeps only the latest result, no history, no trend charts.
Lookups run twice a day on a fixed schedule you can't change, though a Check Now button forces an immediate one. A large portfolio can bump into a WHOIS server's own rate limits. A few exotic country-code TLDs publish formats the parser doesn't recognise, which surface as Unknown rather than a confidently wrong date.
One expectation worth setting: each alert fires once on the status change, with no daily reminder and no acknowledge button. The first notification is the one that counts.
Domain expiry is one of three clocks that tick silently on separate calendars. The certificate is SSL monitoring's job. DNS records are a check inside network monitoring. The registration itself is this. Any one of them lapsing can take you offline, which is the argument for watching all three.
Track every domain from one list and get warned with weeks to spare, straight from WHOIS. Free plan: 5 domain monitors, 3 alert channels, no credit card.07 — Add your first domain#
Paste a domain and the WHOIS lookup runs automatically. See what each plan includes on the pricing page, or create an account and start the countdown working for you. You can check any domain's expiry date right now with our free WHOIS tool.
08 — FAQFrequently asked#
They're two separate clocks on the same domain. SSL monitoring watches the certificate's expiry; domain monitoring watches the registration's expiry. A domain can serve a perfectly valid certificate and still lapse at the registrar, and a renewed domain can still carry a dying certificate, so the two run independently.
It queries WHOIS directly over port 43 and reads the registry's response itself, with no third-party API. It parses out the expiry date and registrar and stores the full raw record so you can inspect exactly what came back.
You set the window from 1 to 365 days, with 30 as the default. It sends one alert when a domain enters that window, and a second one if it actually expires.
Twice a day, at fixed times, and you can force an immediate lookup with Check Now. The interval itself isn't user-configurable.
Common gTLDs and many country-code domains are parsed directly, with a fallback for the rest. A few exotic ccTLDs with unusual WHOIS formats may come back as Unknown rather than a parsed date.