Know the moment your DNS records change.
DNS changes are silent until customers cannot reach you. UptimeStatus snapshots six record types on every check and tells you exactly what changed.
DNS changes never announce themselves.
A teammate edits a record in the registrar console, an email migration rewrites MX, or worse, someone who is not you gets into the account. Either way nothing pages: resolution just quietly points somewhere new.
UptimeStatus snapshots six record types, A, AAAA, MX, TXT, NS, and CAA, on every check and diffs each one against the previous snapshot.
Changes are flagged. Hijacks are escalated.
Most DNS changes are routine, so a changed record opens an informational incident marked monitoring, with the previous and current values side by side. You confirm it was intentional and move on.
NS changes are different. A stolen or misconfigured domain usually shows up first as a nameserver change, so those open as investigating and get the seriousness of an outage.
What DNS monitoring includes.
- Six record types A, AAAA, MX, TXT, NS, and CAA records snapshotted on every check.
- Per-type diffing each record type is compared against its own previous snapshot, so one change never masks another.
- Before and after values every change incident stores the previous and current records, so you see exactly what moved.
- NS changes escalate nameserver changes open an investigating incident. Everything else stays informational.
- No false alarms for absent records a domain without AAAA or CAA records is simply skipped for that type, not flagged.
- Full snapshot history every check stores a snapshot, so you can pinpoint when a record changed, not just that it did.
One monitor per zone you care about.
A dns monitor takes a hostname or URL and starts building history on its next check. Add one alongside every production uptime monitor and record changes stop being archaeology.
Everything in the dashboard sits on the same API, so anything you can click, you can automate.
curl -X POST https://uptime-status.org/api/monitors \ -H 'Content-Type: application/json' \ -d '{ "name": "Primary zone", "url": "yourcompany.com", "type": "dns" }'
Open source, MIT licensed.
The DNS check is a small, readable job in the repo: resolve, snapshot, diff, done. Use the hosted version, or self-host the same code with no feature gates.
DNS monitoring, answered.
Why monitor DNS I control myself?
Because change comes from more places than you: teammates editing records, an email provider migration rewriting MX, a registrar console mistake, or in the worst case a compromised registrar account. The diff surfaces all of them the same way.
Is every DNS change treated as an outage?
No. A changed record opens an incident marked monitoring: informational, with the before and after values attached. Only NS changes open as investigating, because hijacked or misconfigured domains usually show up there first.
Which record types are covered? What about CNAME?
A, AAAA, MX, TXT, NS, and CAA. CNAMEs are followed during A and AAAA resolution, so retargeting a CNAME shows up as a change in the resolved addresses.
My provider rotates IPs. Will that spam me?
Hosts that rotate A records will produce change incidents, though they open as informational, not as outages. For endpoints behind rotating infrastructure, an uptime check is usually a better fit than record diffing.
How do I hear about a change?
Incidents notify through your configured channels: email, SMS, Slack, Discord, Microsoft Teams, PagerDuty, Opsgenie, Pushover, ntfy, or webhooks.
Pairs well with.
DNS blocklist monitoring
Checks whether your IPs appear on DNS blocklists, before deliverability problems become mysteries.
Learn moreDomain monitoring
WHOIS-based expiry warnings at 30, 14, 7, and 1 day, so a registration never lapses by accident.
Learn moreSSL monitoring
Certificate expiry countdowns, fingerprint change detection, and incidents when a handshake fails.
Learn moreStart monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.