Cold Email Domain Setup: Domains, Inboxes, and Warmup Done Right

Cold Email Domain Setup, Explained the Way You Wish Someone Had Told You

Most cold email problems are not copy problems. They are infrastructure problems. If your domains are not separate from your main one, your records are wrong, or you skipped warmup, the best email in the world still lands in spam. So before you write a single line, get the cold email domain setup right. This guide walks the whole thing step by step: buy separate sending domains, set SPF, DKIM, and DMARC, create inboxes, warm them, and forward them back to your root.

None of this is hard. It is just specific, and the order matters. Do it in sequence and you build sender reputation that protects your brand and lands you in the inbox. Skip a step and you spend weeks wondering why nobody replies.

Why You Need Separate Sending Domains (Never Your Primary)

Your primary domain runs your business. It sends invoices, password resets, support replies, and marketing. Every one of those depends on a clean sender reputation. Cold outreach, by definition, goes to people who never asked to hear from you. Some will mark it as spam. A few addresses will be dead or spam traps. That is normal for outbound, and it is exactly why you never point it at the domain you cannot afford to burn.

Instead, register dedicated sending domains that look and feel like your brand but live separately. If your company is at acme.com, buy variations like getacme.com, tryacme.com, acmehq.com, or acme-mail.com. Three rules keep these clean:

• Stay on brand. The domain should be obviously you. On-brand domains read as legitimate and protect open and reply rates.
• Avoid hyphens and numbers where you can. They look spammy and get mistyped. A clean prefix like "get" or "try" beats a string of dashes.
• Keep your real site untouched. The sending domains carry the risk. Your primary stays pristine.

This is the single most important decision in the whole process. Get it right and a bad week on a sending domain never touches your core business. This is also why, at Snipe Outbound, we send every client campaign from dedicated warmed domains and never the client's own.

How Many Domains and Inboxes Do You Actually Need?

This is the question everyone asks, so here is the honest answer with the math, framed as what good looks like rather than a guarantee.

Experienced outbound teams cap cold sends at roughly 20 to 30 emails per inbox per day. Not because your provider blocks more, but because low, steady, human-looking volume is what keeps a new sender trusted. You also want two to three inboxes per domain to spread sending and avoid leaning on one address.

So the planning works backward from your daily target:

1. Decide your daily send volume. Say you want to reach 300 fresh prospects a day.
2. Divide by per-inbox capacity. At 25 sends each, that is 12 inboxes.
3. Group into domains. At three inboxes per domain, that is 4 domains.
4. Add a buffer. Keep a spare domain or two warming in reserve so one flagged domain never stalls the whole campaign.

Here is a quick reference for common targets. Treat these as a sane starting point, not a hard rule.

Daily prospects	Inboxes (≈25/day)	Domains (3 inboxes each)
100	4	2
200	8	3
300	12	4
500	20	7

The principle behind the table is simple: distribute reputation risk. Many small, well-warmed inboxes beat a few inboxes pushed hard. If one gets flagged, the rest keep running and your pipeline does not flinch.

Set SPF, DKIM, and DMARC Before You Send Anything

Authentication is how inbox providers confirm your mail is really from you and not a spoof. Without it, even a warm domain struggles. Three records do the heavy lifting, and you add them in your DNS settings at the registrar or wherever your domain is hosted.

SPF (Sender Policy Framework)

SPF is a single TXT record that lists which servers are allowed to send on behalf of your domain. When a receiving server gets your email, it checks the sender against this list. If your sending provider is not authorized, the message looks forged. Use the exact SPF value your email provider gives you, and keep it to one SPF record per domain.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to every message. The receiving server uses a public key published in your DNS to verify the email was not tampered with in transit and genuinely came from your domain. Your provider generates the key and tells you the exact record to paste in. This one matters a lot for trust.

DMARC (Domain-based Message Authentication)

DMARC ties SPF and DKIM together and tells receiving servers what to do if a message fails both. Start with a gentle monitoring policy so you can watch results without blocking your own mail, then tighten it once everything passes cleanly. A basic record looks like v=DMARC1; p=none; rua=mailto:you@yourdomain.com.

You will also need your MX records pointed at your email provider so mail can be received, which matters for forwarding and replies. Once these are live, give DNS a few hours to propagate, then verify. We built a free cold email grader and a spam checker so you can confirm your setup and copy will actually land before you scale. If you want the deep version of this section, our cold email deliverability guide goes record by record.

