WHOIS Alerts
Get pinged when public registrant or nameserver data on a watched domain changes.
WHOIS alerts fire when registrant or nameserver data on a watched domain changes.
WHOIS is messy and still useful. Privacy redaction hid emails. The fields that remain still move when a name is sold, when nameservers change, or when a registrar transfer starts. If you only check a lookup when something is already wrong, you are using it as an autopsy.
Watch a public lookup page
Paste a public WHOIS or RDAP HTML page for the domain. Write "alert when registrant org, registrar, or nameserver fields change. Ignore last-updated timestamps and noise from privacy placeholders." AyeWatch will summarize the public page. It is not a registrar API, not ICANN's bulk WHOIS, and not a tool that bypasses redaction. If the page is a wall of redacted, there is nothing to alert on. Pick a lookup that still shows NS and registrar.
Brand and lookalike work fits OSINT AI monitoring. New product domains fit competitor launch monitoring. Do not confuse a WHOIS wiggle with a CVE. Software holes stay on CVE alerts.
How to run it day to day
One domain per topic if the name is critical. A topic that lists a handful of lookalikes if you are tracking abuse. Push for production domains. Email for research names. Free Preview is six lifetime runs across three topics. Pro is $9 a month. Paid plans can webhook a change into the same flow you use for other public-web pings. See alerts to automation workflows.
Start a monitor in under a minute
Free Preview is six lifetime runs across three topics. No card.
Try AyeWatch freePrivacy pages will fake you out
Many lookups rotate placeholder text. If you do not say "ignore privacy template changes," you will get nightly junk. Nameservers and registrar name are the stable tells. Registrant org, when it is public, is the sale tell. Start with those three. Add more fields only if they stay visible on your chosen lookup.
Prove it on a name you control
Change a harmless nameserver on a staging domain or use a domain you are already transferring. Confirm AyeWatch describes that field change. Then point it at production. If you cannot trigger a change, wait for a known transfer on a name you track. Either way, do not buy a WHOIS API you will not build on. A public page watch is enough for most teams who just need a nudge.