In short. SPF is the list of servers allowed to send emails on behalf of your domain. If it is missing or badly written, your emails risk being sent to spam or rejected by your recipients' mail systems. It is up to you, or to your IT provider who manages your domain, to add one line at your domain host, in its directory (the DNS). The line takes a few minutes to create, then Google says it can take up to 48 hours before the check works. Make sure you have only one list per domain: with two, the check fails for all your emails.
If Google Workspace is the only service that sends email for your domain, Google recommends this SPF record: v=spf1 include:_spf.google.com ~all. You create it at your DNS host, as a TXT record on the domain, not in the Admin console. If an SPF record already exists, add include:_spf.google.com to it instead of creating a second one. Allow up to 48 hours before it works.
SPF tells receiving mail servers which servers may send email for your domain. Without it, Gmail and other providers send more of your messages to spam, and DMARC can't work.
Last verified: November 18, 2026, against Google Workspace's official help.
Before you start: list everything that sends as you
One SPF record must cover everything that sends email as your domain:
- Google Workspace (Gmail);
- your website, if it sends email (contact forms, orders);
- your tools: newsletter, CRM, invoicing, customer support.
Each tool's documentation gives the include: or IP address to add.
Step 1: check whether an SPF record already exists
nslookup -type=TXT your-domain.comLook for a line that starts with v=spf1. If there is one, go to step 3.
Step 2: create the SPF record
At your DNS host, add a record:
- Type:
TXT - Name / host:
@(or leave it blank, depending on the host: it means the domain itself) Value:
v=spf1 include:_spf.google.com ~all
If other services send as your domain, add them to the same value, before the ~all. Example with a newsletter tool:
v=spf1 include:_spf.google.com include:servers.example-tool.com ~allFor the exact clicks at your DNS host, see our guides for Cloudflare, GoDaddy and Namecheap.
Step 3: edit an existing SPF record
Google is clear on this: each domain has its own SPF record, and only one. With two SPF records on the same domain, the check fails for all your email. Edit the existing line and insert include:_spf.google.com before the final ~all or -all.
If the old record contains an include: for a service you no longer use (a former mail host, an abandoned tool), remove it: it uses up DNS lookups for nothing.
Step 4: stay under 10 DNS lookups
Past 10 DNS lookups, SPF fails with a permanent error (RFC 7208). Each include:, a, mx, exists and redirect counts, as do any include: nested inside the ones you cite. On November 18, 2026, include:_spf.google.com counted for only one lookup: Google publishes its address ranges directly there. It's the tools you add alongside that push you over the limit. Our free SPF checker does the count for you.
~all or -all?
Google recommends ~all: receiving servers then mark email from unlisted servers as suspicious, without rejecting it. It's the safest value until you're certain you've listed every sender. The real protection against spoofing then comes from DMARC.
Step 5: wait, then check it works
Google gives a maximum of 48 hours before SPF authentication works. After that:
- Run
nslookup -type=TXT your-domain.comagain: exactly one line should start withv=spf1. - Send an email from Gmail (your Workspace account) to a personal Gmail mailbox, open it, choose Show original and look for
SPF: PASS.
Verify it's fixed. AttackScout reads your SPF record from the internet, counts DNS lookups, spots duplicates and checks the
Frequently asked questions
Are my subdomains covered?
No. Google says so: each subdomain that sends email needs its own SPF record.
How many include: entries can I add?
Google's help mentions at most 10 include: entries. The real limit is 10 DNS lookups in total, nested ones included: in practice, you hit it before 10 include: entries.
Is SPF enough for Gmail?
No. Gmail requires SPF or DKIM from every sender, and SPF, DKIM and DMARC above 5,000 messages a day to its users. Also turn on DKIM in the Admin console and publish a DMARC record: see our DMARC guide for Google Workspace.
Technical details
Exact configuration. A single TXT record on the domain:
your-domain.com. 3600 IN TXT "v=spf1 include:_spf.google.com ~all"Why. SPF (RFC 7208) checks the envelope address (MAIL FROM) of a message. ~all (softfail) flags other servers without rejecting them; DMARC treats it as a failure.
To check it yourself.
dig +short TXT your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7208
Sources
Accessed November 18, 2026.
- Google Workspace, Set up SPF (updated November 10, 2026): https://knowledge.workspace.google.com/admin/security/set-up-spf
- Google, Email sender guidelines (accessed November 12, 2026): https://support.google.com/mail/answer/81126?hl=en
- DNS record for
_spf.google.com, read on November 18, 2026 (nslookup -type=TXT _spf.google.com):ip4:andip6:addresses only, no nestedinclude:. - IETF, RFC 7208 (SPF): https://www.rfc-editor.org/rfc/rfc7208