About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
If Google Workspace sends mail for your domain, the SPF record has to authorise Google's servers. When Workspace is the only sender, Google's setup page says to copy this line:
v=spf1 include:_spf.google.com ~all
The mechanism is include:_spf.google.com, underscore included. You publish it at the domain host, not in the Admin console: "You don't need to do anything in your Google Admin console to set up SPF." A missing include, a second v=spf1 record, or a chain of DNS lookups over 10 makes the SPF check fail: two v=spf1 records and more than 10 lookups each give permerror under RFC 7208.
What the record means
Google calls an SPF record "a line of text that you add to your domain" which "lists all the servers that send email for your domain." Receiving servers "check the SPF record to verify that the messages came from authorized servers."
Google's SPF setup page gives these rules: "SPF records always start with the v=spf1 tag." "Use the include: tag in front of each sender domain (or IP address) in your SPF record." "The ~all tag tells receiving servers to mark messages as spam if they're from servers that aren't listed in the SPF record. Google recommends you use ~all in your SPF record."
The Workspace-only value is v=spf1 include:_spf.google.com ~all. The same include:_spf.google.com term appears in Google's table of senders when Amazon, Microsoft Office 365, Salesforce, or another listed service also sends.
Google writes: "An SPF record can have up to 10 include: tags." That is about how many include tags you type. Receivers follow a different rule. RFC 7208 section 4.6.4 says the terms that cause DNS queries are include, a, mx, ptr, exists, and redirect, and "implementations MUST limit the total number of those terms to 10 during SPF evaluation". Terms inside an included record count in that same total. One Google include can be enough, or it can be the term that tips a long chain into permerror. Count every DNS-querying term in the chain, including the terms inside each include.
Section 4.5 says that if more than one record begins with exactly v=spf1, "check_host() produces the "permerror" result." Two SPF records fail even when one of them contains the Google include.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
The include string is not include:_spf.google.com |
Workspace mail fails SPF | Compare the TXT answer with the line above |
Two TXT records start with v=spf1 |
permerror from a short record |
Section 4.5 |
| Other senders were added without a recount | permerror after a new service |
Count DNS-querying terms in the whole chain |
| A sending subdomain has no SPF record | Mail from that name fails | Google: each subdomain needs its own record |
Prove the cause before changing anything
1. Read the published record.
dig +short TXT <your-domain>
The dig manual says +short is terse and the default is verbose. Run it once without +short so you can see the status. Paste every string that starts with v=spf1 into a dated note, such as spf-<your-domain>-<date>.txt. Also write down the TTL from the DNS console. That note is what you restore.
2. Compare. For Workspace-only sending, Google's record is v=spf1 include:_spf.google.com ~all. A record that does not contain include:_spf.google.com is not that line.
3. Count records and lookups. Two v=spf1 answers are permerror under section 4.5. If other services send, add one for each include, a, mx, ptr, exists, and redirect in your record and in every record those includes point at. The limit of 10 is section 4.6.4. Google's "up to 10 include: tags" is not a promise that ten includes will pass.
Fix
To save the current record first, run the command below. It writes the published TXT answers for your domain to a file, and the dated note from step 1 holds the TTL.
dig +short TXT <your-domain> > spf-<your-domain>-before.txt
Risk: the next steps replace your domain's SPF TXT record. Receivers use the new value within the record's time to live, and a wrong string makes legitimate mail fail SPF. ~all tells receivers to mark mail from unlisted servers as spam, so a scanner, form, or newsletter that still sends as your domain and is not named is in that set. Add its include in the same edit, or stop it sending, before you publish.
At the domain host, "typically where you purchased your domain name":
- Open the DNS TXT page.
- Add or update one TXT record. If the host is the domain itself, "enter the @ symbol." Otherwise use the domain name.
- For Workspace only, the value is
v=spf1 include:_spf.google.com ~all. Some hosts require quotes. Check that host's help. - If other services send, "use the SPF records in the table as a guide" and "Replace the domains with the domains of your email senders." Keep a single
v=spf1string.
To undo it: if spf-<your-domain>-before.txt shows no v=spf1 answer, there was no SPF record before, so delete only the v=spf1 TXT record you added. Otherwise publish, at the same name, the exact v=spf1 text saved in spf-<your-domain>-before.txt. Then run dig +short TXT <your-domain> and check that the v=spf1 answers returned are the ones saved, and no others (or that no v=spf1 answer remains, if you deleted the record). Receivers keep the new value until the TTL expires. Google's SPF setup page says SPF authentication "can take up to 48 hours" to start working. Seeing the new text in dig is not the same as every receiver having seen it.
Example (illustrative): example.com still has v=spf1 include:spf.protection.outlook.com ~all. Workspace is now the only sender. The administrator saves that string and replaces it with v=spf1 include:_spf.google.com ~all. One TXT answer starts with v=spf1 and contains include:_spf.google.com.
Confirm the fix
digthe name again. Exactly one TXT record begins withv=spf1, and it containsinclude:_spf.google.com.- Send a Workspace message to a mailbox that shows Authentication-Results, and read the
spfresult. - Repeat for each sending subdomain. Google says each one needs its own record.
What to watch afterwards
- When you start using a new mail server or third-party sender, Google says to "make sure to update your SPF record". Otherwise "messages sent by the new senders could be marked as spam."
- Remove domains and addresses you no longer use.
- A provider can add terms inside its own include and push you over 10 without a change on your line.
- Google also recommends DKIM and DMARC. SPF alone does not decide delivery.
Read next
Related articles you may want next.
- TroubleshootingSPF permerror: too many DNS lookups. Count the limit of 10, then shorten the record safelySPF permerror because the record needs more than 10 DNS lookups. Count the terms that query DNS, find the extra ones and shorten the record safely.Read article
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
- TroubleshootingGoogle Workspace: domain verification and MX records that do not matchWorkspace mail needs a verified domain and the MX host smtp.google.com. Compare dig results with Google's values, and leave working aspmx records alone.Read article
Risks and limits
- Google's "10 include: tags" and RFC 7208's 10 DNS-querying terms are not the same ceiling. Receivers implement the RFC.
- Domain-host field names differ. Follow that host's SPF help for the clicks.
- A partner-sold domain may already have SPF. Google says: "To check if SPF is already set up for your domain, use one of many free tools available on the internet."
Sources
- Set up SPF — Google Workspace Help, last updated 2026-11-10 UTC, accessed 22 November 2026
- RFC 7208: Sender Policy Framework (SPF) — IETF, April 2014, accessed 22 November 2026
- BIND 9 manual pages: dig — ISC, version 9.20.9, no date shown, accessed 22 November 2026
This article was originally published on .