[{"data":1,"prerenderedAt":175},["ShallowReactive",2],{"seo-features/dns-monitoring":3},{"slug":4,"kind":5,"archetype":6,"cluster":7,"navGroup":7,"navLabel":8,"meta":9,"breadcrumbs":14,"hero":22,"sections":61},"features/dns-monitoring","spoke","capability","monitoring","DNS Monitoring",{"title":10,"description":11,"canonicalPath":12,"twitterCard":13},"DNS Change Monitoring — MX & CNAME Alerts","Someone changed the MX records and email is silently misrouting. Sitewatch snapshots DNS and alerts on unexpected MX and CNAME changes you did not make.","/features/dns-monitoring","summary_large_image",[15,18,21],{"label":16,"href":17},"Home","/",{"label":19,"href":20},"Features","/features",{"label":8,"href":12},{"eyebrow":8,"headline":23,"intentStatement":24,"bullets":25,"primaryCta":35,"secondaryCta":38,"proofPanel":40},"DNS changes you didn't make — flagged before they cause a support fire","Someone changed the MX records and now the client's email is silently routing to the wrong place. Or a CNAME got repointed during a migration. The website stays up, so nothing alerts — until the support tickets start. Sitewatch sees the DNS change the day it happens.",[26,29,32],{"icon":27,"text":28},"heroicons:envelope","Alerts on unexpected MX (mail) record changes",{"icon":30,"text":31},"heroicons:link","Alerts on CNAME (subdomain/alias) changes",{"icon":33,"text":34},"heroicons:camera","Snapshots and diffs your records on a schedule",{"label":36,"href":37},"Monitor DNS free","/scan",{"label":39,"href":20},"Back to features",{"type":41,"incidentTitle":42,"severity":43,"affectedLabel":44,"detectedLabel":45,"eventLines":46},"incident","DNS record changed","warning","Affected records","Detected in last check",[47,50,55,58],{"icon":27,"text":48,"time":49,"type":41},"MX — changed to mail.unknown-host.com","just now",{"icon":51,"text":52,"time":53,"type":54},"heroicons:arrow-long-left","Previous: aspmx.l.google.com","12h ago","ok",{"icon":30,"text":56,"time":57,"type":54},"CNAME www — unchanged","1m ago",{"icon":59,"text":60,"time":57,"type":54},"heroicons:globe-alt","Website still responding 200 OK",[62,90,104,123,130,148],{"id":63,"tocLabel":64,"type":65,"eyebrow":66,"heading":67,"items":68},"benefits","Why it matters","benefits-grid","High blast radius, often outside your control","DNS drift breaks email and services while the website stays up",[69,72,75,78,82,86],{"icon":27,"title":70,"description":71},"MX record monitoring","Mail records are the highest-stakes DNS records. A change can silently reroute or drop a client's email — and the website gives no sign anything is wrong. Sitewatch flags MX changes you didn't expect.",{"icon":30,"title":73,"description":74},"CNAME change detection","A repointed CNAME during a migration, a subdomain alias gone wrong, a service handoff that broke an integration. Sitewatch catches CNAME drift before it takes a service down.",{"icon":33,"title":76,"description":77},"Snapshot and diff","Sitewatch snapshots your DNS records and compares each check against the last known-good state, so you see exactly what changed — old value versus new.",{"icon":79,"title":80,"description":81},"heroicons:user-group","Changes from outside the agency","DNS is often touched by people you don't control — a client's IT contractor, a registrar migration, a third-party service. Sitewatch is the watch on changes nobody told you about.",{"icon":83,"title":84,"description":85},"heroicons:adjustments-horizontal","Tuned to avoid noise","A/AAAA records churn constantly with CDNs and round-robin DNS, so they are captured but not alerted on at launch. Sitewatch alerts on MX and CNAME — the records where an unexpected change almost always means trouble.",{"icon":87,"title":88,"description":89},"heroicons:bell-alert","Before the support fire","Email bouncing or a service failing is how most teams discover a DNS change — after customers complain. Sitewatch moves that discovery to the moment the record changes.",{"id":91,"tocLabel":92,"type":93,"stats":94},"trust","At a glance","trust-strip",[95,98,101],{"value":96,"label":97},"MX + CNAME","Records alerted on",{"value":99,"label":100},"Before/after","Exact value diff in the alert",{"value":102,"label":103},"Every plan","Available on free and paid",{"id":105,"tocLabel":106,"type":107,"eyebrow":108,"heading":109,"groups":110},"detection","What we detect","detection-list-grouped","DNS failure modes","How DNS drift breaks things the website can't show you",[111,117],{"groupLabel":112,"icon":27,"items":113},"Mail (MX) changes",[114,115,116],"MX records repointed to an unexpected mail host","MX records removed, silently dropping inbound mail","A migration that changed mail routing without notice",{"groupLabel":118,"icon":30,"items":119},"Alias (CNAME) changes",[120,121,122],"A CNAME repointed during a platform migration","A subdomain alias broken by a service handoff","A third-party integration CNAME changed under you",{"id":124,"tocLabel":125,"type":126,"heading":127,"subtext":128,"primaryLabel":129,"primaryHref":37},"cta-mid","","cta-strip","Know about DNS changes before your client does","Add a site and Sitewatch snapshots its DNS automatically. Free plan, no credit card.","Start monitoring free",{"id":131,"tocLabel":132,"type":133,"eyebrow":132,"heading":134,"items":135},"faq","FAQ","faq-accordion","Frequently asked questions",[136,139,142,145],{"question":137,"answer":138},"Which DNS records does Sitewatch alert on?","MX (mail) and CNAME (alias) records at launch. These are the records where an unexpected change reliably signals a problem — misrouted email or a broken service. A and AAAA records are captured for context but not alerted on, because CDN and round-robin churn would create constant false alarms.",{"question":140,"answer":141},"How is this different from DNS resolution monitoring?","Availability monitoring checks whether a domain resolves at all — a hard failure. DNS change monitoring checks whether the records themselves changed when you didn't expect it — a silent change that can break email or services while the site still resolves and returns 200 OK.",{"question":143,"answer":144},"What does a DNS alert contain?","The record type that changed, the previous value, and the new value — so you can immediately tell whether it was a legitimate change you forgot about or something to investigate.",{"question":146,"answer":147},"Why does DNS drift happen without the agency knowing?","Because DNS is frequently managed outside the agency — by a client's internal IT, a contractor, a registrar during a transfer, or a third-party service. Those changes rarely get communicated. Snapshotting the records is the only reliable way to catch them.",{"id":149,"tocLabel":150,"type":151,"eyebrow":152,"heading":153,"links":154},"related","Related","related-links-grid","Explore more","Related monitoring solutions",[155,160,165,170],{"label":156,"href":157,"description":158,"icon":159},"SSL Certificate Monitoring","/features/ssl-certificate-monitoring","Catch expiring certificates and chain problems early.","heroicons:lock-closed",{"label":161,"href":162,"description":163,"icon":164},"Domain Expiry Monitoring","/features/domain-expiry-monitoring","Get warned well before a domain registration lapses.","heroicons:calendar-days",{"label":166,"href":167,"description":168,"icon":169},"Website Migration Monitoring","/website-migration-monitoring","Verify records and pages survive a migration.","heroicons:arrows-right-left",{"label":171,"href":172,"description":173,"icon":174},"Website Monitoring","/website-monitoring","Full-page verification beyond uptime checks.","heroicons:shield-check",1780857882427]