Reputation is attached to the domain, not the address
The instinct behind "just use one email address" is that an address feels like a single, controllable thing. It isn't, not to Gmail, Yahoo, or Outlook. Those providers score the sending domain's reputation (and the top-level organizational domain behind any subdomain). sales@yourco.com and hello@yourco.com draw from the same reputation pool. If one torches it, both suffer.
This is the whole game. A spike in spam complaints or bounces on any address at yourco.com can quietly degrade inbox placement for every other address on yourco.com, including the invoice your customer is now waiting on in their spam folder. So "one handle vs. separate handles" is the wrong framing. Two handles on the same domain are, for reputation purposes, basically one. The real lever is the domain or subdomain the mail is authenticated from.
The three jobs of email are three different risk classes
Email does three jobs, and they carry wildly different risk:
- Transactional, receipts, password resets, order confirmations, booking notifications. Highest trust, highest stakes. Recipients expect these and almost never complain. If one lands in spam, you have a real business problem.
- Marketing / opt-in, newsletters, promotions, nurture sequences to people who subscribed. Medium risk. Even with a clean list, some recipients forget they signed up and hit "spam." Complaints are normal and cumulative.
- Cold outreach, one-to-one sales or link-building email to people with no prior relationship. Highest risk by far. There is no engagement history holding you up; cold mail lives or dies on sender reputation, and a bad list produces complaints and spam-trap hits immediately.
Mixing these on one domain means your most fragile, highest-stakes mail shares a reputation score with your most reputation-hostile activity. That is the mistake: you let the riskiest thing you do set the ceiling for the most important thing you do.

