How to Manage 100+ Domains Without It Becoming a Job
Somewhere around a hundred domains, everything that worked at twenty stops working. You can no longer hold the portfolio in your head, per-name attention becomes arithmetic (a hundred names at five minutes each is a full workday), and a single missed detail — an off auto-renew, a stale card — hides comfortably in the crowd.
Scale management is about replacing per-name attention with systems: bulk operations, conventions that make names self-describing, a review cadence, and automation for everything a machine checks better than you do.
Think in segments, not names
The core move at scale is grouping. Segment the portfolio into tiers — core names you'd never drop, mid names actively listed, and long-shot names on probation — and make policy decisions per tier instead of per name. Auto-renew on for core, annual review for mid, default-drop-unless-defended for the long tail.
Tags or categories (by TLD, by niche, by acquisition batch) let you answer questions like "what does the crypto batch cost me per year" in one filter instead of an afternoon.
Bulk operations or nothing
- •Registrar-side: bulk renewal, bulk auto-renew toggles, bulk nameserver and contact updates. If your registrar makes these painful at your size, that's a reason to consolidate elsewhere.
- •Portfolio-side: CSV import/export as the lingua franca. Every registrar exports it; every serious tool ingests it.
- •Never hand-edit a hundred rows. If a change can't be done in bulk, batch it monthly rather than dribbling it.
Import your domain list in one CSV
Export from any registrar, import into Sourdough, and get live WHOIS/RDAP enrichment on every domain: expiry, registrar, nameservers, status. 7 days free, then $10/mo. $0 due today.
A review cadence that scales
At scale you review windows, not the whole portfolio. A monthly session covering everything expiring in the next 90 days keeps each session small — roughly a twelfth of the portfolio — while guaranteeing every name gets a deliberate renew/list/drop decision annually, ahead of its deadline.
- •Monthly: renew/list/drop pass on the next 90 days of expiries.
- •Quarterly: reconcile registrar CSV exports against your source of truth.
- •Annually: full audit — ownership details, locks, contact emails, renewal price drift.
Automate the checking, keep the deciding
The work that scales worst is verification: is this expiry date still right, did this name's status change, did a renewal actually process. This is exactly what machines do well. A portfolio tool that re-pulls registry data on a schedule and runs a renewal alert ladder turns a hundred manual checks into a handful of alerts. Sourdough does this — CSV import, live RDAP/WHOIS and DNS enrichment on every name, renewal alerts, and unlimited domains at $10/mo — but whatever you use, the principle stands: automate verification, never automate the drop decision.
Frequently Asked Questions
How much time does managing 100 domains take?
With systems: a monthly review of the next 90 days of expiries plus a quarterly reconciliation — a few hours a month. Without systems it either consumes far more than that or, more commonly, quietly doesn't happen, and the cost shows up as missed renewals and unpruned drag.
Should I keep 100+ domains at one registrar?
Consolidating to two or three registrars with good bulk tooling is usually the sweet spot. A single registrar simplifies operations but concentrates account risk; what matters more is a tracking layer above the registrars that sees everything in one place.
What should I automate in a large domain portfolio?
Verification and alerting: registry-data refresh (expiry dates, status codes), renewal reminders on a ladder, and change detection. Keep judgment calls — what to drop, what to price a name at — manual. Automating the checks is what frees the time to make those calls well.