Feature

Domain Name Monitoring That Covers Every Signal

Founder, Notify.domains · ex-GoDaddy Director of Education · founder, DomainSherpa & DNAcademy

Domain name monitoring means one thing in practice: something checks a domain often enough to notice a change, and then tells a human what the change means. Doing it properly requires watching signals that live in completely different systems, from registry records to certificate endpoints to auction feeds, and knowing which combinations matter. Notify.domains runs all of them against every domain on your list 25+ times a day, then sends one plain-English alert with the next step attached.

Try it on one domain right now

Pull the live record for free, then add the name to a watchlist and let the monitoring run for 7 days without a credit card.

Free, no login, and we do not store your lookups.

What we watch

Monitoring is only as good as its coverage. Here is the full set, grouped the way the dashboard groups it.

Registration Records

Expiration date, status flags, registrar, registrant fields, and nameservers, read over RDAP where a registry supports it and WHOIS where it does not.

DNS Records

A, AAAA, CNAME, MX, TXT, and NS records, queried over encrypted DNS. Hosting moves, mail changes, and parking switches all surface here.

Website Health

Whether the site resolves, its HTTP status, page title, meta description, redirect status and target, certificate expiry, and a periodic screenshot of the homepage.

Auctions

The major auction venues used by large registrars, with current bid, closing time, bid and bidder counts where published, and closeout tier moves.

Marketplaces

Resale listings with asking price, listing type, minimum offer floors, and lease-to-own terms where a venue publishes them.

Reputation

Spamhaus domain blocklist status and Ahrefs Domain Rating, so you can tell a clean name from one carrying baggage.

What domain name monitoring actually involves

The word covers three jobs that sound similar and are not.

Collection. Reading each signal from wherever it lives. That means the registry or registrar record, the DNS resolvers, the web server, the certificate endpoint, a blocklist, and every auction and marketplace venue. These are separate systems with separate protocols, rate limits, and failure modes.

Comparison. Storing each value and diffing it against the last one. Without history there is no change detection, only a current state, which is what a one-time lookup gives you.

Interpretation. Deciding which changes deserve to interrupt you and what a person should do about each one. This is the part most tools skip. A raw diff that says a status field went from one string to another is not an alert, it is homework.

We do all three. The output is not a data feed, it is a message that says what happened and what to do next.

How often we check, and why it varies

At current settings we run 25+ checks per day on every watched domain. Those checks are not identical, because the signals do not move at the same speed.

Marketplace and auction data changes fastest, since a listing can appear and a price can be cut within hours, so those passes run most frequently. Registration records, DNS, and website checks run on their own schedules, with a floor of at least twice a day each. Ahrefs Domain Rating runs weekly, because backlink strength does not move hour to hour and pretending otherwise would just add noise.

When a domain is not registered, we skip the checks that cannot apply to it, such as the website fetch and the certificate read. That keeps the data honest and stops us reporting phantom outages on a name that has no site to be down.

Filtering noise so alerts stay worth reading

The failure mode of monitoring is not missing changes. It is sending so many that you stop reading them. A lot of our work goes into deciding what not to send.

Registrant changes get classified. A field moving between "California" and "CA" is formatting. A real value turning into a privacy mask is a privacy toggle. A shift between two known proxy services is an administrative swap. We separate all of these from an actual ownership change.
Listing removals get rechecked. Before we tell you a listing is gone, we poll again several times, and for some venues we wait for a second monitoring run to agree. A marketplace outage should not read as a sale.
Certificate flags do not fire on renewal. Clearing an expired flag because someone renewed is not an expiry event.
Small backlink movements can be muted. Domain Rating drifts. You can suppress changes below a threshold.
DNS-only sale signals are labeled as such. Nameservers matching a for-sale pattern is a hint, not a confirmed listing, and we say so in the alert rather than overselling it.

Where the alerts go

Alerts reach you by email, in the app, in Slack, in Telegram, or on an HTTPS webhook you control. Because webhooks post JSON to any URL, you can route events into Zapier, n8n, Make, or your own stack without us building a specific integration for each one.

You also control volume. Channels are set per domain, so a client name can alert a shared Slack channel while a speculative watch stays quiet. The Domain Insights Digest arrives on the 1st and the 15th with a summary of the previous two weeks, which is the right setting for names you are tracking casually. Individual event types can be muted account-wide when you never want to hear about them.

What this would cost you to do by hand

The honest comparison is not against another tool, it is against your own time.

To match this coverage manually for a single domain you would be checking auction and marketplace listings through the day, re-reading the registration record and DNS, and re-testing the website and its certificate. Totalled up, that is roughly 95 minutes a day, or about 578 hours a year. Valuing your own time at just $5 an hour, that is $2,889.58 a year, for one name.

