DNS Change Alerts
Watch any DNS record and get an email the moment its value changes. Checked hourly, free, no account. Confirm by email, unsubscribe in one click.
What this does
Pick a hostname and a record type. We check it every hour and email you if the value changes — the old value and the new one, side by side, with a link to see how far the change has spread across all 14 resolvers.
It's free, there's no account, and you can stop it with one click from any alert.
When it's useful
- During a migration — know the moment a cutover actually lands instead of refreshing a lookup page all afternoon.
- Catching changes you didn't make — an unexpected NS or MX change is one of the earliest signals of a domain hijack or a compromised registrar account.
- Watching a vendor — when someone else controls a record your service depends on, an alert is better than an outage.
- Expiry-adjacent surprises — records vanishing is itself a change, and NXDOMAIN is reported like any other.
How we handle your address
We ask for an email address because that's where the alert goes, and we use it for nothing else. There's no newsletter, no marketing, and it isn't shared or sold.
Every subscription is confirmed first: we send a link, and the watch doesn't start until you click it. That's deliberate — without it, anyone could sign up anyone else's address, which is both rude and a good way to get a sending domain blocklisted. Unconfirmed requests delete themselves after 48 hours. Every alert carries a one-click unsubscribe that needs no account and no login.
FAQ
How quickly will I hear about a change?
Within the hour. The check runs hourly rather than continuously — DNS changes propagate over minutes to hours anyway, so a tighter loop would mostly generate noise while the record is still settling.
What counts as a change?
Any difference in the record's values, including a record disappearing entirely (reported as NXDOMAIN) or appearing for the first time. Multiple values are compared as a sorted set, so records simply being returned in a different order won't trigger a false alert.
Will a temporary DNS failure trigger an alert?
No. If the check itself fails — a timeout, an unreachable resolver — that's recorded as a failed lookup, not a change. Alerts you can't trust are alerts you start ignoring, so a failed check is treated as "no information", not "something happened".
How many records can I watch?
Ten per email address. If you need more than that you're probably after real monitoring with an SLA behind it rather than a free tool.
Why does the alert come from boringhaus.com?
Boringhaus is the small portfolio WhereIsDNS belongs to, and it's the domain with verified sending set up. Sending from a domain that isn't properly authenticated is the fastest way to land in a spam folder, so alerts go out from the one that is.
Is this a replacement for real DNS monitoring?
No, and it doesn't pretend to be. It's an hourly check from one vantage point with an email at the end. If you need sub-minute detection, an SLA, escalation policies, or an audit trail, use a paid monitoring service.
Background reading
See the DNS Records Explained guide, the TTL glossary entry for why changes take time to spread, and the propagation checker to see where a change has reached.