How does Lemwatch detect DNS record changes?

Lemwatch resolves your A, AAAA, MX, NS, CNAME, and TXT records on every check and hashes them — any hash change triggers a DNS change incident.

Quick answer

Every scheduled check resolves A, AAAA, MX, NS, CNAME, and TXT records, sorts them, and stores a hash. When the hash changes we log the diff and open a DNS change incident.

Why this matters

Where to find it in Lemwatch

Site → DNS — history + latest snapshot.

FAQ

Do you check all resolvers?

We query multiple resolvers (Google + Cloudflare) and flag disagreements.

Related