Check your SPF record, count DNS lookups against the limit of 10, or generate a new SPF record.
Last updated:
All lookups go to Google Public DNS; nothing is stored.
| Part | Meaning |
|---|---|
| v=spf1 | Start of every SPF record |
| include:_spf.google.com | Allow another provider's servers |
| ip4:203.0.113.10 | Allow one IPv4 address or range |
| ip6:2001:db8::/32 | Allow an IPv6 range |
| a / mx | Allow your website or mail server IPs |
| ~all | Soft fail everything else (recommended start) |
| -all | Hard fail everything else (strict) |
| Sender | Add this |
|---|---|
| Google Workspace | include:_spf.google.com |
| Microsoft 365 | include:spf.protection.outlook.com |
| Amazon SES | include:amazonses.com |
| SendGrid | include:sendgrid.net |
| Mailgun | include:mailgun.org |
| Salesforce | include:_spf.salesforce.com |
| India sender | Add this |
|---|---|
| Zoho Mail (India data centre, zoho.in accounts) | include:zoho.in |
| Zoho Mail (global) | include:zoho.com |
| Hostinger Email | include:_spf.mail.hostinger.com |
| GoDaddy email | include:secureserver.net |
Enter your domain and press Check SPF. You will see the record, lookup count, policy and any problems.
An SPF check may use at most 10 DNS lookups for include, a, mx, ptr, exists and redirect, including nested ones. Going over makes SPF fail.
No. Two SPF records make SPF fail. Merge them into one TXT record.
Start with ~all. Move to -all once you are sure every service that sends your email is listed.
A permanent error, usually from too many lookups, two SPF records or bad syntax. Receivers treat it like no SPF.
Yes. Gmail requires SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders.