DNS monitoring that notices what changed
DNS fails quietly. A record edited by mistake, a hijacked nameserver, an expired zone — your servers stay perfectly healthy while nobody can reach them, and mail silently stops arriving. Most teams find out from a customer.
Moonitor's DNS monitoring resolves your records around the clock, compares answers against what you expect, and alerts on unexpected changes — for A, AAAA, CNAME, MX, TXT and NS records.
7-day free trial — no credit card.
How it works
Pick a record to watch
Point a DNS monitor at any hostname and choose the record type — A, AAAA, CNAME, MX, TXT or NS.
Set the expected answer
Pin the values a record must return, or simply enable change alerts to be told whenever the answer differs from the last one seen.
We resolve continuously
Records are re-resolved around the clock, so a bad change made at 2am is an alert at 2am, not a Monday-morning surprise.
Get alerted on drift
An unexpected answer or a failed resolution opens an incident and notifies you by email, Slack, Discord, Telegram or webhooks.
What you get
Six record types
A, AAAA, CNAME, MX, TXT and NS — web, mail and delegation covered by the same monitor type.
Change detection
Alert whenever a record's answer changes, even if you didn't pin an expected value — the fastest way to catch unauthorised edits.
Expected-value pinning
Assert exactly what a record should return and treat anything else as a failure, ideal for SPF/DKIM TXT records and apex A records.
Second-country verification
A weird answer from one resolver isn't an incident; Moonitor reproduces the failure from another country before alerting you.
Full incident history
Every change and outage is recorded with timestamps, so you can reconstruct what DNS looked like when.
Alerts + API
Route DNS alerts anywhere, and manage DNS monitors programmatically through the REST API.
Frequently asked questions
- What DNS record types can Moonitor watch?
- A, AAAA, CNAME, MX, TXT and NS records. Each monitor watches one hostname and record type, and can pin expected values or alert on any change.
- Can it detect DNS hijacking?
- Yes — change alerts fire whenever a record's answer differs from what was seen before, which is exactly the signature of a hijacked or mistakenly edited record.
- How fast will I know about a DNS change?
- Monitors re-resolve records continuously on your configured interval (down to every 30 seconds on Team and Max plans), so changes are caught within minutes at most.
- Does a resolver glitch cause a false alarm?
- No. Failures are re-verified from a second vantage point in another country before an incident opens, so one resolver's bad day doesn't page you.
Every failure verified before you’re alerted
Moonitor re-runs every failing check from a second country before opening an incident — so a network wobble near one checker never becomes a false alarm on your phone. Explore the full feature set, read the docs, or automate it all with the API.
Get started