DNS Change Alerts
Watch public nameserver and DNS record pages so a hijack or migration does not hide.
DNS change alerts watch nameservers and records so a hijack or migration does not go unnoticed.
Migrations are planned. Hijacks are not. Both look like NS or record changes on a public lookup. Uptime monitoring tells you the site failed. SSL tools tell you a cert aged out. Neither tells you the zone now points at a stranger. If you hold a high-value name, that gap is the whole incident.
Public lookup, not a hidden resolver API
Paste a public DNS lookup page for the name, or a status URL that prints NS and A records. Describe "nameserver or material record changes for [domain]. Ignore TTL jitter and lookup timestamps." AyeWatch reads that page or a topic about it. It is not a recursive resolver you run. It is not Route 53. It is not Pingdom and it will not chart latency. If you need probe-based DNS monitoring from many networks, buy that class of tool. If you need a human ping when the public record set flips, this is enough.
Incident context from the open web sits in OSINT AI monitoring. BIND or CoreDNS advisories sit in CVE monitoring. When a change should page a channel, use webhooks.
What "material" means
NS set changes. Apex A or AAAA moves. MX moves. A new unexpected CNAME on a name you use for mail or app. Do not alert on every TXT campaign your ESP rewrites, unless that is the risk. Say so in the rule. Free Preview is six lifetime runs across three topics. Pro is $9 a month. Paid automation patterns are in alerts to automation workflows.
Start a monitor in under a minute
Free Preview is six lifetime runs across three topics. No card.
Try AyeWatch freePlanned migrations still deserve a watch
Set the alert before you move NS, not after. You want the ping that says the cut completed, and the ping if it flips back. Hijack response is the same feed. One topic, two uses. Keep the registrar UI for actually changing records. Keep AyeWatch for noticing.
Start with the zone customers hit
Watch the apex you print on business cards, plus the mail domain if it is separate. If the first alert is a real NS change, you are done with the design. If it fires on lookup-site chrome, switch the URL to a quieter lookup. Then stop assuming DNS is static because it was static last quarter.