DNS Monitoring · All Plans

DNS Monitoring That Catches Every Record Change

Your DNS decides where your traffic and your email go. DNS Spy checks every record on every authoritative nameserver, from several regions, and tells you the moment one changes: what it was, what it is now, and which nameserver served it.

Free scan, no signup · Nothing to install · 7-day trial

What Is DNS Monitoring?

DNS monitoring is the continuous checking of a domain's DNS records from the outside, the way the rest of the internet sees them. A DNS monitoring tool queries your nameservers on a schedule, compares each answer with the last one, and alerts you when a record changes, disappears, or is answered differently by different nameservers.

It exists because DNS fails silently. A changed record takes effect everywhere at once without touching a single one of your servers, and whatever it now points to usually still responds. Uptime checks stay green. The first sign is a customer asking why the login page looks different, or a week of missing email.

The term covers two different jobs. Performance monitoring measures how quickly and reliably DNS answers, and is usually part of a network monitoring suite. Change and integrity monitoring watches whether the answers are still the right ones. DNS Spy does the second: it is DNS monitoring software built to notice that a record is no longer what you published.

What DNS Monitoring Should Watch

A single "does this hostname resolve" check covers very little. These are the six things that actually change.

What Goes Wrong Without It

Each of these happens to real teams, and none of them raises an uptime alert until the damage is done.

A record changes and nobody made the change

A compromised registrar or DNS provider login, a leaked API token, or an insider. The attacker repoints an A or MX record, collects traffic or mail, and often puts it back. Uptime checks stay green the whole time because something is still answering.

A migration leaves records behind

Moving DNS providers means recreating every record by hand or by import. The verification TXT record, the forgotten subdomain and the second MX are the ones that get missed, and they fail quietly days later.

A CNAME outlives the service it points to

The marketing site moves, the old hosting account is closed, and the CNAME stays. Anyone who claims that hostname at the provider now serves content on your domain. This is a dangling DNS record, and it is how subdomain takeovers happen.

One nameserver serves an old zone

A secondary stops receiving updates. Most lookups get the new answer and some get last month's. The symptom is "it works for me", which is the hardest kind of outage to investigate.

Email authentication breaks in passing

Someone edits the SPF record to add a sender and pushes it over the lookup limit, or removes a DKIM key during cleanup. Mail keeps sending. It just stops arriving.

The domain itself lapses or is put on hold

An expired card at the registrar, or a status change such as clientHold, removes the domain from DNS entirely. Every record is still correct in the zone, and none of it resolves.

Related reading: what dangling DNS is and how to find it, and how DNS fits into wider domain monitoring.

How DNS Spy Monitors Your DNS

Step 1

Add a domain

Type the name. There is nothing to install and no change to your nameservers or your DNS provider.

Step 2

DNS Spy builds the record list

Autodiscovery probes hundreds of common hostnames, a zone transfer pulls everything where it is allowed, and a read-only connection to your DNS provider imports the complete zone.

Step 3

Every nameserver is asked, repeatedly

Each record is checked against each authoritative nameserver from query nodes in several regions, at least every ten minutes, so the answer is what the world sees and not what one resolver cached.

Step 4

You are told what changed

An alert shows the record, the old value, the new value and which nameserver served it, by email, Slack, Discord, PagerDuty, webhook or syslog. Every version is kept in the record's history.

The read-only connection works with nine DNS providers, including Cloudflare, Amazon Route 53, GoDaddy and UltraDNS. It is optional: monitoring starts from public DNS alone.

How to Choose a DNS Monitoring Tool

DNS monitoring tools, software and services differ more than their feature lists suggest. Six questions separate them.

Does it find records, or only check the ones you list?

Many monitors verify that one hostname resolves to one expected value. That confirms what you already know. The record you forgot exists is the one that gets hijacked.

Does it query the authoritative nameservers?

A public resolver returns a cached answer and hides disagreement between your nameservers. Only asking each authoritative server shows what is actually published.

Does it keep history?

When something breaks, the first question is what the record was yesterday. A tool that only knows the current value cannot answer it.

Does it tell change from noise?

Load balancers and CDNs rotate addresses constantly. A monitor that alerts on every rotation gets muted within a week.

Is it measuring performance or integrity?

Network monitoring suites measure how fast DNS answers. That matters for large networks, and it is a different job from knowing whether the answer is still the right one.

How is it priced?

Per-check pricing punishes thorough monitoring, because every record on every nameserver is a check. Pricing by domain lets you watch everything.

For a tool-by-tool view, see our comparison of eleven DNS monitoring tools, sorted by what each one actually monitors.

See What DNS Monitoring Finds on Your Domain

The free scan checks your records on every authoritative nameserver, pulls your certificates, runs 50 security checks and grades the result. It takes about a minute and needs no account.

Run the Free Scan

Frequently Asked Questions

DNS monitoring is the continuous checking of a domain's DNS records from the outside, the way the rest of the internet sees them. A DNS monitoring tool queries your nameservers on a schedule, compares the answers with what they were before, and alerts you when a record changes, disappears, or is served differently by different nameservers.

DNS decides where your website traffic and your email go, and a change to it takes effect everywhere without touching any of your servers. Unauthorized changes, migration mistakes and expired records do not trigger uptime alerts, because something usually still answers. DNS monitoring is the control that notices the answer is no longer yours.

Uptime monitoring asks whether a site responds. DNS monitoring asks whether the records that send people to that site are still correct. A hijacked record often points at a server that responds perfectly well, so an uptime monitor reports no problem while visitors are sent somewhere else.

Often enough that a change is caught before its effects spread. DNS Spy re-checks every monitored domain at least every ten minutes against every authoritative nameserver, which is shorter than the cache lifetime of most records.

No. DNS Spy monitors by querying public DNS, so there is nothing to install and nothing to change. Connecting your DNS provider is optional and read-only. It imports the full record list so that records which cannot be discovered from the outside are monitored too.

All of the common ones, including A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA and PTR, as well as DNSSEC records such as DS and DNSKEY. Records are compared value for value on each authoritative nameserver.

The free scan checks any domain once, with no account: its records on every authoritative nameserver, its certificates, and 50 security checks. Continuous monitoring with alerts is a paid plan with a 7-day free trial. The free DNS tools, including the propagation checker and nameserver lookup, are always free.

Know When Your DNS Changes

Every record, every nameserver, with history and alerts where your team already works. Priced by domain, not by check. Free for 7 days.