DNS monitoring for MSPs
Manage hundreds of client domains from one dashboard. Get instant alerts when DNS records change, before your clients notice.
Start Your Free 7-Day TrialCredit card required to start. You won't be charged for 7 days, and you can cancel anytime.
Domains
Viewing 8 of 142 domains
| Security | Domain | Synced |
|---|---|---|
| A (97%) | clientone.com | In sync |
| A (94%) | acmecorp.net | In sync |
| C (71%) | techfirm.io | Out of sync |
| A (92%) | retailco.com | In sync |
| B (88%) | healthgroup.org | In sync |
| B (84%) | devstudio.co | In sync |
| A (95%) | acmecorp-mail.com | In sync |
| B (81%) | shop.retailco.com | In sync |
By the time you notice, it's already broken and your clients are calling you.
A compromised DNS record can redirect websites, intercept email, and get SSL certificates issued to someone else, often without triggering a single security alert.
Without DNS change history, troubleshooting is guesswork. You need a timeline, not a mystery.
With control of your DNS, a malicious actor can redirect your website complete with valid SSL certs, or quietly update your MX records to deliver your email to another host and relay it back to you without you knowing. DNS Spy gives you the instant visibility to catch it before it becomes a breach.
From: DNS Spy <alerts@dnsspy.io>
Subject: DNS Spy: Record changed for acmecorp.net
A record changed on acmecorp.net
Why it matters
Website traffic for acmecorp.net now goes to a different server. If nobody on your team made this change, treat it as a possible hijack.
acmecorp.net · Record history
Last 365 days · 5 changes
| When (UTC) | Record | Old value | New value |
|---|---|---|---|
| Oct 6, 09:42 | A @ | 104.21.45.12 | 198.51.100.44 |
| Sep 28, 16:05 | MX @ | 10 mail.acmecorp.net | 10 acmecorp-net.mail.protection.outlook.com |
| Sep 28, 15:58 | TXT @ | v=spf1 mx ~all | v=spf1 include:spf.protection.outlook.com -all |
| Sep 14, 11:20 | CNAME www | acmecorp.net | acmecorp.azureedge.net |
| Aug 30, 08:03 | TXT _dmarc | v=DMARC1; p=none | v=DMARC1; p=quarantine |
“With control of your DNS, a malicious actor can with ease re-direct your website complete with valid SSL certs for your domain, or quietly update your MX records to deliver your email to another host and then relay back to you without you knowing… Adding DNS Spy to our toolset, provides that additional peace of mind.”
Keith Gatt
Technical Consultant, GOV Architects
A UK zero-trust security consultancy
Start free for 7 days. Credit card required but not charged until your trial ends.
$9 /month
Most Popular for MSPs
$49 /month
7-day money back guarantee. Cancel anytime. No contracts. Prices in USD.
No. DNS Spy monitors public DNS records by querying your authoritative nameservers directly. No credentials or DNS provider access are needed. Connecting a DNS provider such as Cloudflare or Route 53 is optional and only speeds up importing domains.
Yes. DNS Spy is built for MSPs: monitor hundreds of client domains from one account and organize them by client with Domain Groups. Enterprise includes 100 domains and grows in 50-domain packs.
You choose the plan to trial, Enterprise or Personal, and get full access to it for 7 days. A credit card is required to start, but you are not charged until the trial ends. Cancel from Billing before then and you owe nothing. We email you two days before the first charge.
Every plan alerts by email. Enterprise adds Slack, Discord, PagerDuty, SIEM webhooks and syslog, plus full API access.
Join the MSPs who trust DNS Spy to protect their clients' critical infrastructure.
Start Your Free 7-Day TrialCredit card required. You're not charged for 7 days, and you can cancel anytime.
techfirm.io
Out of syncNameservers disagree on the MX record. Some senders will deliver mail to the old host.
| Nameserver | MX answer | Serial |
|---|---|---|
| ns1.techfirm.io | 10 mx1.newmail.net | 2026100801 |
| ns2.techfirm.io | 10 mx1.newmail.net | 2026100801 |
| ns3.techfirm.io | 10 mail.oldhost.com | 2026092203 |
RFC 1034 expects every authoritative nameserver to serve the same zone. ns3 has not picked up the last 2 zone updates.