Anyone administering mail for more than a handful of domains ends up keeping a spreadsheet. Which domain is on which provider, which nameservers, whose card pays for it, when DNS was last checked, who the contact is. Forty domains, one account is the arrangement that makes the spreadsheet unnecessary, because the platform holds the answers instead.
This page covers what actually changes at that scale, the operations that stop being per-domain chores, and where consolidation is the wrong instinct.
How It Degrades at Forty
Nothing breaks dramatically when you reach forty domains, one account or otherwise. What happens is that per-domain work, which was trivial at three, becomes the job.
DNS checking is the clearest example. Verifying that one domain's records are correct takes a minute; verifying forty takes most of a morning, so it gets done rarely, which means a broken record can sit unnoticed for months until somebody reports mail going missing.
The same applies to everything else that's per-domain: adding a mailbox, checking storage, confirming a certificate renewed, noticing that a domain's sending path changed. None of these are hard. All of them are forty times.
And with forty domains spread across providers, there's no single place to look, which is why the spreadsheet exists — it's a manual index of things the systems know but won't tell you together.
The Operations That Turn Collective
Forty domains, one account makes a handful of operations collective rather than repetitive, and those are where the time goes back.
DNS applied rather than instructed. Where domains sit behind Cloudflare, records can be written directly through their API rather than handed to somebody as a list to type. That removes both the typing and the transcription errors, which are the usual cause of a domain that almost works.
Bulk domain addition. Adding forty domains is one operation rather than forty, and the same applies to provisioning their mailboxes.
One view of status. Which domains pass their checks, which have mail flowing, which are quiet. That view is the spreadsheet, maintained by the system rather than by you.
One bill. Not the most interesting benefit and frequently the one that prompts the move, because forty small invoices from four providers is its own administrative burden.
The Limits That Matter at This Scale
Domain counts by plan decide whether forty domains, one account fits at all:
| Plan | Domains | Mailboxes per domain |
|---|---|---|
| Free | 10 | 10 |
| Starter | 50 | 100 |
| Pro | 100 | 300 |
| Agency | 1,000 | 1,000 |
Forty domains, one account fits comfortably on Starter at $4 a month, which surprises people who assumed multi-domain administration was an enterprise concern. What Starter doesn't give you is filters, so if automatic sorting matters the relevant tier is Pro rather than Starter — a boundary worth knowing before choosing.
The other constraint is storage, pooled across everything: 15 GB on Starter, 50 on Pro, 200 on Agency. Forty domains with a few mailboxes each will find that fine; forty domains with busy mailboxes will not.
Keeping It Organized
Forty domains, one account solves the tooling problem and creates an organizational one, because forty of anything in a single list is hard to navigate.
Notes on domains are worth more than they look. A line recording why a domain exists, who it belongs to and what it's for is the thing you'll want in eighteen months when you can't remember, and it lives with the domain rather than in a document nobody updated.
Consistent naming across domains helps as much here as anywhere. If mailbox naming follows the same pattern everywhere, an address tells you which domain it belongs to and what it does without a lookup.
And it's worth deciding which domains are actually live versus parked, because they need different attention. The parked ones want a catch-all and nothing else, described in parked domain email; the live ones want checking.
The Note Field Earns Its Keep
At forty domains the question that recurs is not how something is configured but why it exists at all.
A one-line note on each domain recording who it belongs to, what it's for and when it was last reviewed answers that without a separate document that nobody updates. It's the cheapest piece of documentation in the whole arrangement and the one most consistently skipped.
Where Consolidation Is Wrong
Two cases where forty domains, one account is the wrong shape, and both are worth taking seriously.
Client domains you may hand back. If a client might leave and take their domain to their own account, holding it inside yours makes that separation harder. It's doable, but it's a migration rather than a transfer of ownership, and the time to think about it is before rather than during.
Domains with genuinely different requirements. If one domain needs a compliance posture the others don't — data residency, particular retention, a specific sending path — putting it alongside thirty-nine others means the strictest requirement effectively applies to everything or is met by exception, and exceptions get forgotten.
The middle position most agencies land on is consolidating everything routine and keeping the two or three genuinely special domains separate, which is more sensible than either extreme.
Getting There Without a Weekend
Arriving at forty domains, one account sounds like a project and is mostly waiting.
Nobody should attempt it in a single sitting, and there is no reason to. Domains move independently, so the change can run over weeks with no coordination between them, and a problem on one has no bearing on the rest.
The work per domain is adding it, applying DNS, and migrating any existing mailboxes. Only the last of those takes real time, and it runs in the background. The sequence that avoids trouble is doing the quiet domains first — parked names and low-traffic ones, where a mistake costs nothing — and leaving the busiest until you're confident in the process.
Mail continues arriving at the old provider until DNS propagates, so nothing is lost during the changeover; the two overlap rather than cutting over. Bringing existing mail across is covered in migration, and it's worth running the reconciliation afterwards rather than assuming a successful copy was a complete one.
