Monitoring Coverage Across Multiple Registrars

Monitoring Coverage Across Multiple Registrars

Domain names spread across GoDaddy, Namecheap, Cloudflare Registrar, a corporate registrar like MarkMonitor or CSC, and two or three local ccTLD resellers are a normal sight for any IT or security team that has been around for a while. Monitoring coverage across multiple registrars matters because every account is a separate place where a domain can expire, get unlocked, or have its nameservers changed. Your zone-level monitoring sees none of it. This article covers what to watch at the registrar layer, how to build coverage that doesn’t depend on logging into eight dashboards, and where the usual advice stops working.

How Domains End Up Scattered

Nobody plans a fragmented portfolio. It builds up over time. Marketing registers a campaign domain on a company card at Namecheap. A regional office needs a .fi or .de name, and a local agency registers it for them. An acquisition brings in 40 domains at a registrar nobody on the team has used before. The risks this brings are covered in more detail in hidden DNS risks from acquired companies.

Registrars also change underneath you. When Squarespace took over Google Domains in 2023, thousands of organizations had their registrations migrated without doing anything. Some of them found out later that their account permissions, 2FA settings, or billing contacts had not come across the way they expected.

Why Zone Monitoring Doesn’t Cover the Registrar Layer

A common misconception is that DNS monitoring of your zone covers the domain as a whole. It doesn’t. Your DNS host (Route 53, Cloudflare DNS, Azure DNS) holds the records. The registrar controls the delegation: the NS records and DS records published in the parent zone by the registry.

If someone with access to a registrar account switches the nameservers to their own, your Route 53 zone stays exactly as it was. Every record you monitor still looks healthy. Meanwhile, resolvers worldwide pick up the new delegation as soon as the parent zone’s NS TTL runs out, which is 172800 seconds (48 hours) for .com, though many resolvers re-check sooner. Your DNS health checks only notice once the attacker’s answers differ from yours, and by then mail and web traffic are already going elsewhere.

That’s why an experienced DNS administrator queries the parent directly as well as the authoritative servers. For .com, `dig NS example.com @a.gtld-servers.net +norec` shows what the registry is actually publishing, whatever your own zone says.

What Monitoring Coverage Across Multiple Registrars Should Track

Five signals cover nearly all registrar-layer incidents:

Expiry dates, pulled from RDAP instead of trusting each registrar’s dashboard. ICANN ended the WHOIS obligation for gTLDs on 28 January 2025, so RDAP is now the authoritative source.

EPP status codes, especially clientTransferProhibited, clientUpdateProhibited, and the server-side equivalents if you pay for registry lock.

Parent-zone delegation: NS records and DS records exactly as the TLD servers return them.

Registrar of record, so you notice if a domain moves to a registrar you don’t use.

Registrant and admin contact emails, checked to make sure the mailbox still exists and receives mail.

Lock status deserves its own procedure, and registrar lock settings and emergency recovery goes through it in detail.

Building Coverage Step by Step

A seasoned infrastructure lead starts with the inventory, not the tooling. Pull invoices from finance and search for registrar names: GoDaddy, Gandi, Porkbun, OVHcloud, Tucows, and any local resellers. Credit card statements often turn up domains that no IT system knows about.

Next, write every domain into one source of truth with registrar, account owner, billing method, and renewal date. A spreadsheet is fine for under 50 domains. Above that, put it in version control as YAML or JSON so changes get reviewed.

Then automate the checks. A daily job that queries RDAP for each domain and the parent NS for each delegation, and diffs the results against yesterday’s snapshot, takes roughly 100-200 lines of Python. Alert on any change to NS, DS, status codes, or registrar. Alert on expiry at 60, 30, and 7 days, even when auto-renew is enabled.

Finally, set up subdomain discovery and DNS health monitoring for every apex domain on the list, including the ones you think are parked. Parked domains still tend to have SPF records missing, which makes them easy targets for spoofing.

A Scenario Most Teams Will Recognize

A mid-sized company has 140 domains across six registrars after two acquisitions. Their .se domain was registered years ago by a Stockholm agency, with an agency employee as the technical contact. That employee left in 2022. Auto-renew was set up against a card that expired. Renewal reminders went to a mailbox that bounced.

The domain went into its grace period, the Swedish storefront stopped resolving, and the first alert came from customer support, not from monitoring. The zone itself was configured perfectly the whole time. Recovery took 11 days, mostly spent proving ownership to a registrar the company had no account with.

Common Mistakes With Multi-Registrar Portfolios

The most common mistake is trusting auto-renew as a control. Auto-renew relies on a valid card, a reachable contact, and a registrar that is still in business. It is a convenience, not a guarantee.

The second is monitoring only the domains in the main registrar account. The domains that cause incidents are almost always the ones outside it: the regional ccTLD, the acquired brand, the product name registered by a founder in 2016.

The third is checking the registrar dashboard instead of the registry. Dashboards cache data and sometimes show what the registrar meant to submit, not what the registry accepted. Only the parent-zone query and RDAP from the registry show what’s actually true.

Edge Cases Where Standard Advice Breaks Down

Many ccTLDs have no full RDAP service, or limit their WHOIS output heavily. DENIC (.de) shows very little public data, and some registries rate-limit queries hard enough that a daily scan of 30 domains gets blocked. For these, fall back to parent NS checks and registrar API polling.

Registry lock exists for .com, .net, and a number of ccTLDs, but not all of them, and it usually costs $100-500 per domain per year through a corporate registrar. Use it on the 5-10 domains that carry revenue and email, not across the whole portfolio.

For teams under 10 people with fewer than 20 domains, consolidating into a single registrar usually beats monitoring several. The exception is ccTLDs with local presence rules, where you may legally have to keep a local registrar. Plan consolidation work around the portfolio reviews before renewal deadlines, so transfers don’t land inside the 60-day lock that follows a registrant change.

FAQ

Should every domain be consolidated into one registrar?
Consolidate where possible, but not at any cost. Local presence requirements, registry lock availability, and enterprise contracts sometimes justify keeping 2-3 registrars. What matters is one inventory and one monitoring layer, not one vendor.

How often should registrar data be checked?
Check parent-zone delegation at least every few hours for critical domains, since a nameserver hijack starts spreading as soon as it’s published. Check RDAP data such as expiry, status, and contacts daily.

Does DNSSEC protect against registrar account compromise?
No. An attacker with registrar access can remove or replace the DS record along with the nameservers. DNSSEC protects answers in transit, not the delegation itself.

Summary

Registrar-layer failures don’t show up in zone-level DNS health checks, and they hit hardest on the domains nobody remembers owning. Build one inventory from finance records, compare the parent zone and RDAP data against a daily baseline, and alert on expiry well before the renewal date, whatever auto-renew says. Start with the domains that sit outside your main registrar account, because those are where incidents usually come from.