Home › Blog › How Many Inboxes per Domain for Cold Email? (1 vs 2 vs 3 vs 5, Honestly)
How Many Inboxes per Domain for Cold Email? (1 vs 2 vs 3 vs 5, Honestly)
The advice runs from one inbox per domain to five, and everyone sounds certain. There is no magic universal number, but there is a risk/cost/capacity trade-off with a clear sweet spot. Here's the 2-3 per domain standard we run across hundreds of client fleets, and exactly when to deviate.
Quick Answer: 2-3. Deviate With Reasons, Not Vibes.
2-3 inboxes per domain, ~30 cold sends per inbox per day (15-20 when targeting Microsoft) is the ratio we run fleet-wide. Go down to 1 for Microsoft-heavy or high-stakes segments; going up to 5 saves you ~$12/year per skipped domain in exchange for a louder footprint and a bigger blast radius. There's no universal law, there's a trade-off, and 2-3 is where it balances.
Why the Advice Conflicts: Everyone's Optimizing a Different Variable
The 1-per-domain crowd is optimizing isolation. The 5-per-domain crowd is optimizing cost. Both are describing real trade-offs and presenting them as laws. The honest framing is three dials you're setting simultaneously: capacity (inboxes × per-inbox cap), footprint (how loud one domain's aggregate sending looks to providers), and blast radius (how much warmed capacity dies when one domain burns). More inboxes per domain raises capacity and cost-efficiency while raising footprint and blast radius. That's the whole debate.
The Case for 2-3 (What We Actually Run)
- •Capacity that matters: 60-90 sends/day per domain at safe caps, enough that a 300/day operation needs only 4-5 domains (the full math).
- •A quiet footprint: 2-3 human-named users sending ~30 each looks like a small real team, because that's what small real teams look like.
- •Survivable failures: when a domain hits the recover/rest/retire tree, you lose 2-3 warmed inboxes, annoying, not catastrophic.
- •Warmup economics: every inbox needs 2-4 weeks of warmup (or arrives prewarmed); 2-3 per domain keeps the warming pipeline proportionate to the sending pipeline.
When to Run 1 Per Domain
Maximum isolation earns its overhead in three situations: Microsoft-heavy segments, Outlook's filtering is less forgiving and slower to build trust (the Outlook guide covers why), so some operators run leaner domains there with lower caps; high-value ABM campaigns where one domain's reputation carries a small number of must-land sends; and recovery pools, where a domain re-entering rotation proves itself with one inbox before getting its full complement.
When 4-5 Is Defensible (Rarely)
If budget genuinely caps your domain count, 4-5 inboxes per domain at reduced per-inbox volume (~20/day) keeps the domain's total under ~100/day, workable, and better than overdriving fewer inboxes. But be clear about what you're buying: at ~$12/domain/year, packing five inboxes instead of three saves about $1/month per displaced inbox while concentrating risk. Domains are the cheapest component in the stack; inbox-seats and warmup time are the expensive ones, and those cost the same either way.
Sizing the Whole Fleet
Work backward from volume: target daily sends ÷ 30 = inboxes needed; inboxes ÷ 2.5 ≈ domains. Our Inbox Planner runs the math for any target plus a safe ramp-up schedule, and if you're planning rotation pools with resting and warming groups (you should be, at any real scale), the rotation system guide covers how the ratio extends into a living fleet.
Frequently Asked Questions
How many inboxes should I put on one cold email domain?
2-3 is the standard we run across hundreds of client fleets. It's the point where per-domain cost efficiency and blast-radius control balance: enough capacity per domain to matter (60-90 sends/day at safe per-inbox limits), small enough that the domain's total footprint never resembles a blast operation and a burned domain never takes too many warmed inboxes down with it.
Is 5 inboxes per domain too many?
It's not fatal, but you're trading risk for a small saving: five inboxes pushing ~150/day from one domain is a louder footprint providers can aggregate, and when that domain burns you lose five warmed inboxes at once instead of two or three. The $12/year you save on domains is the cheapest line item in the whole operation, it's the wrong place to economize.
Is 1 inbox per domain safer?
Marginally, and it's the right call in specific cases, Microsoft-heavy targeting, very high-value accounts, or recovery situations. But run fleet-wide it doubles-to-triples your domain count and warmup surface for a small risk reduction. Maximum isolation is a tool for your riskiest segment, not a default.
How many emails can each inbox send per day?
Keep cold volume around 30/day per inbox on Google-targeted sending, roughly half that (15-20) on Microsoft-targeted sending, with warmup running alongside. Provider caps are far higher, Workspace allows ~2,000/day, but cold email isn't about what's allowed, it's about what doesn't pattern-match to bulk.
Should every inbox on a domain be in the same campaign?
Avoid it when you can. Spreading a domain's 2-3 inboxes across different campaigns or segments smooths the domain's sending pattern and means one bad list only touches part of the domain's capacity. Same-campaign stacking concentrates both the pattern and the risk.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes