Domain Monitoring
Watch public registrar, DNS, and nameserver pages for a name you own or track.
Domain monitoring watches registrar, DNS, and nameserver changes on a name you own or track.
Hijacks are boring until they are not. Nameservers flip. A registrar lock disappears on a public WHOIS page. A competitor parks a lookalike. You find out when mail bounces or when a customer lands on the wrong site. Uptime tools will tell you the host is down. They will not tell you the NS set changed.
What AyeWatch can honestly watch
AyeWatch watches public pages and topics. Paste a public WHOIS lookup URL, a DNS status page, or a registrar status URL you can open in a logged-out browser. Describe a topic like "nameserver or registrar change for example.com on public lookup pages." That is the product. It is not a registrar API. It is not a zone editor. It is not Pingdom. It will not probe SSL expiry on a schedule unless you pointed it at a public page that shows that fact.
For lookalike launches and new product domains, combine this with competitor product launch monitoring. For a wider public-source desk, see OSINT with AI. Security advisories on the DNS software you run still belong in CVE monitoring.
How to set it
One topic per name you cannot lose. Write "alert when registrant, registrar, or nameserver data changes on the public lookup page. Ignore timestamp-only refreshes." Push if you own the name. Email if you are only tracking a rival. Free Preview is six lifetime runs across three topics. Pro is $9 a month. Paid webhooks can page whoever holds the registrar login. See webhook pipelines.
Start a monitor in under a minute
Free Preview is six lifetime runs across three topics. No card.
Try AyeWatch freeWhat to use instead when you need a control plane
If you need to change nameservers, buy a registrar account. If you need certificate expiry as a probe, use an uptime tool. If you need RDAP dumps in bulk, use a domain data vendor. AyeWatch is the "this public page moved" layer so a human looks. That is still how a lot of hijacks get caught, because the first signal is a page, not an API you forgot to poll.
Watch the name you would call legal about
Start with production, the email domain, and one lookalike if you already know it. If the first alert is a real NS change, keep it. If it fires every time a WHOIS privacy timestamp wiggles, tighten the rule to nameservers only. Then add WHOIS alerts as a second topic if registrant fields are the risk.