Best Domain Monitoring Tools in 2026: What They Actually Watch
Two completely different products share the name "domain monitoring". One watches whether your website responds. The other watches whether you still own the domain. Here is how to tell them apart and which tool fits which job.
September 21, 20268 min readMonitoring · Tools · Security
The Domain Hub checks every domain you add each day and tells you what changed and when it expires.
Open the Domain HubThe short answer. Most tools sold as "domain monitoring" are uptime monitors that check whether your site returns a 200, with a domain expiry field added later. Genuine domain monitoring watches the registry: expiry, status codes, nameservers, registrar and DNSSEC. If your domain is quietly transferred away, an uptime monitor will report everything is fine right up until it is not.
If you are comparing domain monitoring tools in 2026, the most useful thing you can do first is work out which of the two categories you are actually shopping in. Buying the wrong one is the most common and most expensive mistake in this market.
Domain monitoring vs uptime monitoring
Search for domain monitoring and you get two categories that look identical from the outside.
| Uptime monitoring | Domain monitoring | |
|---|---|---|
| Core question | Is the website responding? | Do I still control the domain? |
| Data source | HTTP requests to your site | Registry (RDAP), DNS, certificate transparency |
| Typical check | Every 1 to 5 minutes | Every few hours to daily |
| Catches | Outages, slow responses, broken pages | Expiry, hijacking, nameserver changes, lock removal |
| Misses | A domain expiring in 40 days | A 500 error on your checkout page |
Both are useful. They are not substitutes, and the failure modes they catch barely overlap.
The uncomfortable version: on the day someone moves your domain to another registrar, your uptime monitor keeps reporting 100% because DNS has not changed yet. By the time it notices, the domain is gone and getting it back is a dispute process, not a support ticket.
What real domain monitoring covers
This is the checklist we would hold any tool to, ours included.
Expiry, with enough warning. Not a 7-day alert. Domains enter a redemption period after expiry where recovery costs a redemption fee, typically far more than a renewal, and after that they drop entirely. Useful alerting starts at 90 days.
EPP status codes. Every domain carries status codes from the registry. The important one is clientTransferProhibited, the transfer lock. If it disappears from a domain you own and you did not remove it, that is the first step of a hijack. Very few tools watch this field.
Nameserver changes. A changed NS record is either you migrating hosts or somebody else taking control. Either way you want to know within hours.
Registrar changes. The domain moving between registrars, which should never happen without you initiating it.
DNS record changes. Specifically MX, because mail redirection is a quiet and extremely damaging attack, and TXT, because that is where SPF and DKIM live.
Certificate expiry. Less dramatic since Let's Encrypt automated renewal, but automation fails silently and a lapsed certificate blocks every visitor.
DNSSEC state. If it is enabled and breaks, your domain becomes unreachable for validating resolvers, which is a particularly confusing outage because it works fine from some networks.
The tools
Dedicated domain monitoring
axath Domain Hub monitors domains at the registry level. It runs scheduled RDAP and DNS refreshes and raises events for registrar changes, nameserver changes, certificate changes and expiry, and authoritative DNS inconsistency. It stores EPP status codes for every domain and tracks lifecycle state through expiry, redemption and pending delete, which is the part most tools skip. Pro covers 100 monitored domains and Scale covers 1,000, and bulk import means you can load an existing portfolio from a file rather than typing it in.
KIT.domains is built for agencies and MSPs holding client domains. It covers expiry across registrars, SSL, and DNS change detection on MX and NS records, with a centralised dashboard and team alerts.
Domain Sentry focuses on certificate expiry with a free tier, adding registration expiry on its paid plan. Narrow, but the narrow thing works.
Uptime monitors with domain features
This is where most search results land, so it is worth being precise about the trade.
Domain Monitor (domain-monitor.io) publishes its pricing clearly. The free plan is 2 monitors and 1 domain at 5-minute checks. The PRO plan is £7.99 per month and includes 75 monitors and 75 domains at 1-minute checks, with 15 SMS alerts and 3 status pages. Within that, 5 domain availability monitors and 5 blacklist monitors. So the domain-specific capability is a component of an uptime product rather than the product. For uptime with some domain awareness, that is good value.
Oh Dear combines uptime with domain and certificate tracking, broken link checking and scheduled task monitoring. Developer-focused and well regarded, and its certificate change detection with before-and-after comparison is genuinely useful now that CDNs rotate certificates automatically.
UptimeRobot has the most generous free tier in the category. Domain features are limited; treat it as an uptime tool that will also tell you a certificate is expiring.
Pulsetic, Site24x7, Uptime.com and Better Stack sit in the same bracket: strong uptime and incident tooling, domain expiry as a secondary field.
Enterprise observability
Datadog and similar platforms can monitor certificates and synthetic transactions as part of full-stack observability. If your company already runs Datadog, use its SSL tests rather than buying a separate tool. Nobody buys Datadog for domain monitoring.
Self-hosted and free
Uptime Kuma is open source and self-hosted, with HTTP, DNS and certificate checks. Free if your time is free. It will not watch registry status codes.
A calendar reminder is not a joke. If you own three domains with auto-renew on and a card that does not expire, a reminder 90 days out covers most of your real risk. Add a tool when the count or the stakes grow.
Choosing, in one pass
| If your situation is | Use |
|---|---|
| A handful of domains, one business | Auto-renew, a card that will not expire, and a 90-day calendar reminder |
| You need to know the site is down now | An uptime monitor: UptimeRobot, Oh Dear, Better Stack |
| You hold client domains across registrars | A dedicated domain monitor: KIT.domains, Domain Hub |
| A portfolio you have money in | Registry-level monitoring with status-code alerting |
| A brand worth defending from typosquatters | Enterprise brand protection, which is a different and much more expensive category |
| You already run Datadog | Datadog SSL tests |
The question that separates them
When you evaluate any tool in this space, ask one thing:
If someone removed the transfer lock on my domain tonight, would this tool tell me?
An uptime monitor cannot answer yes, because nothing it measures has changed. Your site is still up. DNS still resolves. The only place that event appears is the registry status codes, which means a tool has to be reading RDAP and diffing the result.
That single question sorts the category faster than any feature table, and it happens to be the exact moment when being told matters most. We wrote about why in Transfer Lock Removed: The Warning Sign Before a Domain Hijack.
If you want to see what registry data looks like for a domain you own, our checker shows the live RDAP record including status codes, and Domain Hub turns that into scheduled monitoring.
Common questions
What is domain monitoring?
Domain monitoring is the practice of watching a domain's registry record for changes you did not make: approaching expiry, altered nameservers, a changed registrar, removed transfer locks, or DNS records being rewritten. It is distinct from uptime monitoring, which only checks whether your website responds.
Is domain monitoring the same as uptime monitoring?
No. Uptime monitoring sends HTTP requests to your site and reports whether it responds. Domain monitoring queries the registry over RDAP and reports whether your ownership and configuration have changed. A domain can be stolen while uptime stays at 100%.
How often should domain records be checked?
Registry data changes slowly, so checks every few hours are sufficient for expiry and status codes. DNS and certificate checks benefit from being more frequent. Minute-level polling adds cost without adding much warning, because registry updates are not instant either.
How far in advance should expiry alerts fire?
At least 90 days. After a domain expires it enters a redemption period where recovery carries a redemption fee that is usually many times the renewal price, and after that it drops and anyone can register it. A 7-day warning is not enough time to resolve a billing problem.
Can I monitor domains for free?
Yes, for small numbers. Uptime Kuma is open source and self-hosted, several tools have free tiers covering one to ten domains, and auto-renew plus a calendar reminder covers the basic risk for a handful of names. Free tiers rarely include registry status-code monitoring.
What is the most important thing to monitor?
The transfer lock, clientTransferProhibited, on any domain that matters. Its removal is the step that precedes a transfer away, and it is the earliest signal available that someone is moving your domain.
Put the research to work.
Check your shortlist across the extensions that matter, then save the strongest names to a project.
Check a domain