Recap
- Never run cold email from your main domain. A reputation hit there damages every email your business sends, not just the cold ones.
- Buy a separate sending domain that looks like your brand, then point it back to your real site with a redirect.
- Run two or three mailboxes per domain, and add more domains as you scale rather than piling mailboxes onto one.
- Every sending domain needs SPF, DKIM, and DMARC, plus a warmup period before you send real volume.
Send cold email from a separate domain, not your main one. The reason is simple and unforgiving. Mailbox providers score the reputation of the domain you send from, and that score is shared across everything. If cold outreach drags it down, your invoices, password resets, and replies to real customers start landing in spam too. A dedicated sending domain isolates that risk so a bad outreach week never poisons the email your business actually depends on.
Why does cold volume put my main domain at risk?
Cold email gets complaints. People mark it as spam, some addresses bounce, and a few report it. Those signals attach to the sending domain and lower its reputation. Your main domain carries your transactional mail and your real conversations, so if it inherits cold-email damage, the cost is everything, not just a few lost prospects. You cannot un-ring that bell quickly.
Reputation also does not reset on a schedule. A domain that earns a bad name can take weeks of clean sending to recover, and sometimes it does not fully recover at all. That is a fine gamble on a throwaway domain. It is a terrible one on the domain your customers email back.
What is the dedicated sending domain setup?
The pattern is a separate domain that mirrors your brand, sends all your cold outreach, and redirects to your real website. If your company lives at acme.com, you might buy acmehq.com or getacme.com, send from there, and set a 301 redirect so anyone who types or clicks the domain lands on acme.com. Recipients see a name they trust, and your real domain never touches the cold stream.
Within that domain you can also send from a subdomain such as mail.acmehq.com or go.acmehq.com to keep the cold-send identity tidy. The key idea is separation. The cold domain absorbs the risk, the redirect preserves trust, and your main domain stays clean.
How many domains and mailboxes should I run?
Start with one sending domain and two or three mailboxes on it. Each mailbox should send a modest daily volume, ramped up slowly during warmup. When you need more capacity, add domains rather than stacking ten mailboxes onto one, because dense mailbox clusters on a single domain look like a spam operation and concentrate your risk in one place.
A rough guide as you scale:
| Daily cold sends | Sending domains | Mailboxes |
|---|---|---|
| Up to 50 | 1 | 2 |
| 50 to 150 | 1 to 2 | 3 to 5 |
| 150 to 400 | 2 to 4 | 6 to 10 |
| 400 plus | 4 or more | 2 to 3 per domain |
Treat these as starting points, not laws. The principle holds at every level. Spread volume across domains, keep each mailbox sane, and never let one domain carry your whole pipeline.
How do I authenticate and warm a sending domain?
Every sending domain needs three DNS records before it sends anything real. SPF lists the servers allowed to send for the domain. DKIM signs each message so the receiver can verify it was not tampered with. DMARC tells receivers what to do when a message fails those checks, and it gives you reporting. Since the 2024 Google and Yahoo bulk sender requirements, mail without proper authentication gets filtered or bounced, so this is not optional.
Then comes warmup. A brand-new domain has no reputation, and sending hundreds of cold emails on day one is the fastest way to get flagged. Ramp slowly over a few weeks, start with low daily volume to engaged contacts, and let providers learn that your mail is wanted before you scale up.
What are the tradeoffs of going dedicated?
It is more work. You buy and configure extra domains, set up DNS records for each, warm them, and watch their reputation over time. There is also a small honesty point worth naming. A redirect domain is a slight remove from your primary brand, so you want it to clearly read as you, not as a stranger. Done well, recipients never feel misled.
The upside is that the downside is contained. A burned sending domain is an annoyance you can retire and replace. A burned main domain is a business problem. That trade is lopsided in your favor, which is why every serious outbound team runs this way.
How do I keep this from becoming a chore?
The honest answer is that managing domains, mailboxes, authentication, warmup, and reputation by hand gets tedious fast, especially once you are running several domains at once. This is the layer an autonomous GTM operator like LaunchSurface handles for you, spreading sends across healthy inboxes and pulling back automatically when bounces or complaints climb. However you do it, the rule does not change. Keep cold volume off the domain your business runs on, authenticate everything, and grow capacity by adding domains, not by overloading one.