Free SPF checker
Check your SPF record for errors and see which services it authorises to send mail for your domain.
Example report
example.com- 1 Medium
SPF needs too many DNS lookupsMedium
Evaluating the SPF record for example.com needs more than 10 DNS lookups (11 counted before the count stopped); receivers stop at 10.
Next step
Remove unused includes, replace
a/mx/ptrmechanisms with IP ranges where stable, or use your provider's flattened include.
SPF record
v=spf1 mx include:_spf.google.com include:spf.protection.outlook.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net ~all11 of 10 DNS lookups is over the limit: receivers may treat the record as an error (permerror).
Where the lookups come from, record by record:
example.com: 6 lookups (mx, include:_spf.google.com, include:spf.protection.outlook.com, include:sendgrid.net, include:mailgun.org, include:servers.mcsv.net)_spf.google.com: 3 lookups (include:_netblocks.google.com, include:_netblocks2.google.com, include:_netblocks3.google.com)spf.protection.outlook.com: 1 lookup (include:spfa.protection.outlook.com)mailgun.org: 1 lookup (include:_spf.mailgun.org)
What the SPF check looks at
The record
Find the SPF record among the TXT records, and check there is only one.
Syntax
Check that every mechanism and modifier parses as receivers expect.
How it ends
See whether servers it does not list are failed, soft-failed or let through.
DNS lookups
Count the lookups its includes need against the limit of 10.
The result shows the trail of records read, include by include, so you can see where the lookups come from.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
SPF needs too many DNS lookupsMedium
Evaluating the SPF record needs more than the 10 DNS lookups the standard allows.
v=spf1 mx include:_spf.google.com include:spf.protection.outlook.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net ~all (11 lookups counted)Receivers stop evaluating after 10 lookups and treat the result as an error, so legitimate mail may fail SPF.
Remove unused includes, replace a/mx/ptr mechanisms with IP ranges where stable, or use your provider's flattened include.
Common SPF issues you can put right
SPF needs too many DNS lookupsMedium
Each service you add brings its own includes, and past 10 lookups receivers stop evaluating the record. Remove services that no longer send for you before anything else.
SPF does not reject unlisted sendersHigh
A record that ends in +all or ?all lets servers it does not list pass or go unjudged. List every service that sends for you, then end the record in ~all or -all.
More than one SPF recordMedium
Receivers treat two SPF records as an error and ignore SPF for the domain. Merge them into one record.
No SPF recordMedium
The domain does not publish an SPF record.
SPF record has errorsMedium
The SPF record contains syntax that receivers will reject.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- The TXT records at the domain, and which of them are SPF records (those starting
v=spf1). A domain with MX records but no SPF record is a finding; a domain with neither is left to the non-sending domain check. - Whether there is exactly one SPF record, as RFC 7208 requires.
- Whether the record parses:
v=spf1first, then valid mechanisms (ip4:,ip6:,a,mx,include:,exists:,ptr,all) and modifiers (redirect=,exp=). - How the record ends:
-alland~allpass;?all, or neither anallnor aredirect=, is a Medium finding;+allor a bareallis High. - The DNS lookups the record needs, following
include:andredirect=into the records they name, counted against the limit of 10. The result shows the count and the trail of records read.
Reading a result
SPF (RFC 7208) lets a domain list the servers allowed to send mail for it. A receiving server compares the address that connected with the record for the domain in the envelope sender (the Return-Path), not the From address people see. DMARC is what ties an SPF pass to the visible From.
The end of the record decides what happens to every server not listed. -all asks receivers to fail them and ~all to soft-fail them; both pass this check. ?all, or a record with no all, gives unlisted servers a neutral result, which protects nothing. +all authorises every server on the internet, so forged mail passes SPF.
Each include:, a, mx, ptr, exists: and redirect= costs a DNS lookup, including those inside included records, and past 10 receivers return a permanent error (permerror) instead of a result. A passing result means one valid record, ending in -all or ~all, within the limit. A count close to 10 is worth trimming before the next sending service is added.
What it does not do
- The check reads public DNS through public resolvers. It cannot tell whether the servers the record lists are really yours, or whether every service that sends as you is listed; DMARC aggregate reports show that.
- It does not send or receive email and does not test how a particular receiver evaluates the record.
- It counts lookups but does not resolve the addresses behind
aandmxterms or check the separate limit on lookups that return no answer (void lookups). It stops counting once past 10, so a count over the limit is a minimum. - It checks the domain entered only. SPF is not inherited, so each subdomain that sends mail needs its own record and its own check.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- What is the SPF 10 DNS lookup limit?
- Evaluating an SPF record may take at most 10 DNS lookups, counting include, a, mx, ptr, exists and redirect terms, including those inside included records. Past 10, receivers return a permanent error and the record gives no protection. Terms such as ip4, ip6 and all cost nothing.
- Should an SPF record end in -all or ~all?
- Either marks unlisted servers as not authorised. -all asks receivers to treat their mail as a fail; ~all asks for a soft fail, which receivers should not reject on alone but may treat with suspicion. Both pass this check; ?all and +all do not.
- Can a domain have two SPF records?
- No. RFC 7208 treats more than one v=spf1 record as a permanent error, so receivers ignore SPF for the domain. Merge them into one record.
- Does an SPF record cover subdomains?
- No. SPF is checked for the exact domain in the envelope sender, so each subdomain that sends mail needs its own record. DMARC is different: a subdomain without a DMARC record is covered by its organisational domain's record.

