For agencies

Watching domains you do not own

An agency holding sixty client domains has sixty renewal dates it does not control, spread across registrars it often has no login for. The registry is the one source that covers all of them.

Published 18 September 2026 · Updated 27 October 2026 · Figures checked against primary sources, not recalled.

Check it now: the free bulk domain expiry checker will paste up to 100 client domains and see which expire first.

The failure mode is well known to anyone who has run an agency for more than a couple of years. A client's site goes down. It is not the host, not the DNS and not the code. The domain expired, the renewal notice went to a founder who left in 2023, and nobody found out until a customer phoned.

What makes this hard is not tracking dates. It is that the dates live in systems you do not control.

Why the usual approaches fail

Registrar emails go to the registrant, not to you. The registrant contact is frequently an ex-employee, a shared inbox nobody reads, or an address on the domain that just stopped resolving.
A spreadsheet is a snapshot. It records what was true when someone last typed in it. It cannot tell you a domain entered redemption yesterday.
Registrar dashboards do not combine. Sixty domains across eight registrars is eight logins, several of which belong to the client rather than to you.
Uptime monitoring tells you too late. By the time a site fails a check, the domain has already stopped resolving — and the cheap recovery window has already closed.

If you are choosing a tool rather than building a process, our comparison of the best domain monitoring tools sets five of them side by side, ours included, and says where each of the others is the better pick.

What the registry gives you instead

Registry records are public, read-only data. Watching a domain needs no relationship with it, no transfer, no registrar login and no permission from whoever holds it. That single fact is what makes cross-client monitoring possible at all: you can watch a name the client has not given you access to, and a name the client has forgotten they own.

It is also authoritative in a way a reseller panel is not. The registry's status is the record everything else is derived from.

Which states actually warrant an alert

Alerting on everything trains people to ignore alerts. For client work, four transitions carry genuinely different actions:

Transition	What it means for the client	Urgency
Hold (`clientHold` / `serverHold`)	The site is down now, for a reason unrelated to the calendar	Immediate
Expiring soon	Renewal is due; cheapest possible fix	Days
`redemptionPeriod`	Recoverable, but at a restore fee of $41.40–$175 for a .com	Within 30 days
`pendingDelete`	Unrecoverable. Prepare the client for losing the name	Informational

The distinction between the third and fourth rows is the one worth getting right. In redemption there is still something to sell the client — a restore, a conversation, an invoice. In pending delete there is not, and telling them early is the difference between managing it and being blamed for it.

Watching is not the same as controlling. Monitoring tells you a domain is in trouble; only the registrant or their registrar can renew or restore it. The value is the number of days of warning, not the ability to act unilaterally.

A practical setup

List every domain you have ever built on, not just the ones you currently manage. Lapsed clients are where the surprises live.
Watch them all from one place, independent of who holds the registrar login.
Turn on hold and redemption alerts; leave "expiring soon" on only if you are the one who renews.
Re-check the list when a client leaves. A domain you built and no longer watch is a call you will get anyway.

For a client whose site you deploy from GitHub, a weekly domain expiry check in GitHub Actions puts the warning in the same place as their builds.

Common questions

Can I monitor a domain I do not own?

Yes. Registry records are public, read-only data, so watching a name requires no relationship with it and no permission from whoever holds it.

Will monitoring let me renew a client domain automatically?

No. Monitoring reports status; only the registrant or their registrar can renew or restore. What it buys you is warning time, not control.

How is this different from uptime monitoring?

Uptime monitoring tells you a site is already down. Domain monitoring tells you it is going to be, typically weeks earlier, while renewal is still cheap.

What about client domains on ccTLDs?

Any TLD in the IANA bootstrap registry that publishes an RDAP endpoint can be watched. Some ccTLDs publish status but no expiry date, so those are tracked by status transitions instead.

Sources

One watchlist across every client and every registrar

Registry records are public, so DropPerch can watch a client domain without any login, transfer or permission. 25 domains free for the first 25 accounts, 5 after; unlimited on a paid plan.

Start watching free