Domain Monitoring
Your server is perfectly healthy and the site is still gone. Here's why.
The Outage That Isn't an Outage
Picture the worst version of this. Your
server is calm —
top is quiet, the disks have room, every
service is running — and yet the whole site has vanished for the rest of the world.
No one can reach you. The dashboard is green. You're staring at a healthy machine that
nobody on earth can find, and the only honest description is the most maddening one in
this whole business: “it's not down, it's just unreachable.”
That gap — between a server that's up and a site the world can actually reach — is where the domain lives. Someone edited a DNS record and fat-fingered an IP. A registration quietly lapsed because the renewal email went to an inbox nobody reads anymore. A nameserver change propagated halfway and then stalled. None of it touches the box at all. The server never noticed, because from the server's point of view nothing happened — and that's exactly why this class of outage is so good at hiding. Domain monitoring watches the part of your stack that lives outside the machine: that your domain still resolves, still points where it should, and hasn't quietly slipped out from under you.
Two Different Questions Most Tools Treat as One
“Is my server up?” and “can the world reach my site?” feel like the same question. They are not. The first is about a machine; the second is about a name, a chain of DNS lookups, and a registration that has to stay paid and unchanged. A box can be flawless on every metric and still be invisible because the name in front of it broke — and the failure leaves no trace on the server, which is precisely why it eats an afternoon.
The classic version costs real money and is almost embarrassingly avoidable: a domain expires. Not the TLS certificate — the domain registration itself. The renewal notice landed in an inbox someone left two jobs ago, and one morning the site is simply gone, the DNS stops resolving, and in the worst case the name is now sitting in a redemption window with a four-figure recovery fee on it. The server was healthy the entire time. It just had no name anyone could type.
The expiry that bites hardest isn't the certificate
Everyone learns to fear the expired SSL certificate — but a lapsed domain registration is worse, because there's no “renew in one click” once it's gone: the name can land in a redemption window, get auction-sniped, or cost a small fortune to recover. It is the one outage where the fix is don't let it happen, and the only defence is something quietly watching the calendar for you.
How CleverUptime Watches the Domain, Not Just the Box
This is the whole reason CleverUptime exists: we don't just flash a red light, we tell you the likely cause and the next move. When your site goes unreachable while the server is fine, that's the alert that usually leaves people lost — so it's exactly the one we refuse to leave at “site down.” We tell you whether the domain stopped resolving at all, whether it's resolving to the wrong place, or whether the registration is running out of road — and every alert links to a knowledge-base article that walks you through the fix, so the next time it happens you already know what to do.
Cause, not just symptom
“Site unreachable” is the start of the question, not the answer. CleverUptime separates the three real causes — the name doesn't resolve, the name points somewhere wrong, or the registration is about to lapse — because each one is a completely different fix, and knowing which it is is the work. The matching root-cause analysis turns the red light into a next step.
Auto-Provisioned From the Domains Your Server Already Serves
Here's the part people don't expect. You don't fill in a form listing your domains, and you certainly don't keep that list up to date by hand. You run one short, readable bash script on the server — short enough to read in a couple of minutes, and we explain every line, because you should never run code on your box you don't understand. The moment it checks in, CleverUptime sees which domains that machine is actually serving and provisions the right monitors automatically, with sensible settings already dialled in. No wizard, no “add your first domain” screen.
And it stays honest over time, which is the quietly clever bit: the list of domains worth watching is the list your server is genuinely serving right now — so when you add a vhost, the monitor appears, and you never end up paging yourself about a domain you decommissioned six months ago. The setup that makes most people abandon a monitoring tool on day one is the part we took off your plate entirely.
What It Actually Watches
Domain monitoring is the umbrella over everything between “the world types your name” and “the world reaches your box.” In practice that means:
- It still resolves — the name turns into an address at all, so the site doesn't silently fall off the internet while the server sits there perfectly fine.
- It resolves to the right place — the address it hands out is still yours, not a stale record left pointing at an old host or a fat-fingered edit nobody caught.
- The registration isn't running out — the domain's own expiry watched on the calendar, so a renewal that slipped through the cracks becomes a warning weeks early instead of an outage with a recovery fee.
- The world can reach it — the name resolves and the site answers behind it, the two halves of “is it actually up?” checked together rather than one at a time.
For the record-by-record layer underneath — the individual A, CNAME, MX and TXT entries, response times, and resolver drift — that's the DNS monitoring deep dive. Think of this page as the domain as a whole; DNS monitoring is what's inside it. And because an unreachable site is so often not a domain problem at all, it sits next to uptime monitoring, port monitoring, and SSL certificate monitoring — with root-cause analysis tying the whole picture together so you find out which layer broke, fast.
Healthy server, unreachable site — how long before you'd even notice?
CleverUptime watches your domain from the outside — that it still resolves, still points where it should, and isn't about to expire — and tells you which of those broke, in plain language, the moment it does.