Most teams blame the subject line when a cold campaign goes quiet. Far more often the real problem sits underneath: a domain with no authentication, one inbox sending 200 emails a day, or a brand new domain that never warmed up. Gmail and Outlook decide where an email lands before anyone reads it, and that decision is mostly about the sender.
This guide explains what cold email infrastructure is, what each part does, and how to size it for the volume you want to send.
What is cold email infrastructure?
Cold email infrastructure is the technical setup that sends your outreach and shapes its reputation. It has six parts that work as a chain. If one link is weak, the whole chain suffers.
- 1
Sending domains
Separate from your main domain
- 2
DNS records
SPF, DKIM, DMARC, MX
- 3
Inboxes
Google or Microsoft
- 4
Warm-up
Builds sending history
- 5
Sending tool
Limits and rotation
- 6
Monitoring
Bounces, spam, blocklists
Why infrastructure decides your results
Every receiving server asks the same questions about each email: is this sender who they claim to be, have they behaved well before, and do people want their mail? Authentication answers the first. Domain age, warm-up and sending history answer the second. Bounce and complaint rates answer the third.
The rules have also become stricter. Since February 2024, Google’s email sender guidelines and Yahoo’s sender best practices require bulk senders to authenticate with SPF, DKIM and DMARC and to keep spam complaints low. Microsoft introduced similar requirements for high volume senders to Outlook.com in 2025. Cold email teams sending across many inboxes are exactly who these rules are written for.
The six components
1. Sending domains
Never send cold email from the domain your team uses every day. Buy separate domains that look like your brand, such as getnorthwind.com or trynorthwind.com for northwind.com. If one runs into trouble, your main domain and the rest of your setup stay safe. Point each one at your website so curious prospects land somewhere real. Our sending domains page covers naming in more detail, and main domain vs sending domains explains the difference.
Separate domains or subdomains? Some teams send from a subdomain such as outreach.northwind.com. It is cheaper, but a subdomain still shares part of its reputation with the main domain, so a problem can spill over to the email your company relies on. Separate domains keep the risk fully apart, which is why we use them for every order. Buy them in a batch, and buy a few more than you need so you can rest a domain without slowing your campaigns.
2. Inboxes
Each domain carries a few real mailboxes, usually from Google Workspace or Microsoft 365. Many teams use both, matching Google inboxes to prospects on Gmail and Microsoft inboxes to corporate prospects on Outlook. We recommend 3 inboxes per domain, which spreads volume and limits the damage if one domain slips.
3. DNS authentication
Four records prove your emails are legitimate:
- SPF lists the servers allowed to send for your domain.
- DKIM signs each email so receivers can check it was not altered.
- DMARC tells receivers what to do when SPF or DKIM fail, and where to send reports.
- MX lets the domain receive replies, which receivers expect from a real sender.
Our SPF, DKIM and DMARC setup guide shows the exact records for Google and Microsoft. You can check any domain with MXToolbox or the Google Admin Toolbox Check MX.
4. Warm-up
A new inbox has no history, and sudden volume from a stranger looks like spam. Warm-up sends small, growing amounts of email that get opened and replied to, which builds a positive record. Plan on a full 30 days before your first campaign, and keep warm-up running at a low level afterwards.
5. Sending limits and rotation
Google Workspace allows up to 2,000 emails a day per user, but that is a ceiling, not a target. For cold email we recommend 25 to 30 a day per inbox once the 30-day warm-up is done. Your sending tool spreads each campaign across all your inboxes, so no single one stands out.
6. Monitoring
Watch bounce rates per domain and keep them under 2%. Register your domains with Google Postmaster Tools to see spam rates and reputation at Gmail, and use Microsoft SNDS for Outlook data. Check domains against blocklists with the Spamhaus reputation checker. Our deliverability guide lists the warning signs to look for.
Cold email infrastructure vs email marketing
Newsletters and cold outreach both send email, but they need very different setups.
| Email marketing | Cold email | |
|---|---|---|
| Who receives it | People who opted in | Prospects who have not heard from you |
| Sends from | A marketing platform on your main domain | Real inboxes on separate domains |
| Volume per sender | Thousands at once | 25 to 30 per inbox a day |
| Looks like | Designed newsletter | A plain personal email |
| Scales by | Bigger sends | More inboxes and domains |
How much infrastructure do you need?
Work backwards from your daily sending target:
- Divide the emails you want to send each day by 30 to get the number of inboxes.
- Divide the inboxes by 3 to get the number of domains.
- Add about 20% spare so you can rest an inbox without slowing down.
For example, 1,500 emails a day needs 50 inboxes on about 17 domains. With Google Workspace inboxes at $3 each and domains at $12 a year, that is a predictable monthly cost you can plan around. Try your own numbers in our pricing calculator.
A healthy setup at a glance
Whatever your volume, these are the numbers to aim for and to keep checking every week:
| Measure | Target |
|---|---|
| Inboxes per domain | 3, never more than 5 for Google or Microsoft |
| Cold emails per inbox a day | 25 to 30 after warm-up |
| Warm-up before the first campaign | 30 days |
| Bounce rate | Under 2% |
| Spam complaint rate | Under 0.1%, and never above 0.3% |
| DNS records | MX, SPF, DKIM and DMARC on every domain |
If any of these drift, fix the cause before adding volume. More inboxes on a setup that is already struggling only spreads the problem.
Common mistakes that send cold email to spam
- Sending from the main domain. One bad campaign can hurt the email your whole company relies on.
- Skipping DMARC. Google and Yahoo now expect it, and missing it is an easy reason to filter you.
- Launching without warm-up. Brand new inboxes sending 100 emails on day one look exactly like spammers.
- Too many inboxes per domain. Ten inboxes on one domain means one domain carries all the risk.
- Unverified lists. High bounce rates tell providers you do not know who you are emailing.
- Heavy tracking and links. Open tracking pixels, images and several links make a cold email look like marketing.
Build it yourself or have it built
You can build all of this yourself. For a handful of domains it is a few evenings of work: buying domains, creating workspaces and users, adding DNS records, checking them, and preparing an import file for your sending tool. At 20 or more domains the time adds up, and a single typo in an SPF record can quietly undo the rest.
That is the work we do every day with our done-for-you cold email infrastructure setup. You choose your inboxes, domains and sender names, and we set up the records, check every inbox by hand and hand you a CSV for Instantly, Smartlead or any other tool. See how it works, or read our step-by-step guide to setting up cold email infrastructure yourself.
Frequently asked questions
What is cold email infrastructure?
It is the technical setup behind cold outreach: sending domains, inboxes on those domains, DNS records such as SPF, DKIM and DMARC, warm-up, and the sending limits and monitoring that keep each inbox healthy.
How many inboxes do I need for cold email?
Divide your daily sending target by 25, the safe end of 25 to 30 emails per inbox. For 1,500 emails a day you need about 60 inboxes, which at 3 inboxes per domain is 20 domains.
Can I send cold email from my main domain?
You should not. Cold email carries more risk of spam complaints and bounces. Separate sending domains protect your main domain, so your everyday email keeps reaching the inbox.