Free plan: 3 domains, 15 active monitors and 1 member per organization. Minimum check interval: 60 minutes. All Free plan limits
INTERACTIVE DEMO · 1/4SIMULATED DATA
example.test AHealthy
DNS provider Configured zone192.0.2.40
Zone provisioning ↓
Authoritative NS Published answer192.0.2.40
DNS queries ↑ · answers ↓
Resolver A Refreshed cache192.0.2.40
Resolver B Cached answer192.0.2.40
Root/TLD delegation omitted. Provider provisioning is separate from DNS queries.
DNStracr compares snapshots.Not in the DNS query path.
Every source agrees.
The zone, authoritative servers and both resolver caches return 192.0.2.40.
One resolver still has the old answer.
The zone and authoritative answer changed. Resolver B keeps its cached answer until its TTL expires. No incident confirmed yet.
Repeated disagreement confirms an incident.
Three simulated hourly checks failed the agreement rule. This example does not predict real detection time.
The cached answer caught up.
Both resolvers now return 192.0.2.41. Two simulated passing checks confirm recovery.
Timeline & demo rules
Answers agree
Change; first failed checkNot reached in this simulation.
Third failure; incident confirmedNot reached in this simulation.
Second pass; recovery confirmedNot reached in this simulation.
Example rule: all answers must agree. Checks 1 hour apart; incident after 3 failures, recovery after 2 passes. Times are illustrative, not elapsed time.
Root/TLD delegation omitted. Provider provisioning is separate from DNS queries.
No live DNS queries. This demo does not create monitors or incidents.
ONE DOMAIN. MULTIPLE SOURCES.Authoritative DNSRecursive resolversDNS over HTTPSProvider comparisons
INSIDE DNStracr
See what changed. Know what recovered.
Follow the same example through domain health, DNS answers and recovery. Open any screenshot for a closer look. All data is fictional.
01 / Check domain health
Dashboard
See which domains are healthy and where monitoring is missing.
02 / Compare DNS sources
Monitor detail
Compare the configured record with answers from nameservers, recursive resolvers and DNS over HTTPS.
03 / Follow change and recovery
Domain history
Trace the confirmed DNS change and see when recovery was confirmed.
LESS GUESSWORK. MORE CONTEXT.
DNS monitoring for the work you do.
01 / DevOps & SRE
Separate resolver differences from DNS incidents.
Investigate DNS after a deployment or Cloudflare change. Compare configured records with observed answers, and allow expected CDN or GeoDNS differences while keeping missing records and query failures visible.
Review changes to MX, SPF, DKIM and DMARC during a mail-provider move or policy update. Follow failed checks and confirmed recovery. DNS checks do not test actual email delivery.
Organize client domains with tags, review monitored resources and compare before-and-after answers. Use the change and incident history to see what changed and when recovery was confirmed.
DNStracr compares DNS answers from authoritative nameservers, recursive resolvers and DNS over HTTPS. It tracks record changes, checks configured expectations and follows confirmed incidents through recovery.
Why can DNS resolvers return different answers?
DNS caching, CDN routing and GeoDNS can produce different answers. DNStracr lets you configure expected resolver variation while keeping missing records, query failures and unexpected authoritative differences visible.
Can I investigate DNS changes and email records?
A domain or record timeline brings DNS changes and incidents together. Mail analysis helps you inspect MX, SPF, DKIM and DMARC records, alongside DNSSEC evidence. Raw-check retention is shown separately from retained changes and incidents.
How do I get started for free?
Create a free account and verify your email. The free DNS scan needs no account.
FREE PLAN
Start monitoring your DNS
Create a free account to add your domain and track DNS changes over time.