Free SPF checker
Grades your SPF record from A to F: the record itself, its all rule and all 10 DNS lookups, with where each one goes and a corrected record when one is safe to give. Free, no signup.
Why SPF matters for a small business
If your quotes, invoices or enquiry replies land in spam, email authentication is the first place to look. SPF (Sender Policy Framework) is the record on your domain that lists which services may send email as you: your email provider, plus anything else that sends on your behalf, like a booking system, invoicing tool or newsletter platform. Receiving servers check it, and a missing or broken record makes your genuine mail look forged.
This checker reads your SPF record from public DNS, follows every include the way a receiving server does, and grades the result from A to F. It doesn't send any email, and nothing on your mail server changes.
What this checker tests
One record, not two. Having two v=spf1 records is a common mistake after switching provider, and it makes SPF fail for every message.
Every term is one SPF understands. A typo such as inculde: is a permanent error: receivers give up on the whole record. We also flag terms that sit after the all rule, because receivers stop reading at all and never see them, and the ptr mechanism, which the standard discourages.
The all rule. The record should end with ~all or -all. +all lets anyone send as you, and ?all offers no protection.
The 10-lookup limit. Every include:, a, mx, ptr, exists and redirect costs a DNS lookup, including the ones inside the records you include. We follow the whole chain, count them, and show where each lookup comes from. If you're over the limit, we tell you by how much.
Broken includes. An include pointing at a service you no longer use, or a mistyped domain, is a permanent error.
Your mail provider is listed. If your mail servers are Google Workspace or Microsoft 365 and the record doesn't include them, mail you send through them can fail SPF.
How the grade works
The grade runs from A to F, and the report puts the top fix first. One valid record, a protective all rule and staying well inside the lookup limit carry most of the weight. Eight to ten lookups still works, but costs a few points, because one new sending service could tip you over.
Some problems cap the grade however well the rest scores:
- No SPF record, or more than one, is an F.
- A permanent error (over 10 lookups, a broken include or a term SPF doesn't recognise) caps you at E, because SPF then fails for every message.
?all, or noallrule at all, caps you at D.+all, which lets anyone send as you, is an F.
A domain with no mail servers is graded differently. If it never sends email, the only right record is v=spf1 -all, which tells receivers to refuse anything claiming to come from it. A parked domain set up that way scores an A.
Your corrected SPF record
When we can build a better record without guessing, the result includes one to paste in as a TXT record on your domain:
- Two or more records: we merge them into one, keeping every sender from each.
?all,+allor noallrule: we keep every sender you list and end the record with~all.- A domain that sends no email: you get
v=spf1 -all.
We never add a service you haven't listed ourselves, because a guessed list could block your genuine mail. If you have no SPF record at all, the result tells you what to include for your mail provider instead.
Getting under 10 lookups
There is no ready-made record for this one, because the right answer depends on what you still use. In order:
- Remove any service you no longer send through. Old marketing tools and previous email providers are the usual culprits.
- Move bulk senders, such as a newsletter or marketing platform, to a subdomain like
news.yourdomain. Each subdomain has its own SPF record and its own 10 lookups. - Replace an
include:with theip4:andip6:ranges it publishes. This is called flattening. It works, but providers change their ranges without warning, so only do it with a tool that keeps them up to date.
SPF isn't enough on its own
SPF checks the hidden envelope sender, not the From address people see, and it doesn't tell receivers what to do when a check fails. That's DMARC's job. Once your SPF is right, use the DMARC and email security checker to grade your SPF, DKIM and DMARC together. The free website audit also checks SPF and DMARC alongside everything else that affects whether your site and email are trusted.
Common questions
Straight answers about what this check does, and doesn't do.
What is an SPF record?
SPF (Sender Policy Framework) is a TXT record on your domain listing the servers allowed to send email as you. Receiving mail servers check it to spot forged mail. You should have exactly one, starting v=spf1 and ending ~all or -all.
What is the SPF 10 lookup limit?
Checking SPF can make at most 10 DNS lookups, counting every include:, a, mx, ptr, exists and redirect, including those inside the records you include. Go over and SPF fails for every message. This checker follows your includes and counts them for you.
Should I use ~all or -all?
~all (soft fail) marks mail from unlisted servers as suspicious; -all (hard fail) rejects it. ~all is the common, safer choice while you're still finding every service that sends for you. Once DMARC is enforcing, either works well.
How do I get my SPF record under 10 lookups?
Remove any service you no longer send through first. Then move bulk senders, such as a newsletter tool, to a subdomain like news.yourdomain, which gets its own 10 lookups. Replacing an include with the IP ranges it publishes (flattening) also works, but those ranges change without warning, so only do it with a tool that keeps them up to date.
Is SPF enough to stop someone faking my emails?
No. SPF checks the hidden sender address, not the From address people see, and it doesn't tell receivers what to do when a check fails. DMARC does both, using SPF and DKIM. Once your SPF is right, check DMARC with our DMARC and email security checker.
From the blog
All postsHTTPS and Security Headers: The Trust Signals Most Sites Get Wrong
The padlock icon is just the start. Here's what HTTPS and security headers actually protect - and why Google and visitors both care.
Read moreWhat Is a Website Security Audit? A Plain-English Guide
A website security audit checks your site for weaknesses an attacker could exploit. Here's what it covers, what you can check yourself, and when to call in a professional.
Read moreHow to Audit Your Website: The Technical SEO Checklist Every Small Business Should Run
What an SEO audit actually checks, how to run one yourself for free, and the ordered checklist of technical fundamentals that decide whether Google can find, crawl, and rank your site.
Read moreOther free tools
Quick checks for the things that most often go quietly wrong.