Create Your Inboxes the Right Way

With records in place, create the mailboxes. For B2B, Google Workspace and Microsoft 365 are the most trusted providers, and a mix of both can help you reach recipients on either platform. A few specifics make a real difference:

• Use real human names. firstname@getacme.com beats sales@ or info@. People reply to people.
• Set a profile photo and full display name. A real face and name read as legitimate and lift trust.
• Fill in the signature. Name, title, company, and a link. Sparse, honest signatures outperform busy ones.
• One persona per inbox. Keep each mailbox tied to a consistent sender identity so your warmup and sending behavior look human.

Two to three inboxes per domain, each a believable person, gives you room to scale volume without ever overloading a single address.

Warm Up Every Inbox Before It Touches a Prospect

Warmup is the process of gradually increasing activity on a new mailbox so inbox providers learn to trust it. Skipping warmup is the most common reason new cold email campaigns fail. A brand-new domain that suddenly blasts 200 messages looks exactly like a spammer, because that is what spammers do.

Good warmup ramps slowly and leans on engagement, not just volume. The signals that build reputation are opens, replies, and messages getting moved out of spam into the inbox. Here is a sensible ramp:

• Week 1: start low, around 5 to 10 sends per inbox per day, with warmup tools exchanging and replying to mail.
• Weeks 2 to 4: increase steadily, adding roughly 5 to 10 a day, watching that replies and inbox placement stay healthy.
• Weeks 4 and beyond: reach your target of 20 to 30 per inbox per day once engagement holds.

Plan for three to six weeks of warmup before real sending, and keep a light warmup running in the background even after you go live. It maintains reputation the same way regular exercise maintains fitness. Sudden spikes are the enemy. Steady is the goal.

Forward Your Sending Domains to Your Root

One step people forget: set up a redirect so each sending domain forwards to your primary website. When a curious prospect types getacme.com into their browser, they should land on acme.com, not a blank page or a parked-domain ad. This is a simple domain forward or 301 redirect you configure at your registrar or host.

It matters for two reasons. First, it looks legitimate, which reinforces trust. Second, a sending domain with no working website is a small red flag to both prospects and filters. The fix takes minutes and closes the loop on a setup that otherwise looks complete.

The Cold Email Domain Setup Checklist

Run this in order. Each row depends on the ones above it.

Step	What to do	Why it matters
1. Buy domains	Register on-brand variations, not your primary. No hyphens or numbers.	Protects your core domain from any outbound risk.
2. Add MX	Point MX records at your email provider.	Lets your domains receive mail and replies.
3. Set SPF	Publish one TXT record authorizing your sender.	Proves your mail is from an allowed server.
4. Set DKIM	Add the signing key from your provider.	Verifies the message was not altered.
5. Set DMARC	Start at p=none, then tighten.	Tells servers how to handle failures.
6. Create inboxes	2 to 3 real-name mailboxes per domain, with photo and signature.	Spreads volume and reads as human.
7. Warm up	Ramp over 3 to 6 weeks via a warmup tool.	Builds the reputation that lands you in inbox.
8. Forward to root	Redirect each sending domain to your primary site.	Looks legitimate to prospects and filters.
9. Verify	Test records, placement, and copy before you scale.	Catches problems before they cost you replies.

Once this is done, the rest of your program has a foundation to stand on. Clean infrastructure makes good targeting and good copy actually count. To go further upstream, see how to build a B2B prospect list and grade it with our list grader so you only send to addresses worth the reputation you just built.

When to Build This Yourself, and When to Hand It Off

If you are running one or two domains and have time to manage DNS, warmup, and monitoring, building this in-house is entirely reasonable. The steps above are the whole job. Be honest about the ongoing part, though. Domains need monitoring, inboxes drift, warmup has to keep running, and one misconfigured record can quietly sink a campaign for weeks before you notice.

That maintenance load is where a lot of founders decide it is not worth their team's hours. At Snipe Outbound, this is what we run every day. We set up signal-based targeting, send from dedicated warmed domains that are never your own, write per-prospect researched copy, and run an AI SDR that books and follows up, all aimed at putting qualified demos on your calendar. If you would rather skip the setup and the babysitting and just get meetings, book a call and we will show you exactly how we would run it for you.