Domain monitoring, explained

A domain is five separate systems, and each one fails on its own.

Registration, DNS, the certificate, mail authentication, and the site. They have different owners, different expiry dates and different failure modes, and none of them sends you a message when it goes wrong. Domain monitoring is reading all five on a schedule and keeping the previous answer so a change is visible.

The checkup asks you to create a free account before it shows the report. No card, and the account keeps your results so the next scan is a comparison rather than a fresh opinion.

The five layers

What each layer is, and what it looks like when it breaks.

The symptom column is the useful one. Most of these arrive at your desk as the same sentence — “the website is down” — and the layer they came from is what decides who can fix it.

Registration

What it does
Your right to use the name at all. Held at a registrar, recorded at the registry.
How it fails
The registration lapses, a transfer is approved, or the registrar lock comes off.
What you see
Website and email stop together, at the same second, for no reason anyone can find.
Where the truth lives
The registry's RDAP record — expiry date, registrar, status codes.

DNS

What it does
Turning the name into an address, and pointing mail at a mail host.
How it fails
A record is edited, a nameserver is changed, or a zone is moved and half the records do not come with it.
What you see
Some people reach the site and some do not, or mail from one provider starts bouncing.
Where the truth lives
The authoritative nameservers, queried directly and compared to the last answer.

The TLS certificate

What it does
The padlock. Proof the server answering is the one the name points at.
How it fails
It expires, or an automated renewal quietly stopped working weeks ago.
What you see
Every browser shows a full-page warning. Nothing is broken except trust.
Where the truth lives
The certificate the server presents, plus the public Certificate Transparency logs.

Mail authentication

What it does
Whether receiving servers believe mail claiming to be from you.
How it fails
SPF drifts out of date, a DKIM key is rotated on one side only, DMARC is never published.
What you see
Your invoices land in spam, and someone else's fake ones land in the inbox.
Where the truth lives
The SPF, DKIM, DMARC, MX and MTA-STS records, and the DMARC reports mailbox providers send back.

The site itself

What it does
What a visitor gets, and what an attacker can see from outside.
How it fails
A plugin goes out of date, a .env file becomes reachable, a header gets dropped in a deploy.
What you see
Usually nothing at all, until it matters.
Where the truth lives
The HTTP response, the security headers, the software versions the page discloses.

Why nobody notices

Every one of these failures is quiet by design.

The warnings go to an address nobody reads

ICANN's Expired Registration Recovery Policy makes registrars send renewal reminders roughly a month out and again about a week out. They go to the registrant email on the registration record. On a domain bought six years ago, that is often a person who has left, a mailbox that now bounces, or a privacy-service forwarder pointed at the same place.

Nothing tells you a renewal did not happen

Auto-renew is a charge attempt, not a guarantee. A card expires, a bank declines an unfamiliar merchant, the domain sits in an account whose payment method was never updated. The registrar records a failed charge. Nobody on your side sees a failure — they see the absence of a receipt, which looks identical to not looking.

DNS changes are made by people who do not tell you

A marketing agency points a subdomain at a landing page tool. An email vendor asks for a new TXT record and the old one gets replaced instead of added. Both are ordinary work. Neither generates a notification, and the SPF record that broke will not be noticed until a customer says they never got the quote.

Certificates renew until the day they do not

Let's Encrypt certificates last 90 days, so the renewal is automated and invisible. When the automation breaks, whether from a moved webroot, a changed firewall rule or an expired API token, nothing is different for weeks. Then every visitor gets an interstitial at once.

What it is not

Four things domain monitoring gets confused with.

It is the same as uptime monitoring
Uptime monitoring answers one question: did the server respond. A domain can respond perfectly while its certificate has 6 days left, its SPF record is broken, and its registration expires next month.
It protects the site
Monitoring watches and reports. It is not a firewall, a WAF, a backup, or malware removal. It shortens the time between something changing and you knowing, and that is all it does.
It needs software on your server
Almost none of it does. Registration, DNS, certificate and mail-authentication data are public records. A scan reads what any visitor or any mail server can already see.
It is a one-time audit
An audit tells you the state on a Tuesday. Monitoring is the same checks on a schedule, with the previous answer kept, so the alert is about what changed rather than what is.

How DomainGuard does it

The same five layers, on a schedule, with the last answer kept.

Free account

Unlimited domains, checked whenever you press scan, with every result kept so the next one is a comparison. Dark-web breach checks and alerts when a vulnerability is published for software found on your sites run automatically. Nothing else scans on its own.

Paid plans

25 domains on Starter, 100 on Pro, unlimited on Enterprise, re-checked daily without being asked. That is where the alerts live: an expiring certificate, a changed DNS record, a site that stopped answering, a DMARC report showing a sender you do not recognize.

Where it runs

A web dashboard and an iPhone app, same account and same data. The iPhone app is in public beta on TestFlight while we finish it. There is no Android app, and the web dashboard is dark theme only.

Questions people actually ask

What is domain monitoring, in one sentence?

Re-reading the public records a domain depends on, meaning registration, DNS, certificate, mail authentication and the HTTP response, on a schedule, keeping each answer, and telling you when one of them changes or is about to expire.

How is it different from uptime monitoring?

Uptime monitoring asks whether the server answered. Domain monitoring asks whether the name will still be yours next month, whether the certificate will still be valid next week, and whether anyone can send mail pretending to be you. A site can be up and failing all three.

Do I need to install anything?

No. The data is public: the registry's RDAP record, the authoritative DNS answers, the certificate the server presents, the Certificate Transparency logs, and the HTTP response headers. Nothing is installed and nothing logs in to your site.

How often should the checks run?

Daily is enough for registration and certificate expiry, because both fail on a known date. DNS and mail authentication are worth checking daily too, since a change is silent. Uptime is the only one that needs minutes rather than days.

What does DomainGuard cost?

The account is free and holds unlimited domains, checked whenever you press scan. What a paid plan buys is domains watched without being asked: 25 on Starter at $6.99 a month, 100 on Pro, unlimited on Enterprise, plus DMARC report processing and SEO scans. Plans are bought through Apple in-app purchase.