Dedicated Sending Domain for Cold Email: Subdomain or Separate Domain?

Last updated July 2026.

The reason this question matters is not deliverability theory. It is that your primary domain carries things you cannot rebuild in a week: the email your customers reply to, your invoices, your password resets, and the search rankings your marketing site earns. Cold email is the one activity in your company that deliberately sends unsolicited mail to strangers who may mark it as spam. Doing that from the domain your business runs on is a bet with a bad payoff structure.

What is a dedicated sending domain?

A dedicated sending domain is a domain you own and use exclusively for outbound email campaigns, kept separate from the domain that hosts your website and your day-to-day company mail. If your company is at acme.com, a dedicated sending domain would be something like getacme.com or acmehq.com, with mailboxes such as [email protected] sending the campaigns.

The point is reputation isolation. Mailbox providers assign reputation to the domain in the From address and to the domain that signs the message with DKIM. When a campaign goes badly, that reputation absorbs the damage. If the damaged domain is one you bought for $12 and can retire, you have lost $12. If it is acme.com, your invoices start landing in spam.

Should I use a subdomain or a separate domain for cold email?

Use a separate domain. The subdomain approach is popular because it looks like a compromise between brand recognition and safety, and because a lot of vendor content asserts, without a source, that subdomain reputation is evaluated independently. Google's documentation says something different about volume.

Gmail defines a bulk sender as one sending close to 5,000 messages or more to personal Gmail accounts in 24 hours, and states that messages sent from the same primary domain count toward that limit. Google's own worked example: 2,500 messages a day from solarmora.com plus 2,500 a day from promotions.solarmora.com makes you a bulk sender, because all 5,000 came from the same primary domain. The subdomain did not buy a separate identity for that calculation.

That is a volume rule rather than a reputation rule, and it is worth being precise about the difference, because most articles are not. Google does not publish a clear statement that a subdomain's spam complaints are attributed to its parent for reputation purposes. What Google does publish is that the two are treated as one sender when deciding whether the bulk sender requirements apply to you. Everything beyond that is inference from practitioner observation rather than documented policy, and you should treat anyone who states it as settled fact with some suspicion.

Given a rule that demonstrably aggregates and a reputation question the vendor will not answer, the asymmetry decides it. A separate registrable domain removes the question. A subdomain leaves you relying on a behavior nobody has documented.

How many sending domains do I need?

Start with the arithmetic rather than a rule of thumb. A well-warmed mailbox on a healthy domain sends somewhere in the range of 30 to 50 cold emails a day. That is not a platform limit, it is what keeps you inside the behavior mailbox providers consider normal. Two or three mailboxes per domain is the usual ceiling before the domain starts to look like a sending farm.

So a domain carries roughly 60 to 150 cold emails a day. If your target is 300 a day, you need two to three sending domains and six to nine mailboxes. If your target is 1,000 a day, the infrastructure is eight or more domains and twenty-plus mailboxes, and the honest question is whether that volume is a strategy or an admission that the targeting is wrong. Our breakdown of how many cold emails you can send per day works through the per-inbox numbers, and how many email accounts you need covers the mailbox side.

How do I choose a good sending domain name?

The prospect will look at it. A domain that reads as a burner destroys the trust the email is trying to build, so the goal is a name that a person who knows your company would accept as plausibly yours.

What works: a prefix or suffix on your real brand. getacme.com, tryacme.com, acmehq.com, acme.co, acmeteam.com, useacme.com. What fails: hyphens, numbers, unrelated words, and anything that could not appear on a business card. Registrar and TLD matter less than people claim, though the discount TLDs that spammers favor, several of which you can register for under a dollar, carry a reputational tax you do not need to pay. Stick to .com or .co.

Then make the domain look real. Put a one-page site on it that redirects to your main site or at minimum explains who you are. Set up the MX records so replies arrive. Fill in the mailbox display names properly. A domain with no website, registered three days ago, sending to strangers, is the exact profile filters are built to catch.

Do I need SPF, DKIM, and DMARC on a sending domain?

Yes, on every one of them, before a single campaign email leaves. Since February 2024 Google and Yahoo require SPF, DKIM, and DMARC from bulk senders, and DMARC must be published with at least a p=none policy. Google's guidance for all senders, bulk or not, is to keep the spam rate reported in Postmaster Tools below 0.10% and never to reach 0.30%.

Those complaint thresholds are the reason domain isolation matters so much. Cold email produces complaints even when it is done well, because some percentage of strangers will always hit the spam button rather than the unsubscribe link. A rate that would be catastrophic for a transactional domain is an ordinary Tuesday for a cold outreach domain. Separating them means the two never share a score. Setting the records up is mechanical, and we walk through it in SPF, DKIM, and DMARC for cold email.

How long should I warm up a new sending domain?

Two to three weeks before it carries a real campaign, and the first week should be almost entirely conversational mail rather than outreach. A domain registered yesterday has no sending history, and mailbox providers treat volume without history the way a bank treats a large wire from an account opened this morning.

Warmup means starting at a handful of messages a day, ramping gradually, and generating replies, because a reply is the strongest positive signal a mailbox provider can observe. Most platforms automate this with a warmup network. The mistake that undoes it is ramping to full campaign volume the day the warmup tool says the domain is ready. Give it a week at half volume first. Warming up an email domain covers the schedule in detail, and the warmup calculator will do the ramp arithmetic for you.

Can I reuse a burned sending domain?

Sometimes, and rarely worth it. Domain reputation recovers slowly, over months of good behavior at low volume, and you are rebuilding a signal on a domain that mailbox providers already have a negative opinion of. The alternative costs about twelve dollars and two weeks of warmup.

Retire the domain, keep the mailboxes alive long enough to catch replies to campaigns already in flight, and diagnose what went wrong before you point campaigns at the replacement. If you burned a domain through bad targeting or unverified lists, a fresh domain will burn identically. Run an email deliverability audit first.

The setup that works

Keep acme.com for the business. Register two to three lookalike domains, put a simple page on each, configure SPF, DKIM, and DMARC before anything sends, create two or three mailboxes per domain, warm each for two to three weeks, then run campaigns at 30 to 50 emails per mailbox per day with verified addresses and stop-on-reply follow-ups. Watch the spam rate in Postmaster Tools and treat 0.10% as the line, not 0.30%.

ColdMailer connects unlimited mailboxes over your own SMTP, checks SPF, DKIM, and DMARC on every sending domain you add, warms new domains before they carry campaign traffic, and spreads volume across mailboxes automatically so none of them looks like a bulk sender. The infrastructure discipline is the product. See cold email deliverability for how the pieces fit together.