When a single domain is actually fine
Not everyone needs a sprawl of domains. If you are a solo operator or small business that only sends one-to-one human email (replies, quotes) and a modest opt-in newsletter to people who clearly asked for it, sending both from your primary brand domain is reasonable. Volume is low, complaints are rare, and the simplicity is worth more than marginal isolation. Keep SPF, DKIM, and DMARC configured and you are fine.
The single-domain approach breaks the moment you add cold outreach or start sending marketing at real volume. That is when you need to split.
The architecture: isolate by risk
Here is the structure we recommend, from safest to most aggressive:
| Mail type | Send from | Why |
|---|---|---|
| Transactional | Primary domain or dedicated subdomain (mail.yourco.com) | Must always inbox; isolate from marketing complaint noise |
| Marketing / newsletters | Subdomain of primary (news.yourco.com) | Partial isolation; keeps opt-in complaints off transactional reputation while staying on-brand |
| Corporate / 1:1 | Primary domain (yourco.com) | Your real human identity; protect it |
| Cold outreach | Separate domains entirely (tryyourco.com) | Full isolation; the only safe home for no-relationship mail |
Two principles make this work. First, subdomains give partial isolation; separate domains give full isolation. Second, never mix sending types on the same identity, cold outreach, marketing, and transactional each get their own home.
Why a subdomain is not enough for cold outreach
This is the most common and most expensive myth: "I'll run cold email from outreach.yourco.com, so my main domain is safe." It isn't, not fully. Mailbox providers associate a subdomain with its parent organizational domain. A subdomain inherits some of the parent's reputation history, and, the part that hurts, a badly behaving subdomain can bleed damage back to the parent. Subdomains contain damage; they are not a firewall.
There is a second, concrete trap: for the purpose of deciding whether you are a "bulk sender," mail from a subdomain counts toward the primary domain's volume. So the subdomain doesn't even give you a clean separate volume ledger. For genuinely high-risk mail like cold outreach, the only safe choice is a completely separate domain that carries none of your brand's trust and can't drag your brand down with it. A subdomain is the right tool for separating marketing from transactional within your brand. It is the wrong tool for cold outreach.
How to run separate domains for cold outreach
If you are doing outbound at scale, the standard, deliverability-safe setup looks like this:
- Buy lookalike domains close to your brand but clearly separate (
tryyourco.com,getyourco.com,yourcohq.com). Redirect them to your main site so links resolve to your real brand. - Authenticate each one, every sending domain needs its own SPF, DKIM, and DMARC records. Authentication is per-domain; a new domain starts from zero.
- Warm up slowly. New domains start at roughly 5 to 10 emails per day per mailbox and ramp over 2 to 6 weeks. Skipping warmup is the fastest way to get blocklisted.
- Cap volume per mailbox, on a warmed domain, keep cold sends to roughly 20 to 50 per mailbox per day. Pushing a single inbox higher is how you get flagged.
- Scale horizontally, not vertically. Add mailboxes and domains instead of cranking one inbox. A common structure is 4 to 5 sending domains with 4 to 6 mailboxes each, which limits the blast radius if one domain develops a deliverability problem.
The whole philosophy is blast-radius management: assume any given outreach domain will eventually get burned, and arrange things so that when it does, it takes nothing important with it.
The 2024 to 2025 rules you can't ignore
The ground shifted under email in the last two years. Google and Yahoo began enforcing new bulk sender requirements in February 2024, and Microsoft followed for Outlook, Hotmail, and Live in May 2025. If you cross the threshold, these are non-negotiable:
- Threshold: "bulk sender" means 5,000+ emails per day to that provider's users, defined by volume, not type. An app sending only password resets can cross it.
- SPF and DKIM. All senders should have one; bulk senders must have both.
- DMARC. Publish a policy (at minimum
p=none), and your visibleFrom:domain must align with the domain authenticated by SPF or DKIM. - One-click unsubscribe. Bulk marketing mail must support RFC 8058 one-click unsubscribe via the
List-Unsubscribeheader. - Spam complaint rate under 0.3%, and aim well below, ideally under 0.1%.
Two implications for the "how many domains" question: authentication and these thresholds are evaluated per sending domain or subdomain, so each identity is its own setup job; and because subdomain volume rolls up to the organizational domain, splitting marketing onto news.yourco.com isolates reputation but does not reduce your bulk-sender obligations on yourco.com.
A simple decision guide
- Solo / tiny list, no cold outreach: one brand domain is fine. Set up SPF/DKIM/DMARC and move on.
- Sending real marketing volume: move newsletters to a subdomain (
news.yourco.com); keep transactional on the primary domain ormail.yourco.com. - Doing any cold outreach: buy separate domains for it. Never run it from your primary domain or a subdomain of it. Warm up, cap volume, spread across multiple domains and mailboxes.
- Crossing 5,000/day to any provider: treat bulk-sender compliance as mandatory on every sending identity, transactional included.
The organizing idea is not "more domains is better." It is match the isolation to the risk. Your transactional mail and your cold outreach should never be able to hurt each other, because one is the mail your business runs on and the other is the mail you are willing to lose.
Our Research On This
Original SEMPITE studies, live queries, recorded answers, named sources. Free to cite under CC BY 4.0.
- Who AI Cites When Readers Ask What to Read Next, 0/95 AI book citations that went to author sites
- Google’s AI Knows This Working Actress in Detail, 80% of casting answers cite IMDb
- Decline, Fabricate, or Retrieve, 0/7 working actors ChatGPT would describe
SEMPITE helps small businesses and personal brands get found, in search and in AI answers.
Get Your Brand Audit →Frequently Asked Questions
Can I just use one email address for everything?
For reputation purposes, two addresses on the same domain behave like one, because Gmail, Yahoo, and Outlook score the domain, not the inbox. A single domain is fine for a small sender doing only 1:1 mail and a modest opt-in newsletter. It becomes risky the moment you add cold outreach or high-volume marketing, because the riskiest mail then shares a reputation score with the mail that must always land.
What is the difference between cold outreach and email marketing?
Cold outreach targets people with no prior relationship, usually sent one-to-one with a single ask. Email marketing goes to a list that opted in, typically from a platform with templates and tracking. The rules differ: marketing relies on consent and engagement, while cold outreach lives or dies purely on sender reputation, which is why it needs its own separate domains.
Does a subdomain protect my main domain from cold-email damage?
Only partially. Mailbox providers link a subdomain to its parent organizational domain, so a subdomain inherits some parent reputation and can bleed damage back to it. Subdomains contain damage but aren't a firewall. For cold outreach specifically, use a completely separate domain, and reserve subdomains for separating marketing from transactional within your brand.
How many cold emails can I send per day per mailbox?
Estimates vary by vendor, but the conservative consensus is roughly 20 to 50 per mailbox per day on a fully warmed domain. New domains should start at about 5 to 10 per day and ramp over 2 to 6 weeks. Scale by adding mailboxes and domains, commonly 4 to 5 domains with 4 to 6 mailboxes each, rather than pushing one inbox higher.
Should transactional and marketing email be separated?
Yes. Marketing draws more spam complaints than transactional mail, and those complaints degrade the reputation your receipts and password resets depend on. Keep transactional on your primary domain or a dedicated subdomain like mail.yourco.com, and move marketing to its own subdomain like news.yourco.com so complaint noise can't follow your most important mail into the spam folder.
What are the 2024 to 2025 bulk sender requirements?
Google and Yahoo (enforcing since February 2024) and Microsoft (since May 2025) require senders of 5,000 or more emails per day to a provider to authenticate with SPF and DKIM, publish an aligned DMARC policy, support one-click unsubscribe on bulk mail, and keep spam complaint rates under 0.3%. Bulk is defined by volume, not type, so transactional mail can trigger it too.
Do separate domains need their own email authentication?
Yes. SPF, DKIM, and DMARC are configured per domain, and a brand-new outreach domain starts with zero reputation and no records. Every sending domain and subdomain you add is its own authentication setup, so plan for that overhead when you decide how many identities to run.
Leave a Comment
Have a question or something to add? Drop a comment below.