This is the cheapest high-impact decision in outbound, it takes an afternoon, and it is almost impossible to fix retroactively.

What is actually at risk

Sender reputation attaches to your domain. Mailbox providers build a picture of it over time from bounce rates, complaint rates, engagement, authentication and sending patterns.

If you run cold outreach from yourcompany.com, every one of those signals is shared with:

  • invoices and payment reminders
  • contracts and proposals
  • support replies to existing customers
  • password resets and account notifications
  • the reply you send to an inbound lead who found you and is ready to buy

A cold campaign to a list that was stale, or to people who did not want it, damages the reputation carried by all of the above. The failure is silent: nothing bounces, nothing errors, your invoices simply start arriving in spam and nobody tells you.

That asymmetry is the whole argument. The upside of using your main domain is that you saved twelve dollars. The downside is that your business mail becomes unreliable and you find out from a customer.

The subdomain trap

The common half-measure is mail.yourcompany.com or outreach.yourcompany.com.

It is better than the root domain, and it is not isolation. Two reasons:

Reputation inherits. Providers do not treat a subdomain as a stranger. Parent-domain reputation informs subdomain reputation and, to a lesser extent, the reverse. Damage bleeds.

DMARC inherits. A DMARC policy on yourcompany.com applies to every subdomain unless you publish a separate record or set the sp tag. People discover this the day they move the parent to p=reject and the subdomain's mail stops.

If the reason for separating is containment, a separate domain contains more. If the reason is organisation, a subdomain is fine.

Choosing the domain

The domain has to look like you, not like a burner.

Good patterns:

  • The .co, .net or .io of your .com
  • getyourbrand.com, tryyourbrand.com, yourbrandhq.com
  • yourbrand-mail.com, yourbrandteam.com

Bad patterns:

  • Random strings or numbers: yourbrand2024mail.com
  • Novelty TLDs with a poor sending reputation
  • Anything unrelated to your brand, which makes your email look like impersonation
  • Expired domains with unknown history, which is a genuine hazard: you inherit whatever the previous owner did

Keep it short and pronounceable. Someone will read it aloud on a call.

Setting it up

1. Register it and point it somewhere real. Redirect the domain to your main website. A sending domain that resolves to nothing, or to a parking page, is a signal.

2. Let it age. Two to four weeks before serious sending. A domain registered on Monday sending cold email on Tuesday is the oldest pattern in spam.

3. Set up SPF, DKIM and DMARC. All three, in that order, with DMARC starting at p=none. See DMARC for cold email for the sequence.

4. Create your mailboxes. Two or three per domain. Use real names: sarah@, not sales@ or info@, which are treated as role accounts and perform worse.

5. Make them look inhabited. Real display name, a proper signature, a profile photo if the provider supports it.

6. Warm up. Two to four weeks minimum before meaningful cold volume, and keep warm-up running afterwards. Reputation decays, and a mailbox whose only traffic is cold outreach has a profile no ordinary mailbox has.

7. Ramp slowly. 10 a day in week one, 20 in week two, 30 to 40 by week four. If bounces or complaints move, stop climbing.

Scaling: more domains, not more volume

Once one domain and its mailboxes are producing, the instinct is to send more from them. The safer move is to add another domain.

Reputation is tracked per identity. Three domains at three mailboxes each, 35 emails per mailbox per day, is roughly 315 a day spread across nine identities. One domain pushing 315 concentrates every bit of that risk in one place.

Spreading also gives you something more valuable than throughput: if one domain gets into trouble, the campaign continues while you deal with it, rather than stopping.

Whatever platform you use should rotate across mailboxes automatically, show health per mailbox, and reroute away from one that starts failing rather than continuing to feed it.

When a domain is damaged

For a dedicated sending domain: retire it. Stop sending, let it go quiet, and start a fresh one with proper warm-up. This is unpleasant but survivable, and it is survivable precisely because it was never your main domain.

For a primary business domain: this is the situation the whole article exists to prevent. Stop all cold sending immediately. Fix authentication. Purge and re-verify your lists. Then wait, because recovery is measured in months of consistent normal behaviour, and it is not guaranteed.

The one-line version

Twelve dollars a year and an afternoon of setup buys you the ability to make a mistake without it reaching your invoices. There is no version of this maths that favours saving the twelve dollars.

Leads Ranger warms every mailbox you connect, audits its DNS in plain English, verifies addresses at send time, and rotates across mailboxes with automatic failover when one falters. Which domain you point it at is still your decision, and it is the one that matters most.