Learn
v=spf1 include:_spf.google.com ~all: SPF Record Explained
v=spf1 include:_spf.google.com ~all is Google's SPF record for domains that send only through Workspace. What each part does and how to add other senders.
Reference
v=spf1 include:_spf.google.com ~all is the SPF record Google documents for a domain that sends mail only through Google Workspace. SPF (Sender Policy Framework) is a DNS TXT record that lists the servers allowed to send mail for your domain. This record has three parts, and receiving servers read them from left to right.
| Part | What it does |
|---|---|
v=spf1 |
Marks the TXT record as SPF. It must come first. Receivers discard TXT records that do not begin with exactly this value. |
include:_spf.google.com |
Runs an SPF check against Google's own record. If the sending server is on Google's list, the check ends here with pass. |
~all |
all matches every server left. The ~ qualifier gives those servers softfail, a weak statement that they are probably not authorized. |
What _spf.google.com contains
Google publishes its outbound mail ranges in the TXT record _spf.google.com. Google says these addresses change often, so keep the include: term and leave the ranges out of your own record. On 2026-11-09 that record held two ip4: ranges, six ip6: ranges and no nested include:.
Google's record ends in a ~all of its own, and that ending does not decide your result. RFC 7208 says only the evaluated result of the referenced record is used, and a softfail there counts as no match. The check then moves to the next term in your record.
An include: costs one DNS lookup, and SPF allows 10 per check. The ip4:, ip6: and all terms cost none.
What ~all means for other servers
Receivers decide what happens to a softfail. RFC 7208 says they should not reject a message on that result alone. Google says receivers typically accept such mail and mark it as suspicious.
Google recommends ~all and says a hyphen "can be overly restrictive and cause delivery issues for legitimate email". For DMARC (the policy built on SPF and DKIM), ~all and -all are both failed SPF checks. Only a pass on a domain aligned with the From address counts.
Caution: with -all, receivers may reject mail from any sender you forgot to list. Google recommends DMARC reports to identify all your senders. Read them before you make this change.
When this record is correct as written
Use it unchanged when Google Workspace is the only system sending mail for the domain. Google documents it for exactly that case.
It is incomplete when other servers also use this domain in MAIL FROM, the address SPF evaluates. Google lists web servers, on-premise mail servers, outbound gateways, contact forms that send automatically and third-party services.
It also covers one name. Google says each domain must have its own SPF record and each subdomain you use needs one too. The publishing steps are in the SPF setup guide for Google Workspace.
Examples
Each line below is a complete value for the TXT record. A domain publishes only one of them.
Google Workspace only
v=spf1 include:_spf.google.com ~all
Google Workspace and Microsoft 365
Google documents this pair:
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
Google Workspace and Zendesk
Google and Zendesk publish this pair with different endings. Google uses ~all. Zendesk recommends -all. A record has one ending, and this example follows Google:
v=spf1 include:_spf.google.com include:mail.zendesk.com ~all
Google Workspace and your own server
A server of your own goes in by public IP address, with ip4: or ip6:. The include: term takes only a domain name. Replace this example address with yours:
v=spf1 ip4:203.0.113.25 include:_spf.google.com ~all
How to add a sender to this record
- Start from the value already published. Caution: edit that record. A second
v=spf1record on the same name makes the check returnpermerror, and Google warns that mail might end up in spam. - Read the sender's own documentation. SPF checks the domain in MAIL FROM, the envelope sender used during delivery. It can differ from the From address people see. A service that uses its own domain there does not rely on your record. Amazon SES does this by default with a subdomain of
amazonses.com. Google's table listsinclude:amazonses.com, but Amazon's custom MAIL FROM setup publishes that term on the subdomain you choose. - Put the new term before
~all. Separate terms with one space. The SPF generator can build the line for you. - Count the lookups. Terms inside an
include:count toward the 10. On 2026-11-09,_spf.google.com,spf.protection.outlook.comandmail.zendesk.comused one each._spf.salesforce.comused two, because its record relies onexists. Past 10, the check returnspermerror. See how to fix too many lookups. - Replace the old value. Caution: keep the terms of every sender still in use. Google says a sender missing from the record might fail SPF and be rejected or sent to spam.
Common mistakes
- A separate record for each sender. The check returns
permerror. Merge them into one. - A sender added after
~all. Receivers ignore terms afterall, sov=spf1 include:_spf.google.com ~all include:mail.zendesk.comleaves Zendesk out. spf.google.comwith no underscore. That name did not exist when we resolved it on 2026-11-09. Aninclude:whose name has no SPF record returnspermerror.- Pasting Google's ranges in place of the
include:. Google's addresses change often, and a pasted copy goes out of date. See how an SPF include works. - Leaving off
~all.v=spf1 include:_spf.google.comgives unlisted serversneutral, a result that asserts nothing about the server. Google recommends always includingall. - Typos and stray characters. Google warns that typos, extra spaces and wrong quotation marks can make the record invalid.