Quick answer
SPF lists the servers allowed to send email for your domain. DKIM signs every email so the receiver can check it came from your domain and wasn't changed. DMARC tells the receiver what to do when a message fails, and it only passes when the domain in your From address matches the domain SPF or DKIM checked. That match is called alignment. For cold email, every sending domain needs all three: one SPF record with no more than 10 DNS lookups, a DKIM key of at least 1024 bits (2048 if your provider supports it) and a DMARC record with at least p=none. Google, Yahoo and Microsoft all require that from bulk senders. I checked their pages on 14 October 2026.
What SPF, DKIM and DMARC do, in plain words
I set up cold email and LinkedIn outbound for B2B companies, and before any campaign goes out I check these three records on every sending domain. Great copy means nothing if it lands in spam. Each record answers a different question for the receiving server:
| Record | The question it answers | Where it lives | Without it |
|---|---|---|---|
| SPF | Is this server allowed to send mail for this domain? | One TXT record on the domain itself | Receivers can't tell your servers from a spoofer's |
| DKIM | Was this email signed by the domain, and is it unchanged? | A TXT record at selector._domainkey.yourdomain, plus a signature in every email | Nothing proves the email really came from you |
| DMARC | Does the From domain match what SPF or DKIM checked, and what should happen if not? | A TXT record at _dmarc.yourdomain | No policy or reports, and you miss the bulk sender rules |
One detail explains most of the confusion later. SPF doesn't check the From address people see. It checks the hidden envelope sender (the Return-Path), which your sending platform may set to its own domain. DKIM checks whichever domain signed the email, which may also be the platform's. DMARC is the record that ties either of them back to the From address your prospect actually reads.
Example records for a cold email domain
Say you send cold email from example.com, a domain you bought for outreach, with mailboxes on Google Workspace. These are the three records you'd add at your DNS host:
Type Host Value
TXT example.com v=spf1 include:_spf.google.com ~all
TXT google._domainkey.example.com v=DKIM1; k=rsa; p=MIIBIjANBg...(your public key)
TXT _dmarc.example.com v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
- SPF: the value comes from Google's SPF setup page, which recommends
~all. On Microsoft 365 the record isv=spf1 include:spf.protection.outlook.com -all, and Microsoft recommends-all. DMARC treats both as an SPF fail, so either works once DKIM is in place. - DKIM: you don't write this one. Your mailbox provider generates the key and gives you the record. Pick 2048 bits: Google requires at least 1024 to reach personal Gmail accounts and recommends 2048 if your DNS host supports it, and the DKIM standard says the same (RFC 8301). On Google Workspace the default selector is
google, and a new key can take up to 48 hours to start working (Google). - DMARC:
p=noneis the policy,ruais where receivers send daily reports. Send them to a mailbox or a DMARC reporting tool someone actually reads.
If you use a mailbox provider built for cold email, it often adds all three for you. Check them anyway. The free cold email deliverability checker on this site reads a domain's MX, SPF, DKIM and DMARC from public DNS and tells you what's missing.
To see what your own domain publishes right now, run it through the free SPF, DKIM and DMARC checker on my agency's site, Shipyard GTM. It reads the live DNS records and flags what is missing.
Alignment: why SPF and DKIM pass and DMARC still fails
DMARC passes when SPF passes for a domain that matches your From domain, or DKIM passes for a domain that matches it. One is enough. A pass on some other domain doesn't count.
The DMARC standard allows two modes. Relaxed, the default, accepts any domain under the same organizational domain, so mail.example.com aligns with example.com. Strict needs an exact match. The standard itself says nearly every domain owner finds relaxed enough, and Yahoo says relaxed is acceptable.
Where it goes wrong in cold email:
- The platform signs with its own domain. DKIM passes, but for the platform's domain, not yours. Fix: generate a DKIM key for your own domain in Google Workspace, Microsoft 365 or your sending tool.
- The Return-Path belongs to the platform. SPF passes for the platform's bounce domain, which doesn't match your From. Fix: set a custom return-path domain if your tool supports it. If DKIM aligns, DMARC passes anyway.
To see what actually happened to one email, send it to a Gmail address, open it and choose "Show original". You'll see SPF, DKIM and DMARC each marked PASS or FAIL, and the headers below show which domain each check used.
p=none vs quarantine vs reject
| Policy | What it asks receivers to do with failing mail | When to use it |
|---|---|---|
p=none | Nothing. Deliver as normal and send reports | A new domain, or any domain while you read the reports |
p=quarantine | Treat it as suspicious, usually the spam folder | Once reports show your real mail passes |
p=reject | Refuse it | When you're sure nothing legitimate fails |
Two things people get wrong here. First, p=none is enough to meet the rules. Google, Yahoo and Microsoft all accept it as the minimum, and Microsoft recommends p=reject. Second, the policy only decides what happens to mail that fails DMARC. Your own cold emails pass, so moving to reject doesn't push them into the inbox. What it does is stop other people sending as your domain.
For a domain that only sends cold email from one provider, the move to quarantine is low risk once the reports are clean. For your main company domain, where people, invoices, support tools and newsletters all send, go slower. For domains like that, the new DMARC standard, RFC 9989 from May 2026, suggests p=none for at least a month, then quarantine for as long again, before reject. It also drops the old pct tag, which many guides, Google's included, still use to roll out a policy in steps.
Leaving p=none forever. It's the right place to start and a bad place to stay on your main domain, because it monitors spoofing and stops none of it. Put a date in the calendar a month after you publish it, read the reports, then move.
SPF mistakes: two records and the 10-lookup limit
An SPF record usually breaks the day someone adds a new sending tool. These are the common mistakes, with what RFC 7208, the SPF standard, says happens:
| Mistake | What happens | Fix |
|---|---|---|
Two SPF records on one domain, usually a second v=spf1 record added for a new tool | A permerror. SPF fails for all your mail | Merge them into one record with both includes |
| More than 10 DNS lookups | A permerror | Remove tools you no longer use, or give each tool its own sending domain |
| More than 2 "void" lookups (includes that point to nothing) | The RFC says implementations should limit these to two, and going over is a permerror | Delete includes for services you've cancelled |
A ptr mechanism | The RFC says it should not be published, and it counts toward the 10 | Remove it |
Ending with +all | Any server in the world may send as you | Use ~all or -all |
What counts toward the 10: include, a, mx, ptr, exists and redirect. What doesn't: ip4, ip6 and all. Includes inside includes count too, so a record with six includes can still go over 10 if a vendor's record includes others. A record that's over the limit looks normal in DNS, which is why it often goes unnoticed. Run any checker that counts lookups after every change.
What Google, Yahoo and Microsoft require in 2026
I read each provider's own page on 14 October 2026. The short version: all three want SPF, DKIM and DMARC from anyone sending at volume, and all three accept p=none.
| Gmail | Yahoo | Outlook.com | |
|---|---|---|---|
| Who counts as bulk | Close to 5,000+ messages a day to personal Gmail accounts. Subdomains count toward the main domain, and the status never expires | No number. "A significant volume of mail" | More than 5,000 emails a day to Outlook.com, Hotmail and Live addresses |
| Everyone else | SPF or DKIM, valid reverse DNS, TLS, spam rate under 0.3% | SPF or DKIM, valid reverse DNS, spam rate under 0.3% | SPF, DKIM and DMARC strongly recommended |
| SPF and DKIM (bulk) | Both | Both | Both must pass |
| DMARC (bulk) | At least p=none, From aligned with SPF or DKIM | At least p=none, must pass, relaxed alignment is fine | At least p=none (p=reject recommended), aligned with SPF or DKIM, preferably both |
| Unsubscribe (bulk) | One-click for marketing and promotional mail, plus a visible link, honoured within 48 hours | One-click for marketing mail, plus a visible link, honoured within 2 days | A clear, working unsubscribe link (recommended) |
| Spam rate | Under 0.1%, never 0.3% or higher | Under 0.3% | Not stated |
| If you don't comply | Temporary and permanent rejections, with enforcement stepped up from November 2025 | Enforced since February 2024 | Since 5 May 2025: rejected with 550 5.7.515 |
Sources for Gmail: Google's sender guidelines and FAQ. For Yahoo: its sender best practices and FAQ. For Outlook.com: Microsoft's announcement for high-volume senders. Microsoft's own pages don't fully agree on that last row: an April 2025 update to the announcement says failing mail is rejected, while its postmaster policy page says it goes to Junk first and may be rejected if the problem stays. Plan for rejection.
Two notes for cold email. Each sending domain in a typical setup sends far below 5,000 a day, so on paper most cold domains aren't bulk senders. I'd still meet the bulk rules on every domain: they cost nothing once set up, and Yahoo doesn't publish a threshold at all. And on unsubscribes, Google and Yahoo require one-click only for marketing and promotional mail. Whether a cold email counts is a grey area. Either way, make opting out easy, because someone who can't find a way out has one button left, and it's "Report spam".
What authentication doesn't fix
SPF, DKIM and DMARC make you eligible for the inbox. They don't put you there. Gmail's spam rate limit applies to perfectly authenticated mail, and so does everything else that decides placement: how new the domain is, how fast you ramp, how many emails each mailbox sends, how clean the list is and what the email says.
So the order is: authenticate every sending domain, then warm it up before it touches real prospects, then keep daily volume per mailbox low. I cover the rest in the cold email deliverability guide, and the inbox placement audit checklist shows how to test where your emails actually land.
Key takeaways
- SPF says which servers may send for your domain, DKIM signs each email and DMARC checks that one of them matches your From domain.
- Keep one SPF record per domain, with 10 DNS lookups or fewer. Two records or 11 lookups is a permanent error.
- DMARC fails when SPF and DKIM pass for someone else's domain. Sign with DKIM on your own domain.
p=nonemeets Google's, Yahoo's and Microsoft's minimum. Moving to quarantine or reject stops spoofing, not your own mail.- Use a 2048-bit DKIM key where your DNS host allows it.
- Authentication gets you considered for the inbox. Warmup, volume, list quality and copy decide where you land.
FAQ
Do I need SPF, DKIM and DMARC for cold email?
Yes, all three on every sending domain. Gmail, Yahoo and Outlook.com require all three from bulk senders, and a cold domain without them is easy for receivers to treat as spoofed.
What DMARC policy should I use for cold email?
Start with p=none and a reporting address, which meets all three providers' minimum. Once the reports show your mail passing, you can move a cold-only domain to p=quarantine. On your main company domain, go slower and check every service that sends as you first.
Why does DMARC fail when SPF and DKIM pass?
Because SPF or DKIM passed for a different domain from the one in your From address, usually your sending platform's. DMARC needs at least one of them to align with your From domain. Set up DKIM signing for your own domain and the problem usually goes away.
What is the SPF 10 DNS lookup limit?
RFC 7208 limits SPF evaluation to 10 terms that trigger DNS lookups: include, a, mx, ptr, exists and redirect, counting nested includes. Go over and SPF returns a permanent error, which counts as a fail.
Do Google's sender rules apply if I send fewer than 5,000 emails a day?
Some do. Every sender to Gmail needs SPF or DKIM, valid reverse DNS, TLS and a spam rate under 0.3%. The DMARC, alignment and one-click unsubscribe rules apply from about 5,000 a day, counted across the main domain and its subdomains.
