Free SPF checker
SPF Record Checker & Generator
Check that your SPF record is valid, stays under the 10-lookup limit and protects your domain. Then build a correct one in seconds.
Free, no sign-up. We only read public DNS records and do not keep what you check.
Result look wrong, or not sure what to change? A GoProIT technician can check it with you over a secure remote session. $59 per fix, Monday to Friday 8am to 8pm Eastern.
Book a technician(844) 734-1288SPF record generator
Tick every service that sends email using your domain. The record updates as you go. Replace your existing SPF record with it: never add a second one.
What SPF does
SPF (Sender Policy Framework) is a TXT record at your domain that lists the servers allowed to send email for it. When a message arrives claiming to be from yourcompany.com, the receiving server checks whether it came from one of those servers. If not, SPF fails.
The four SPF rules people break most
- Only one SPF record per domain. Two records starting with
v=spf1cause a PermError, and SPF fails for all your mail. This usually happens when a new service tells you to “add” a record. Merge them instead. - No more than 10 DNS lookups. Every
include:,a,mx,existsandredirectcounts, including the ones inside each include. This checker counts them all for you. - End with ~all or -all.
+alllets anyone send as you, and?allgives almost no protection. - Don’t use ptr. It is slow, deprecated, and ignored by many receivers.
~all or -all?
~all (soft fail) marks mail from unlisted servers as suspicious. -all (hard fail) says to reject it. With a DMARC policy in place, receivers follow DMARC anyway, so ~all is the safe, common choice. Use -all only when you are sure every sender is listed.
How to read your SPF check results
When you check an SPF record for a domain, the tool reads the TXT record that starts with v=spf1, follows every include, and counts the DNS lookups. Here is what each part of the result tells you.
- Record found: the exact text published at your domain. If you see two lines starting
v=spf1, that is a PermError on its own, whatever they contain. - Lookup count: how many of the 10 allowed DNS lookups your record uses. 8 or 9 works, but leaves no room for the next service you add.
- Void lookups: includes or
a/mxterms that point to names with no answer. The SPF standard (RFC 7208) suggests receivers allow no more than two of these before failing the check. They usually come from a service you stopped using. - Syntax warnings: typos such as
include: spf.protection.outlook.comwith a space,v=spf1missing from the start, or text afterall, which receivers ignore.
What receivers do with each SPF result
| Result | Meaning |
|---|---|
| pass | The sending server is listed in your record. |
| softfail | Not listed, and your record ends in ~all. Usually delivered but marked as suspicious. |
| fail | Not listed, and your record ends in -all. |
| neutral | Your record ends in ?all, so it makes no claim either way. |
| temperror | A DNS lookup timed out. Normally retried later. |
| permerror | The record is broken (two records, too many lookups, bad syntax). Treated as a fail by most receivers. |
SPF includes for common small-business senders
Each service that sends mail using your domain in the envelope sender needs to be covered. These are the values the big providers publish:
| Service | What to include |
|---|---|
| Microsoft 365 | include:spf.protection.outlook.com |
| Google Workspace | include:_spf.google.com |
| GoDaddy email (Workspace Email) | include:secureserver.net |
| SendGrid | include:sendgrid.net |
| Mailgun | include:mailgun.org |
| Amazon SES | include:amazonses.com |
Always confirm against the service’s own help page before you add anything. Many newsletter and CRM tools now send with their own return-path domain, which means their SPF check happens against their domain, not yours. For those, adding an include to your record does nothing. What they need from you is DKIM, set up through their “domain authentication” screen.
How to merge two SPF records into one
This is one of the most common SPF fixes. Say your DNS has these two TXT records:
v=spf1 include:spf.protection.outlook.com -all
v=spf1 include:sendgrid.net ~all
Combine the include terms into a single record and keep one all at the end:
v=spf1 include:spf.protection.outlook.com include:sendgrid.net ~all
Then delete the second record. At GoDaddy, that’s in your domain’s DNS page under DNS Records. In Cloudflare, open the domain, go to DNS, then Records, and filter by TXT. At Namecheap, it’s under Advanced DNS. Edit one record, paste the merged value, save, and remove the other.
Run the SPF checker again a few minutes later. You should see one record and a lookup count that adds up the two services.
How to fix “too many DNS lookups”
If the checker counts more than 10 lookups, receivers return a PermError and SPF fails for every message. Work through these options in order:
- Remove services you no longer use. Old web hosts, a previous email provider or a trial marketing tool are the usual culprits. This alone fixes most records.
- Drop includes that aren’t needed. As above, many tools check SPF on their own domain. Removing their include costs you nothing.
- Replace
aandmxwithip4. If your own server or office sends mail from a fixed IP, list it asip4:203.0.113.10.ip4andip6terms don’t count toward the limit. - Move bulk senders to a subdomain. Send newsletters from
news.yourcompany.com, which gets its own SPF record with its own 10 lookups. - Flatten as a last resort. Flattening replaces includes with the IP ranges behind them. It works, but providers change their IPs without notice, so a flattened record needs regular updates or it slowly breaks.
If you’d rather not edit DNS yourself, a technician can clean up the record over a remote session for $59.
How to test SPF manually
You can look up the SPF record for a domain without any tool:
- Windows Command Prompt:
nslookup -type=txt yourcompany.com - PowerShell:
Resolve-DnsName yourcompany.com -Type TXT - macOS Terminal:
dig txt yourcompany.com +short
Look for the line starting with v=spf1. To check that a real message passed, send one to a Gmail address, open it, and choose Show original from the three-dot menu. The SPF line shows PASS, SOFTFAIL or FAIL with the IP address that sent it. The email header analyzer reads the same information from a pasted header.
Frequently asked questions
Where do I add the SPF record?
At the DNS host your domain’s nameservers point to (for example Cloudflare, GoDaddy or your web host). Create a TXT record with host @ (or your domain name) and paste the record as the value. If an SPF record already exists, edit it instead of adding another.
What does SPF PermError mean?
It means receivers could not evaluate your SPF record, so they treat it as failed. The usual causes are two SPF records on the domain, more than 10 DNS lookups, or a typo in an include. This checker shows which one applies.
What SPF record do I need for Microsoft 365?
If Microsoft 365 is your only sender, use v=spf1 include:spf.protection.outlook.com -all (or ~all). Add an include for every other service that sends as your domain, such as a newsletter or invoicing tool.
Is SPF enough to stop spam and spoofing?
No. SPF only checks the hidden envelope sender, not the From address people see. You also need DKIM and a DMARC policy to stop look-alike emails reaching your customers.
Do subdomains need their own SPF record?
Yes, if they send mail. SPF isn’t inherited, so billing.yourcompany.com is checked against its own TXT record, not the one on yourcompany.com. A subdomain that never sends mail can publish v=spf1 -all to stop anyone using it.
Do ip4 and ip6 count toward the 10-lookup limit?
No. Only terms that make the receiver run a DNS query count: include, a, mx, ptr, exists and redirect. Lookups inside each include count too, which is why one include can use three or four of your ten.
How long does a new SPF record take to work?
Usually a few minutes for a new record. If you edited an existing one, receivers may use the old version until its TTL runs out, which is often one hour and at most a day. Check again here after a short wait.
What does SPF softfail mean in an email header?
It means the message came from a server your record doesn’t list, and your record ends in ~all. Most receivers still deliver it, but it counts against the message. If it’s your own mail, add the missing service to your SPF record or make sure DKIM passes for it.
Related guides
- How to set up an SPF record, step by step
- How to set up DMARC
- Emails going to spam: how to fix it
- Fix Gmail error 550 5.7.26
Get help from a technician
More free tools
Email & domainEmail Domain Health CheckOne check for MX, SPF, DKIM, DMARC and blocklists, with a score out of 100 and a fix list.Open tool
Email & domainMX Record LookupSee which mail servers receive email for a domain, their priority, IPs and provider.Open tool
Email & domainDMARC Checker & Record GeneratorCheck your DMARC policy and reports, and generate a DMARC record.Open tool
Email & domainDKIM Record CheckerFind and test DKIM keys by selector, including key size and revoked keys.Open tool
Email & domainEmail Blacklist CheckCheck a mail server IP or domain against 14 email blocklists.Open tool
Email & domainFree Email Signature GeneratorBuild a clean HTML signature and paste it into Outlook, Gmail or Apple Mail.Open tool
Email & domainEmail Header AnalyzerPaste email headers to see authentication results, spam verdicts and delivery delays.Open tool
DNS & websiteDNS LookupSee every DNS record for a domain or hostname: A, MX, TXT, CNAME, NS and more.Open tool Free tools find it. We fix it.
Want a technician to sort it out for you?
One-time remote fix for $59, or unlimited help for your whole team at $49 per user per month. No contract and no setup fee.