Using a separate domain for outreach email
A separate outreach domain needs its own SPF, DKIM and DMARC, exactly like your main domain, and it starts with no sending history at all. It keeps your outreach tools and DNS changes apart from the mail your business depends on, such as staff mailboxes and invoices. It doesn't hide who's sending, and it doesn't let you send more than your list quality supports.
The common pattern goes wrong in a predictable way. A team registers example.net for sales, connects a mailbox and a sending tool, and stops there: no DMARC record, no reports, sometimes no DKIM. The domain then misses provider requirements, it's easy to spoof, and nobody can see what's happening to its mail.
Subdomain or separate domain: what changes
A subdomain such as outreach.example.com falls under your main domain's DMARC record unless it publishes its own. The sp tag on the parent record sets the policy for subdomains; without sp, the parent's p applies. That's convenient, but it also means a strict parent policy applies to outreach mail as soon as you send it. Subdomain policy (sp) explains sp, and Subdomain policy is not doing what we expected covers what to check when a subdomain policy behaves unexpectedly.
A separate registered domain such as example.net inherits nothing from example.com. It needs its own SPF, its own DKIM keys and its own DMARC record.
Whichever you pick, recipients see the From domain. A domain that looks like your brand but isn't obviously connected to it can confuse people and look like phishing. Keep the link visible: the same company name in the From name, a website on that domain or a clear link to your main one, and the same signature your team uses everywhere else.
The checklist for every sending domain
- MX and a real mailbox. Replies and bounces need somewhere to go, and someone needs to read them.
- One SPF record listing only the services that send for that domain. Don't copy the main domain's record across if half of those services never send outreach. See How to write an SPF record and Multiple SPF records (why that is invalid).
- DKIM signed with that domain. Turn on custom DKIM in the sending tool so the signature uses
example.net, not the tool's own domain. See DKIM selectors and DNS records and SPF include vs DKIM from the vendor. - A DMARC record with a reporting address, starting at
p=noneand moving to enforcement once reports show every legitimate source passing:
_dmarc.example.net TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
Publishing the record is covered on our DMARC setup page, and the staged rollout is in A safe rollout: p=none to quarantine to reject. If reports go to an address on a different domain, that domain has to authorize receiving them.
5. Lock down domains that never send. First confirm nothing still sends from the domain. Then publish an SPF record that allows nothing and a DMARC record at p=reject:
parked.example TXT "v=spf1 -all"
_dmarc.parked.example TXT "v=DMARC1; p=reject"
That asks receivers to reject any mail using the domain, and the SPF record tells them no server is authorized to send it. Common SPF mistakes covers the SPF record for parked domains, and When you are ready for p=reject covers when p=reject is the right policy for a domain that never sends.
6. Add every domain to your DMARC reporting, so you can see all sources across all domains in one place. See How to inventory sending sources and What visual DMARC analysis should show you.
7. One-click unsubscribe and an opt-out you honor on every outreach domain.
For setups where several services share domains, see Shared domains and multi-service setups.
What a separate domain does and doesn't do
It does keep outreach apart from your main domain's mail flows. Your sales team can add tools and change records on the outreach domain without touching the records your finance and support mail depend on.
It doesn't hide who's sending. Complaints still count against the outreach domain, and recipients still connect it to your brand.
And it doesn't let you send more safely. A new domain has no history for providers to judge, so it starts from zero. IP and domain reputation explains how domain reputation builds up.
How many domains and inboxes do you need for a cold email campaign?
There's no required number. Every extra domain is another SPF, DKIM and DMARC setup to maintain, another set of reports to read, and another domain to protect once you stop using it.
Work it out from your real volume and how your team is organized, not from a wish to stay under filters. If you're adding domains so each one sends less, the underlying problem is usually list quality or volume growth, and more domains won't fix it. How many emails can you send per day? explains which daily limits actually exist.
How to warm up a new cold email domain
"Warm-up" just means giving a new domain a sending history gradually. Send small volumes first, to people who expect or welcome the mail. Increase in steps while bounces and complaints stay low, and hold or step back if they rise. No provider publishes a warm-up schedule, so be wary of anyone selling one as a rule.
Don't use services that fake opens, replies or "not spam" clicks to simulate engagement. That's filter evasion, and we don't recommend it. Engagement only helps your reputation when it's real.
Do you need DMARC for cold email? covers the authentication setup outreach mail needs before you start.
Common mistakes
- No DMARC on the outreach domain because "it's only for sales".
- Leaving the sending tool on its own DKIM domain.
- Forgetting to add new domains to DMARC reporting.
- Leaving old outreach domains unprotected after a campaign ends.
- Lookalike domains with no visible connection to the brand.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
Does a subdomain need its own DMARC record?
Not necessarily. The parent domain's policy, or its sp tag, applies to the subdomain. Publish a separate record if you want a different policy or separate reporting for it.
Will a separate domain protect my main domain?
It separates DNS records and sending tools. It doesn't stop recipients connecting the two domains, and complaints about outreach still reflect on your brand.
How many domains do I need for cold email?
As few as your volume and team structure require. There's no required number, and each one adds maintenance.
How long should I warm up a new domain?
No provider publishes a schedule. Grow slowly while complaints and bounces stay low.
Should unused outreach domains be deleted?
While you still own them, and once you're sure they no longer send, keep them protected with an SPF record that allows nothing and a DMARC p=reject record, so nobody can send as them.