Why SPF decides whether your emails get through
SPF is your domain’s list of approved senders. When someone receives an email from [email protected], their email server looks up your SPF record and checks that the email came from a server on that list. If it did, the email passes SPF. If not, the server treats it as suspicious, and your DMARC policy decides what happens next.
Without SPF, inbox providers can’t tell your real emails from fakes, so more of your emails end up in spam. Since February 2024 Google and Yahoo require SPF or DKIM from everyone who emails their users, and both from anyone sending in bulk.
What your result means for your business
One record
Your domain must have exactly one TXT record starting with v=spf1. Two records break SPF for every email.
The ending
~all marks unlisted senders as suspicious, and -all rejects them. ?all does nothing and +all lets anyone send as you.
Lookups
Receivers may do at most 10 DNS lookups for your SPF, counting the includes inside your includes. We add them all up for you.
Includes
Each include: brings in a service’s own list of servers. An include that points to a name with no SPF record adds nothing.
SPF records for common email providers
Use the record for the provider that hosts your mailboxes, then add an include for every other service that sends email as you (newsletters, invoicing, your website’s contact form).
| Provider | SPF record |
|---|---|
| Google Workspace | v=spf1 include:_spf.google.com ~all |
| Microsoft 365 | v=spf1 include:spf.protection.outlook.com -all |
| Zoho Mail | v=spf1 include:zohomail.com ~all |
| GoDaddy email | v=spf1 include:secureserver.net -all |
| Rackspace Email | v=spf1 include:emailsrvr.com ~all |
| Google Workspace plus SendGrid | v=spf1 include:_spf.google.com include:sendgrid.net ~all |
Moving from one provider to another? During the move, include both, then remove the old one once all mailboxes have moved. We do this for you in every Googally migration.
Common SPF errors and how to fix them
“Multiple SPF records”
Usually left over from an old provider or added by a second service. Combine every include into one record and delete the other.
“Too many DNS lookups” (permerror)
Remove services you no longer use. For a service that sends from a few fixed addresses, replace its include with ip4: ranges. Avoid ptr entirely.
Emails from a tool still fail SPF
The tool isn’t in your record. Find its include in the tool’s help pages (search “SPF”) and add it before the ~all.
Record saved but checker shows the old one
DNS changes can take up to an hour or two to show, depending on the record’s TTL. Wait, then check again.
How to add or edit your SPF record
- Sign in where your domain’s DNS is managed (often GoDaddy, Namecheap, Squarespace or Cloudflare).
- Open the DNS records for your domain and look for a TXT record with host
@that starts withv=spf1. - If there is one, edit it. If not, add a TXT record with host
@. Paste your record from the table above. - Save, wait a few minutes, and run this checker again.