Why track a domain portfolio
With one or two domains, a company can keep track of them from memory. A portfolio of dozens of names is a separate task: different registrars, different renewal dates, different people responsible for DNS. Without a single registry, a typical scenario plays out: a domain from a marketing campaign expires quietly because nobody knows it even exists, and a drop-catcher picks it up on the first day after release.
Managing a domain portfolio is not bookkeeping for its own sake — it is a way to keep control of an asset worth more than it looks: a domain carries reputation, link value and sometimes the only inbound mail channel for customers.
What to record in a domain registry
The minimum set of fields without which tracking is useless:
| Field | Why it matters |
|---|---|
| Registrar and account | Where exactly to renew and who has access to the panel |
| Expiration date | The reference point for reminders and the renewal budget |
| NS servers | Where the domain points and who is responsible for the zone |
| WHOIS owner | The legal entity or person the registration is issued to |
| Purpose | Main site, subdomain, redirect, defensive brand registration |
A registry can be kept in a spreadsheet, but for dozens of domains it is easier to export the data with a scheduled script than to rewrite it by hand at every check.
Auto-renewal and controlling expiration dates
Auto-renewal removes part of the risk but does not replace tracking: if the linked card has expired or the registrar balance has run out, renewal quietly fails. A practice that actually works: two independent reminders, 60 and 14 days before expiration, from different sources. The first from the registrar itself, the second from the company's own calendar or task tracker built on the internal registry.
For domains that are not renewed automatically by business decision, status needs review at least once a quarter: some registrations are made just in case and over time people forget why they were needed at all.
Bulk status checks via API
Once there are more than ten domains, manual checks through the registrar's web interface turn into an error-prone routine. It is simpler to query WHOIS or RDAP in bulk with a script and compare expiration dates against the registry:
for domain in $(cat domains.txt); do
echo -n "$domain: "
whois "$domain" | grep -i "Registry Expiry Date"
doneA more reliable option for dozens or hundreds of domains is a dedicated WHOIS API: it does not hit the request limits of public servers and returns data in a structured form that is easy to reconcile with the registry automatically.
Common portfolio risks and how to close them
Most domain portfolio problems repeat from one company to another:
- A domain is registered under the personal account of an employee who has already left — renewal access leaves with them.
- NS servers point to infrastructure that was decommissioned a year ago.
- WHOIS contact details lead to a mailbox nobody reads anymore, so renewal notices go nowhere.
- Similar spellings of the brand are not registered at all, and anyone can use them.
Every one of these risks is closed by the same measure — regularly reconciling the registry with the real state of the domains, not a one-time check at purchase.
Domain portfolio management checklist
- Set up a single registry with every company domain, including defensive and unused ones.
- Tie renewal to a corporate account and mailbox, not a personal one.
- Set up two independent expiration reminders for each domain.
- Reconcile the registry with real data via WHOIS or an API once a quarter.
- Check WHOIS privacy for domains where public contacts are not needed.