
SPF tells receiving mail servers which servers may send email for your domain. For Google Workspace and Microsoft 365 the basic record is one line — but small mistakes, like a second SPF record or too many includes, quietly break it. This guide shows how to configure the SPF record for Google Workspace and Microsoft 365: the exact values, choosing between ~all and -all, the 10-lookup limit, subdomains and parked domains, whether your sending tools need adding, and how to fix common failures.
Ten Lookups Is All You Get
💡 TL;DR
The SPF record for Google Workspace is v=spf1 include:_spf.google.com ~all, and for Microsoft 365 it's v=spf1 include:spf.protection.outlook.com -all (standard commercial tenants). Publish exactly one SPF TXT record per sending domain and subdomain, stay within SPF's 10-DNS-lookup limit, add v=spf1 -all to parked domains, and remember that cold email tools connected by OAuth send through Google or Microsoft — so they usually don't need their own include.
Ten. That's how many DNS lookups SPF allows while evaluating a record. Every include, a, mx, and redirect counts — including the lookups nested inside each include. Go over, and the result is a permanent error, which many receivers treat as a failure.
For a domain sending only from Google Workspace or only from Microsoft 365, ten is plenty. The trouble starts when teams keep adding services — a CRM, a marketing platform, a help desk — each with its own include, until the record quietly breaks.
By the end of this, you'll know exactly how to set up and maintain the SPF record for Google Workspace and Microsoft 365 without hitting those limits. For multi-domain Microsoft 365 setups, see multi-domain SPF for Microsoft 365.
The Exact Values for Each Platform
Platform | SPF record | Notes |
|---|---|---|
Google Workspace | v=spf1 include:_spf.google.com ~all | Google's commonly documented value |
Microsoft 365 (commercial and GCC) | v=spf1 include:spf.protection.outlook.com -all | Microsoft's documented value |
Microsoft 365 GCC High / DoD | v=spf1 include:spf.protection.office365.us -all | Sovereign cloud variant |
Microsoft 365 operated by 21Vianet | v=spf1 include:spf.protection.partner.outlook.cn -all | China variant |
Domain that sends no email | v=spf1 -all | Tells receivers no mail should come from it |
These values come from the platforms' own documentation; Microsoft's SPF configuration guide lists its variants. Publish the record as a TXT record at the root of the domain (host @).
~all or -all?
The last part of the SPF record for Google Workspace and Microsoft 365 domains tells receivers what to do with mail from servers not listed.
Qualifier | Meaning | When to use it |
|---|---|---|
~all (softfail) | Mail from unlisted servers is suspicious but not definitively rejected by SPF alone | While you're still discovering every service that sends for you |
-all (hardfail) | Mail from unlisted servers is not authorized | Once you're confident every legitimate sender is listed |
?all / +all | Neutral / allows anyone | Avoid — they weaken or remove protection |
In practice, DMARC does most of the enforcement today, so the difference between ~all and -all matters less than it used to. What matters most is that every legitimate sender is listed and the record is valid. Google's documentation typically shows ~all; Microsoft's shows -all. Either works when DMARC is in place.
The 10-Lookup Limit and How to Stay Under It
Every include counts — and so do the includes nested inside it.
a, mx, exists, and redirect count too. ip4 and ip6 don't.
Use an SPF checker to count total lookups after every change.
Remove services you no longer use — old includes are the most common cause of going over.
Move third-party senders to subdomains with their own SPF records, so the main domain stays lean.
Be careful with "flattening" (replacing includes with IP lists) — provider IP ranges change, and stale lists break silently.
Here's the advice we'd push back on: "Add every service's include to the same record so nothing gets missed." That's exactly how records exceed ten lookups. Each service should either send through your main platform, use its own subdomain, or be removed.
Do Cold Email Tools Need Their Own SPF Include?
Usually not — and this is a point many SPF guides skip.
When tools like Instantly, Smartlead, or Lemlist connect to your Google Workspace or Microsoft 365 mailbox by OAuth, the email is still sent through Google's or Microsoft's servers. Those servers are already covered by your platform's include. Adding the sending tool's own include is unnecessary and uses up lookups.
How the tool sends | Extra SPF include needed? |
|---|---|
Through your Google Workspace or Microsoft 365 mailbox (OAuth) | No — your platform's include covers it |
Through the tool's own mail servers | Yes — follow the tool's instructions, ideally on a subdomain |
Through a separate email service (newsletters, notifications) | Yes — preferably on a subdomain with its own SPF |
Check your tool's documentation to see which applies. Connecting mailboxes by OAuth is covered in Microsoft 365 OAuth setup.
Worked Examples for Common Setups
Here's how the SPF record for Google Workspace and Microsoft 365 looks in a few real-world setups.
Setup | SPF record | Why |
|---|---|---|
Outreach domain on Google Workspace only | v=spf1 include:_spf.google.com ~all | One platform; tools connect by OAuth |
Outreach domain on Microsoft 365 only | v=spf1 include:spf.protection.outlook.com -all | One platform; tools connect by OAuth |
Main domain on Microsoft 365 plus a help desk that sends from its own servers | v=spf1 include:spf.protection.outlook.com include:{helpdesk-include} -all | Two real senders; check total lookups |
Domain moving from Google to Microsoft 365 | v=spf1 include:spf.protection.outlook.com include:_spf.google.com ~all (temporarily) | Both send during the migration; remove Google's include afterwards |
Newsletter subdomain via an email service | On news.{domain}: the service's own include | Keeps the main record lean |
Notice what's missing from the outreach rows: no includes for sending tools. Because those tools send through the mailbox platform, the SPF record for Google Workspace and Microsoft 365 outreach domains can stay as a single include.
Write each domain's intended SPF value into your inventory. When someone proposes adding an include later, compare it with the inventory first — it's the simplest way to stop a lean SPF record for Google Workspace and Microsoft 365 domains from growing past the lookup limit over time.
Subdomains, Parked Domains and Alignment
🌿Subdomains need their own record
An SPF record on getacme.com doesn't cover mail.getacme.com. Each sending subdomain needs its own SPF TXT record.
🅿️Parked domains
Domains you own but don't send from should publish v=spf1 -all, so nobody can easily send as them.
🎯Alignment for DMARC
SPF checks the envelope sender (Return-Path), not the visible From. For SPF to satisfy DMARC, those domains must align. Google Workspace and Microsoft 365 normally handle this for mail sent from your mailboxes.
📦Outreach domains
Every outreach domain gets its own SPF record — see DNS templates for Google Workspace and Microsoft 365.
Checking and Fixing SPF
Check the SPF record for Google Workspace and Microsoft 365 domains after every change.
Look it up: dig +short {domain} TXT — confirm exactly one record starting v=spf1.
Count lookups with an SPF checker.
Send a test message to a Gmail address and confirm spf=pass in the headers.
Check DMARC reports for legitimate sources failing SPF.
Problem | Likely cause | Fix |
|---|---|---|
SPF permerror | Two SPF records, or more than 10 lookups | Merge into one record; remove unused includes |
SPF fail for your own mailboxes | Wrong include for your platform | Use _spf.google.com or spf.protection.outlook.com as appropriate |
SPF fails on a subdomain | No record on the subdomain | Publish an SPF record on the subdomain |
Record not found | Published on the wrong host or as the wrong type | TXT record at the root (@) |
Syntax error | Missing v=spf1, stray quotes, or typos | Re-enter carefully and recheck |
SPF works alongside DKIM and DMARC — see the DKIM guide and our SPF, DKIM, and DMARC setup guide. Litemail configures SPF, DKIM, and DMARC automatically on every domain for its Google Workspace and Microsoft 365 inboxes.
SPF configured correctly on every domain — Litemail Google Workspace and Microsoft 365 inboxes come with SPF, DKIM, and DMARC configured automatically, full admin access, dedicated US and EU IPs, and pre-warmed options. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Multi-Domain SPF for Microsoft 365 · DKIM Guide · DNS Templates for Google Workspace and Microsoft 365 · Pre-Warmed Domains
Key Takeaways
The SPF record for Google Workspace is v=spf1 include:_spf.google.com ~all; for Microsoft 365 commercial it's v=spf1 include:spf.protection.outlook.com -all.
Publish exactly one SPF record per domain, and a separate one for each sending subdomain.
Stay within 10 DNS lookups, counting nested includes; remove unused services.
Cold email tools connected by OAuth send through your platform and usually don't need their own include.
Publish v=spf1 -all on parked domains.
Verify with a DNS lookup, an SPF checker, and a test message showing spf=pass.
Frequently Asked Questions
What is the SPF record for Google Workspace?
v=spf1 include:_spf.google.com ~all, published as a TXT record at the root of the domain.
What is the SPF record for Microsoft 365?
For standard commercial tenants: v=spf1 include:spf.protection.outlook.com -all. Government and China clouds use different includes.
Can a domain have two SPF records?
No. Two SPF records cause a permanent error. Merge them into one.
Should I use ~all or -all?
Use ~all while you're still identifying all senders and -all once you're confident. With DMARC in place, either works.
Do I need to add my cold email tool to my SPF record?
Not if it sends through your Google Workspace or Microsoft 365 mailbox via OAuth. Only tools that send from their own servers need an include.
What happens if my SPF record has more than 10 lookups?
SPF returns a permanent error, which many receivers treat as a failure. Remove unused includes or move senders to subdomains.
Does Litemail set up the SPF record for Google Workspace and Microsoft 365?
Yes. Litemail configures SPF, DKIM, and DMARC automatically on every domain for its Google Workspace and Microsoft 365 inboxes.
Get Authentication Right From the Start
Litemail inboxes come with SPF, DKIM, and DMARC configured, full admin access, dedicated US and EU IPs, sending history on pre-warmed plans, and free domain replacement.
Plans from $39/month · Google Workspace and Microsoft 365 · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Pre-Warmed Inboxes · Google Workspace Inboxes · Microsoft 365 Inboxes · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


