Domain Health: domain, DNS and email under control

A site can respond perfectly, with its SSL certificate in order, and still have a problem brewing that HTTP monitoring never sees: a domain approaching expiry, a nameserver changed without anyone authorizing it, an email landing in spam because an authentication record is missing. These are problems that start outside the site itself, often in a registrar's or DNS provider's panel that almost nobody checks again after the initial setup.

A separate cron, at a different pace

These checks run on a cycle separate from HTTP/TCP/ICMP monitoring, much slower: there's no point querying a DNS registry or a registrar every minute for data that, at best, changes a few times a year. The same respect toward the services we query that we apply to HTTP monitoring applies here too, adapted to a naturally slower pace.

Why an unannounced change matters

A nameserver that changes on its own, without you requesting it, is almost always a sign of unauthorized access to the registrar panel: whoever controls a domain's nameservers can redirect traffic, intercept mail, issue certificates in their own name. It's one of the most serious scenarios for a domain, and also one of the quietest: the site can keep responding normally for days before anyone notices through another signal.

Turned on per monitor

Each check is a checkbox, per monitor: you can track the main domain's expiry without also enabling the blacklist check on a secondary subdomain, for example. The dates and states found stay visible only in the authenticated panel, never on a public status page: an approaching expiry isn't information to show to an outside viewer.

Self-service or assisted setup

If you'd rather not deal with it, we can set up the right checks for your domains together as part of the assisted setup.