Send cold outreach from a separate domain, not your main one

The mistake that ends worst is running cold email from your company's main domain. One careless campaign, and the domain your invoices, contracts and support run on is the one in the spam folder.

Reputation attaches to the domain

Mailbox providers judge the sending domain, and that judgement covers every email from it. A cold campaign that draws complaints or bounces damages the reputation of the whole domain, not just the campaign.

If that domain is also your primary one, the damage hits the mail your business depends on: replies to customers, notifications, everything. That is a risk not worth taking with your main identity.

A separate domain contains the risk

Send cold outreach from a dedicated domain and any reputation damage stays contained there. Your primary domain, and the critical mail it carries, is insulated from whatever happens to a campaign. The outreach domain becomes something you can afford to lose; the main one is not.

Use a close, credible variant

The separate domain should still look like you. A close variant of your main domain, the sort a recipient reads as legitimately yours, keeps trust while isolating risk. It should not look like a throwaway, because a strange, unrelated domain undermines the credibility the email needs.

Authenticate and warm it properly

A fresh domain has no reputation, which is a clean slate, not a free pass. Set up SPF, DKIM and DMARC before sending, and warm it up gradually so it does not look like spam software the day it starts. Skipping either wastes the protection the separate domain was meant to provide.

Scale with domains and mailboxes, not volume

The same logic extends to scaling. Rather than pushing ever more volume through one outreach domain, serious senders add mailboxes and sometimes additional domains, keeping each within safe limits. It spreads risk and protects sending volume from concentrating into a single point of failure.

The setup that protects you

A dedicated, close-variant domain, authenticated and warmed, sending within safe limits, kept separate from the mail your business runs on. It is a small amount of setup that prevents the single most damaging deliverability mistake in outbound.

Setting up a sending domain, step by step

1. Register the variant domain. Something a recipient reads as yours: try-yourbrand, yourbrand-hq, getyourbrand. Avoid hyphens stacked with numbers, which pattern-match to spam.
2. Redirect it to your main site. A prospect who types the domain into a browser should land on your real website. An empty page erodes the trust the variant was chosen to keep.
3. Publish SPF, DKIM and DMARC before the first send. Unauthenticated mail from a fresh domain is filtered aggressively, and Google and Microsoft now require authentication from bulk senders outright.
4. Create 2-3 mailboxes on the domain. Real names, real photos where possible. More mailboxes per domain concentrates risk instead of spreading it.
5. Warm up for 2-4 weeks. Low volume, gradually increasing, with genuine engagement. Only then move to campaign sends.
6. Cap the volume. Practitioners generally keep each mailbox between 20 and 50 cold sends per day. Past that, the risk curve steepens fast regardless of how good the copy is.

How many sending domains you need

Work backwards from your target volume. At 2-3 mailboxes per domain and 20-50 daily sends per mailbox, one domain safely carries somewhere between 40 and 150 cold emails a day. A campaign that needs 300 emails a day therefore needs 3-4 domains rotating, not one domain pushed harder. The arithmetic, and how to plan it before you buy anything, is covered in how many mailboxes you need and inbox rotation at scale. Buy the domains at the start rather than mid-campaign, because every new domain restarts the warm-up clock.

Common sending domain mistakes

• Sending from the new domain on day one. A domain with no history that starts at 200 emails a day looks exactly like spam infrastructure. Fix: warm up first, always.
• Buying a batch of domains from one registrar in one hour. Bulk-registered lookalike domains are a known spam fingerprint. Fix: vary registration timing where you can, and use realistic variants.
• Forgetting DMARC alignment. SPF and DKIM that pass but do not align with the From domain still fail DMARC. Fix: verify alignment with a test send, not just the DNS records.
• Ignoring the domain after launch. Reputation moves. Fix: watch bounce rates, spam-folder placement and blacklist status weekly, as part of routine deliverability monitoring.
• Letting the domain expire mid-relationship. Prospects reply to old threads months later. Fix: auto-renew every sending domain and keep the mailboxes alive.

"Doesn't a lookalike domain seem like phishing?"

A fair worry, and the answer is in the execution. A phishing domain hides who is behind it. A legitimate sending domain does the opposite: it redirects to your real site, carries your real name and signature, authenticates cleanly, and states your company details in the footer. Recipients rarely inspect the domain at all; filters do, and filters care about authentication and behaviour, not the name itself. In Europe this transparency is not optional anyway. GDPR-clean outreach means the recipient can always see who is writing, from what company, and how to opt out, whichever domain carries the message. Done that way, the separate domain protects both sides: your business mail stays safe, and the recipient still knows exactly who they are talking to.