What Are SPF, DKIM, and DMARC for Cold Email?
SPF, DKIM, and DMARC are email authentication standards because mailbox providers need technical proof that your domain is allowed to send what it claims to send.
SPF tells receiving servers which mail servers can send on behalf of your domain.
DKIM adds a cryptographic signature to each message so providers can verify the message was sent by an authorized system and was not altered in transit.
DMARC tells providers what to do when SPF or DKIM checks fail and gives you reporting visibility into authentication problems.
For cold email, this is not optional. Gmail, Outlook, and Microsoft 365 tenants increasingly expect alignment and consistency. At OutboundPros we have seen campaigns go from low single-digit inbox placement to stable sending only after fixing basic authentication mistakes. The honest limitation is that authentication alone will not save a bad setup. If your domains are burned, your copy triggers spam complaints, or you ramp volume too aggressively, SPF, DKIM, and DMARC will not compensate.
Why Do SPF, DKIM, and DMARC Matter More for Cold Email Than Regular Sales Email?
SPF, DKIM, and DMARC matter more for cold email because unsolicited outreach gets less trust by default and is judged more harshly by mailbox providers.
Internal mail and normal one-to-one sales email often benefit from existing reply history, recipient recognition, and lower complaint risk. Cold email has none of that. You are sending to new contacts from domains that may have little reputation, often through a separate infrastructure stack.
That means small technical issues become big delivery problems.
- A missing SPF include can cause soft fails.
- A disabled DKIM key can break domain trust.
- A weak DMARC setup can hide alignment problems until performance drops.
- Sending from Google Workspace or Microsoft 365 while using a third-party sequencer can create mismatch between envelope sender and visible from-domain.
At OutboundPros we usually check authentication before touching copy, list quality, or sequencing. In practice, a 20-minute DNS fix is often worth more than rewriting the first line of an email.
How Do You Set Up SPF for Cold Email in Google Workspace and Microsoft 365?
SPF is a DNS TXT record because receiving servers query DNS to confirm whether your sending platform is authorized.
You should have exactly one SPF record per domain. That single record can contain multiple authorized senders through include statements, but publishing two separate SPF TXT records will usually break validation.
For Google Workspace, the standard SPF value is typically:
v=spf1 include:_spf.google.com ~all
For Microsoft 365, the standard SPF value is typically:
v=spf1 include:spf.protection.outlook.com ~all
If you use additional sending tools for cold email, you may also need to include their SPF mechanism inside the same record. Common examples are custom tracking domains, sending relays, or inbox rotation tools.
A practical structure looks like this:
v=spf1 include:_spf.google.com include:thirdparty.example ~all
Or:
v=spf1 include:spf.protection.outlook.com include:thirdparty.example ~all
The important rules are simple.
1. Publish one SPF TXT record at the root domain or subdomain you send from.
2. Merge all includes into that single record.
3. Stay under the 10 DNS lookup limit.
4. Start with ~all, not -all, unless you fully control all send sources.
At OutboundPros we usually send cold email from subdomains rather than the primary company domain. That gives cleaner separation between outbound activity and core business email. One honest trade-off is that SPF setup becomes slightly more complex when multiple tools are involved, especially if a client already has old marketing platforms sitting in DNS.
How Do You Set Up DKIM in Google Workspace?
DKIM in Google Workspace is configured by generating a domain key in the Admin console and publishing the matching DNS TXT record because Google signs outgoing mail only after it finds the correct public key.
The basic process is:
1. Open Google Admin console.
2. Go to Apps, Google Workspace, Gmail, Authenticate email.
3. Select the domain or subdomain.
4. Generate a new DKIM record.
5. Use a 2048-bit key when your DNS provider supports it.
6. Copy the TXT record name and value into DNS.
7. Wait for DNS propagation.
8. Return to Google Admin and click Start authentication.
A typical selector is something like google or google2024, and the host record often looks like:
google._domainkey.yourdomain.com
The TXT value starts with:
v=DKIM1; k=rsa; p=
Then a long public key follows.
The most common mistakes are operational, not technical.
- Publishing the key on the wrong domain
- Adding extra quotation marks or broken line wraps in DNS
- Generating DKIM for the primary domain but sending from a different subdomain
- Forgetting to click Start authentication after the DNS record is live
At OutboundPros we verify DKIM with external header checks after launch, not just inside Google. Google saying authentication is enabled is useful, but inbox providers care about what is actually present in the message headers.
How Do You Set Up DKIM in Microsoft 365?
DKIM in Microsoft 365 is enabled by creating two CNAME records and then turning signing on in Defender or Exchange settings because Microsoft hosts the signing keys on its side.
The exact menu names move around over time, but the process is usually:
1. Open Microsoft 365 Defender or Exchange Admin.
2. Locate DKIM settings for your custom domain.
3. Microsoft will show two required CNAME records.
4. Publish both CNAMEs in DNS.
5. Wait for propagation.
6. Enable DKIM signing for that domain.
The CNAME format often follows this pattern:
selector1._domainkey.yourdomain.com
selector2._domainkey.yourdomain.com
And the targets usually point to Microsoft-managed values tied to your tenant.
This is where teams get tripped up. They expect a TXT record like Google, but Microsoft 365 usually relies on CNAME-based delegation for DKIM. If you skip one selector or mistype the tenant value, signing will not activate.
If you send cold email through Microsoft 365 mailboxes connected to a sequencer, make sure the visible from-domain, return-path behavior, and DKIM signing domain all align. We have seen setups where mail technically sends, but alignment is weak enough that Outlook recipients start junking messages after a few days of volume.
How Do You Set Up DMARC Safely for Cold Email?
DMARC is a DNS TXT policy record because it tells receiving servers how strictly to enforce alignment and where to send aggregate reports.
The DMARC record lives at:
_dmarc.yourdomain.com
A safe starting DMARC record for cold email is usually:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; pct=100; adkim=s; aspf=s
Here is what the main tags mean.
| Tag | Meaning | Recommended starting point |
| --- | --- | --- |
| v | DMARC version | DMARC1 |
| p | Policy action | none |
| rua | Aggregate report address | a monitored mailbox |
| pct | Percentage of mail affected | 100 |
| adkim | DKIM alignment mode | s |
| aspf | SPF alignment mode | s |
Start with p=none so you can monitor failures without telling providers to quarantine or reject mail yet. Once you confirm legitimate mail passes consistently, you can tighten the policy.
A staged rollout usually looks like this:
1. Week 1 to 2: p=none
2. Week 3 to 4: p=quarantine
3. After stable validation: p=reject
That said, not every cold email domain needs to rush to reject. If you are using a dedicated sending subdomain with tightly controlled sources, moving to quarantine or reject is easier. If the domain has multiple legacy tools attached, DMARC tightening can accidentally break valid mail. We have had clients discover old support platforms, invoicing tools, and forms software only because DMARC reports exposed them.
How Do You Check Whether SPF, DKIM, and DMARC Are Working?
Authentication is working when live test emails show SPF pass, DKIM pass, and DMARC pass with alignment because published DNS records alone do not guarantee correct message handling.
There are three practical ways to verify this.
1. Send a test email to a Gmail inbox and inspect Show original.
2. Send a test email to an Outlook inbox and inspect message headers.
3. Use a deliverability testing tool that reports authentication status and alignment.
What you want to see is simple.
- SPF: PASS
- DKIM: PASS
- DMARC: PASS
- From-domain aligned with either SPF or DKIM, ideally both
At OutboundPros we also check whether the message is signed after it passes through the actual sending workflow, not just from the mailbox itself. This matters because some sequencers, forwarding setups, or SMTP relays alter the path enough to create different results than a direct manual send.
A common operator detail: test from the exact mailbox, tool, and sending path you will use in production. A Gmail mailbox sent manually from the web app can behave differently from that same mailbox connected through an outbound platform.
What Mistakes Hurt Cold Email Deliverability Even When Authentication Is Set Up?
Authentication can be technically correct while deliverability still suffers because mailbox providers evaluate behavior, reputation, and engagement in addition to DNS records.
The biggest mistakes we see are these.
- Sending 50 to 100 emails per mailbox on day one
- Using the primary company domain instead of a dedicated subdomain or adjacent domain
- Running too many mailboxes on one domain without warming
- Mixing marketing blasts and cold outbound through the same domain identity
- Leaving old SPF includes that push the record over lookup limits
- Publishing DMARC but never reading reports
- Personalizing poorly and driving spam complaints
A practical baseline for new cold email infrastructure is conservative ramping. For brand-new mailboxes, many teams start at 10 to 20 emails per day, then build toward 25 to 40, sometimes 50, depending on domain age, list quality, and reply rates. Anyone promising that DNS records alone let you safely send 200 cold emails per mailbox is selling a fantasy.
At OutboundPros, authentication is part of a bigger system: domain strategy, mailbox count, warm-up, targeting, copy, and reply handling. The honest limitation is that even a perfect technical setup can stall if the offer is weak or the list is off.
How Should You Structure Domains and Mailboxes Before You Publish These Records?
Domain structure matters because authentication works best when the sending identity is isolated, intentional, and easy to control.
A practical setup for many B2B teams looks like this:
| Asset | Recommended approach |
| --- | --- |
| Primary company domain | Keep for website and normal business email |
| Cold email domain or subdomain | Use for outbound only |
| Mailboxes per domain | Usually 3 to 10 to start |
| Daily volume per mailbox | Usually 20 to 40 after ramp |
| Authentication | SPF, DKIM, DMARC on every sending domain |
Two common patterns work well.
1. Subdomain model: outbound.yourcompany.com or mail.yourcompany.com
2. Adjacent domain model: getyourcompany.com or yourcompany.co
We often prefer subdomains when the main brand domain is strong and tightly managed. We use adjacent domains when the client wants maximum separation or already has messy DNS history on the main domain. The trade-off is branding. Adjacent domains can protect reputation, but they can also look less natural if chosen badly.
The key point is consistency. Whatever domain strategy you choose, publish SPF, DKIM, and DMARC on the exact domain that appears in the from-address.
Frequently Asked Questions
Do I need SPF, DKIM, and DMARC on a subdomain used for cold email?
Yes. A cold email subdomain needs its own authentication because mailbox providers evaluate the exact sending domain identity, not just your main root domain.
If you send from reps@outbound.yourcompany.com, configure records for that sending setup directly and verify alignment on live messages.
Should I use ~all or -all in my SPF record?
Use ~all first because it is safer while you are validating all legitimate send sources.
Move to -all only when you are certain every valid sender is included. A strict SPF policy with missing includes can silently break real mail.
Can I publish more than one SPF record?
No. You should publish one SPF TXT record per domain because multiple SPF records usually cause validation errors.
If you use several sending platforms, merge them into one record with multiple include mechanisms.
What DMARC policy should I start with for cold email?
Start with p=none because it gives visibility without enforcement.
After 1 to 4 weeks of stable passing mail and reviewed reports, consider moving to p=quarantine and then p=reject if the domain is tightly controlled.
Does Google Workspace use TXT for DKIM while Microsoft 365 uses CNAME?
Usually yes. Google Workspace typically publishes a DKIM TXT public key, while Microsoft 365 typically asks you to create two CNAME records that point to Microsoft-managed selectors.
Always follow the values shown inside your actual admin account because selectors and tenant targets differ.
Will setting up SPF, DKIM, and DMARC guarantee inbox placement?
No. Authentication improves trust, but it does not guarantee inboxing because providers also score reputation, content, complaints, sending patterns, and recipient engagement.
It is foundational, not magical. You still need good domain strategy, sane volume, decent targeting, and strong copy.