Guide
How to Buy Domains and Mailboxes for Cold Email in 2026
September 15, 2026 · 7 min read
Buying domains and mailboxes for cold email? Get the volume math, naming rules, aging window, and buying process before you provision anything.
The sending setup
Most founders buy domains and mailboxes the same way they buy a SaaS subscription: pick a number that sounds reasonable, buy it, and hope deliverability sorts itself out. It rarely does. The domains and mailboxes under a cold email campaign are infrastructure decisions, and getting the count, the naming, and the sequencing wrong is the fastest way to spend three months rebuilding a sender reputation you never needed to lose.
By Rishabh Ambasta, Founder, Modern Inbound.
This guide covers the actual buying process: how many domains and mailboxes a given send volume needs, how to name them so they don't read as bulk-purchased infrastructure, why a domain has to sit and age before it ever sends a cold email, and where the process breaks for most teams. DNS setup, SPF, DKIM, and DMARC gets a full guide of its own, so this one links out to it instead of repeating it.
How Many Domains and Mailboxes You Actually Need
Start from your target daily send volume instead of a round number that feels safe. A single warmed mailbox holds a conservative 30 to 50 emails a day without tripping spam filters at Gmail or Microsoft 365. Push past that on one inbox and you're relying on technical capacity that exists in theory rather than the sending pattern that keeps a domain healthy across a year of continuous use.
From there the mailbox count is simple division. Sending 500 emails a day at 40 per mailbox needs 12 to 13 mailboxes. Domains come next. The standard ratio is 2 to 3 mailboxes per domain, so a 500-email day runs on 5 to 6 domains. Put more than 3 mailboxes on a single domain and you concentrate all your sending reputation on one asset. A single spam complaint spree can then take out a third of your daily volume in one hit.
| Target daily volume | Mailboxes needed (~40/day each) | Domains needed (~2-3 mailboxes each) |
|---|---|---|
| 250 emails/day | 6-7 | 2-3 |
| 500 emails/day | 12-13 | 5-6 |
| 1,000 emails/day | 25 | 9-12 |
| 2,000 emails/day | 50 | 17-25 |
Buy 15 to 20% more mailboxes than the math requires. Some will underperform warmup, some will get flagged and need replacing mid-campaign, and reprovisioning from scratch costs you two to three weeks of pipeline every time it happens.
Naming Conventions That Keep You Off Spam Filters
Domains registered in a single batch with sequential or obviously templated names are one of the easier patterns for spam filters and manual reviewers to flag. Avoid anything with "sales," "deals," "offers," or your exact brand name repeated across every domain. A cleaner approach is a small set of natural-sounding variations on your brand or a related term, registered a few at a time rather than all in one afternoon.
Mailbox naming matters just as much. Use real first and last names that match a plausible sender rather than generic addresses like sales@ or info@. Keep the format consistent enough that your team can track which mailbox belongs to which domain internally, but distinct enough on the receiving end that nothing looks assembly-lined. A recipient should never be able to tell they're one of twenty identical-looking senders from the same operation.
Why a Domain Needs to Age Before It Sends Anything
Domain age is one of the reputation signals mailbox providers weigh before anything else happens. A domain registered yesterday and sending cold email today looks exactly like the pattern spammers use, because it is. Hold newly registered domains for at least 2 to 4 weeks before you point DNS at a sending platform or create the first mailbox.
Age alone doesn't replace warmup. It just removes one red flag before you start building the sender reputation signals that actually matter: engagement, reply behavior, and spam complaint rate. Once a domain has aged and DNS is live, run the full domain warmup protocol before any real prospect sees an email from it.
DNS Basics, Briefly
Every domain needs SPF, DKIM, and DMARC configured and verified before it sends a single email. SPF authorizes which servers can send on your behalf, DKIM signs each message so it can't be tampered with in transit, and DMARC tells receiving servers what to do when either check fails. Get any one of them wrong and you cap your deliverability regardless of how good the copy is.
We've written the full setup process, records, host, and common mistakes, in a dedicated guide: SPF, DKIM, and DMARC setup for cold email. Work through that guide domain by domain as you provision, rather than trying to remember the steps from a single read-through.
The Actual Buying and Provisioning Step
Once you know your target count and naming pattern, the buying process itself is mechanical: register the domains, point DNS, and create Google Workspace or Microsoft 365 mailboxes on top. Doing this manually across 10 to 20 domains at a registrar's default checkout flow takes hours and invites exactly the kind of batch-registration pattern that naming conventions are supposed to avoid.
We buy our own mailboxes and domains through Zapmail, which handles bulk domain registration, DNS configuration, and mailbox provisioning as one workflow instead of a dozen separate steps across a registrar, a DNS panel, and an admin console. Whatever provider you use, the sequence stays the same: register, verify DNS, provision the mailbox, then hand it to warmup. Skipping ahead to sending before every domain in the batch has cleared DNS checks is the single most common reason a fresh batch underperforms in week one.
Common Mistakes When Buying Domains and Mailboxes
- Buying exactly the number the math says. No buffer for mailboxes that fail warmup or get flagged mid-campaign, which forces an emergency reprovisioning cycle right when volume needs to be steady.
- Sending the same day a domain is registered. Skips the aging window entirely and starts the domain's reputation history with the worst possible first impression.
- Putting 5 or more mailboxes on one domain. Concentrates risk so heavily that one bad sending day can take a large share of total volume offline at once.
- Copying DNS records across domains without editing the selector. DKIM selectors and SPF includes are often domain-specific. A copy-pasted record that isn't adjusted per domain fails silently until a placement test catches it.
- Treating provisioning as a one-time project. Domains age out, get flagged, or simply wear down in reputation over months of sending. Budget for ongoing replacement instead of assuming a single batch lasts forever.
Want This Handled For You?
Modern Inbound sources, names, ages, and provisions domains and mailboxes as part of managed outbound, so your team gets sending infrastructure that's ready on day one instead of a spreadsheet of DNS records to track.
Frequently Asked Questions
How many domains do I need for cold email?
Plan for roughly one domain per 2 to 3 mailboxes, with each mailbox handling 30 to 50 emails a day. A team targeting 500 emails a day needs about 5 to 6 domains running 12 to 13 mailboxes.
How long should a domain sit before I start sending from it?
Hold a newly registered domain for at least 2 to 4 weeks before connecting DNS and creating mailboxes. After that, run a full 14 to 21 day warmup before any real prospect sees an email from it.
Can I use my main company domain for cold email?
No. Use a separate sending domain so a deliverability problem in your outbound campaign never touches the domain your regular business email relies on.
What's the biggest mistake teams make when buying domains and mailboxes?
Buying the exact number the math requires with no buffer, then sending from every domain the same day it's registered. Both compress your margin for error to zero in the first two weeks.
Should I buy domains one at a time or in bulk?
Bulk provisioning through a dedicated platform is faster and keeps DNS configuration consistent, but stagger the actual registration dates where possible so the batch doesn't read as one obvious purchase event.
Let’s chat about your sales pipeline goals.
A flat tech fee, then pay per positive reply delivered. No long lock-ins.
Apply to work with usRishabh AmbastaFounder, Modern Inbound
Runs a research-led cold email agency measured in delivered replies. Before that, outbound for SaaS teams from $1M to $50M ARR. LinkedIn
Keep reading