Alerted the moment your DNS shouldn't have changed.
Continuous DNS record monitoring with email + webhook alerts. Watch A, AAAA, MX, NS, TXT, or CNAME records. AS-aware fingerprinting tolerates anycast IP rotation while catching real DNS changes, the kind that mean a hijacked domain or a botched zone update.
What we watch.
A & AAAA records
IPv4 and IPv6 records. Fingerprinted by the network that announces them (not the raw IP), so anycast rotation doesn't false-alert.
NS records
Watch the NS record set. A change is often the first sign of an unauthorised registrar or DNS provider change.
MX records
Mail server changes. Catches when mailflow is silently rerouted.
TXT records
SPF, DKIM, DMARC, domain-verification records. Catches subtle edits that break email delivery or add a verification record you didn't expect.
Configurable resolvers
Default is Cloudflare DoH. Override per monitor if you want to watch what Google or Quad9 returns instead.
Resolver-failure tolerant
Failed queries are retried once, and 0-record answers on a non-empty baseline count as lookup errors, not drift. A resolver hiccup never reads as a DNS change or overwrites your baseline.
What this catches.
Dangling records
A CNAME still points at a cloud resource you deprovisioned. Watching what the name resolves to shows when that target stops answering, the warning sign that the name is open to a subdomain takeover.
Registrar compromise
If someone takes over your registrar account, the first sign is usually an NS-record change. The monitor flags it on the first check after the change reaches public resolvers.
Botched zone updates
An infra change goes wrong, the zone file has a typo, mailflow breaks. DNS drift catches it the moment propagation completes.
Common questions.
Why DNS monitoring?
Unauthorised DNS changes are how domains get hijacked. They're also how a botched zone-file update takes your mail down for 4 hours. Either way you want to know within minutes, not when a customer reports it. The monitor captures a baseline on first run, then compares every subsequent check against it.
What's 'AS-aware fingerprinting' and why does it matter?
Anycast and CDN-hosted domains (Google, Cloudflare, the big CDNs) legitimately return different IPs from one query to the next, all announced by the same network. Naive DNS monitors flag every rotation as drift. Ours fingerprints A and AAAA records by the network that announces them (the organisation behind the autonomous system, or AS) rather than the raw IP, so rotation inside the same provider is ignored, even when that provider answers from several AS numbers. If the records move to a different provider (say, a domain migrated from Google to AWS), the fingerprint changes and you get a real alert. If the AS lookup is unavailable, IPs already in your baseline keep their known owner, and any IP whose owner can't be determined marks the check as an error instead of being compared, so a lookup outage never looks like drift.
Which record types are supported?
A, AAAA, MX, TXT, CNAME and NS. You configure which types to watch per monitor; the default is A. NS and MX are good for detecting delegation or mail-server changes; TXT catches SPF / DKIM / verification record edits.
What happens if my upstream resolver is having a bad day?
A record type whose query fails is retried once straight away. If it still fails, or a check returns 0 records when the baseline had records, we record state=error (a lookup problem), not state=critical (real drift), and leave the baseline alone. A resolver outage can send you an error notice, but never a false drift alert, and your baseline is intact when the resolver recovers.
Can I update the baseline if I intentionally change DNS?
Yes. Delete the monitor and re-create against the same hostname; the first check captures a fresh baseline from the new state.