Monitoring costs $24 a year for your first domain, which is about $2.00 a month. You are not really buying checks, you are buying the consistency nobody sustains by hand: no weekends off, no forgetting for three weeks, no discovering in November that the thing you wanted sold in September.

The alerts you actually receive

Real notification examples for this feature. Every alert names what changed and what to do next.

Domain became available for registration

Example.com is no longer registered. You can register it now at your preferred registrar before someone else does.

Nameservers changed

Nameservers updated. This often signals a hosting change, migration, or sale preparation. Worth keeping an eye on for availability.

Hosting or mail changed

A record changed. This can mean a hosting move or business change. The owner might be more open to selling.

Transfer lock added

A transfer lock was placed on the domain, so it can no longer be transferred. This may be a registrar security measure or the start of a dispute.

Domain Rating changed

The backlink strength score moved meaningfully. Useful context when you are valuing a name or checking whether its history is intact.

Site came back online

The domain began resolving again after being unreachable. Somebody is still paying attention, so temper your expectations.

Key facts

We run 25+ checks per watched domain per day at current settings, spread across registration, DNS, website, auction, and marketplace passes.
Marketplace and auction checks run most frequently because listings and prices move fastest.
Ahrefs Domain Rating is refreshed weekly rather than daily, because backlink strength does not change hour to hour.
Checks that cannot apply to an unregistered domain are skipped, so you do not get phantom downtime alerts on a name with no website.
Registrant changes are sorted into real ownership moves versus privacy toggles, proxy swaps, and formatting noise.
Listing removals are rechecked, and for some venues confirmed across two monitoring runs, before we report them.
Coverage spans all 2,205 extensions in the IANA root zone.
Alerts go to email, in-app, Slack, Telegram, or an HTTPS webhook, configurable per domain.

Doing it yourself versus Notify.domains

Capability	Registrar alerts	Enterprise brand suites	Notify.domains
Works on domains you do not own	No	Yes	Yes
Registration and status monitoring	Partial	Yes	Yes
Website, certificate, and redirect signals	No	Partial	Yes
Auction venue coverage	No	No	Yes
Marketplace price tracking	No	No	Yes
Plain-English next steps	No	No	Yes
Priced for one domain	Yes	No	Yes

Frequently asked questions

What is domain name monitoring?

It is the practice of repeatedly checking a domain's public data and alerting you when something changes. Done properly it covers the registration record, DNS, the website and its certificate, and the places a domain can be sold, then interprets those changes rather than just reporting raw differences.

How often should a domain be checked?

It depends on the signal. Marketplace prices and auction listings can change within hours, so those deserve frequent polling. Registration records and DNS move more slowly, though the important transitions such as entering pending delete still need catching the same day. We run 25+ checks per domain per day and weight them accordingly.

Can I monitor a domain I do not own?

Yes, and that is the main use case. Every signal we use is public: registry and registrar records, DNS, the web server response, the certificate it presents, blocklists, and public listings. No account access at the registrar is required.

Is there free domain monitoring?

Our lookup tools are free with no account, and monitoring is free for 7 days on one domain with no credit card. After that it is $24 a year for your first domain. Genuinely free ongoing monitoring tends to mean either a single signal or a very slow check cycle, which is where the gaps come from.

What is WHOIS monitoring?

It is watching the public registration record for changes to the registrant, registrar, status codes, expiration date, or nameservers. We do this using RDAP where the registry supports it, since RDAP returns structured data, and fall back to WHOIS where it does not.

How is this different from your solutions pages?

This page describes the monitoring capability itself. The solutions pages describe applying it to a specific goal, such as catching an expiration, coordinating backorders, or protecting a brand. Same product, different starting point depending on whether you are asking what it does or what it does for you.

Will I get too many alerts?

You control it. Channels are configurable per domain, individual event types can be muted account-wide, and the Domain Insights Digest gives you a twice-monthly summary instead of a stream. We also filter aggressively on our side, for example classifying registrant formatting changes separately from real ownership changes.

Explore the other features

All features

Website Signals

Watch the website itself for distress. Downtime, an expired certificate, or a redirect to a new brand often shows up months before a name reaches the open market.

Domain Monitoring

Check any domain expiry date, then keep checking it automatically. We read the registry record all day and tell you the moment a date or status flag moves.

Backordering

Backorders only work if they are placed at the right service before the right deadline. We track the drop timeline and tell you where to position and when.

Auction Platforms

Expiring domains are sold at auction long before they drop, and each registrar uses a different venue. We watch them all so you do not have to guess which one to check.

Aftermarkets

Most good names are for sale somewhere at some price. We watch the resale marketplaces for listings and price moves, so you buy on a dip instead of at full ask.

Matching solution

The Best Domain Monitoring Service

Compare domain monitoring services for expired names, auctions, drops, marketplaces, and brand protection. See how Notify.domains stacks up against registrar alerts, DomainTools, and DomainIQ.