Free SPF checker

SPF checker: is your record valid, or one lookup from failing?

See duplicate records, the full recursive lookup chain, unresolved include targets, recognized sending providers, record length, and the hard 10-lookup limit.

How the lookup count is calculated

We fetch your domain's SPF record (the TXT record starting with v=spf1), then walk every include: mechanism recursively — because an included record can include others, and all of those count against the same shared limit of 10.

The breakdown below the result shows exactly which part of the chain is contributing lookups, including repeated references, provider labels, duplicate root records, and include or redirect targets that do not return an SPF record. If you're over the limit, you can see which included provider is the heaviest and decide whether to drop it, flatten it, or push back on whoever asked you to add it.

This check reflects your SPF setup only. A domain can have flawless SPF and still allow spoofed mail if DMARC isn't enforcing alignment — worth checking with our DMARC checker too.

What each SPF result means

The checker reads the published policy. A receiver evaluates that policy against one message: the connecting IP and the envelope (Return-Path) domain. These are the results you will see in Authentication-Results headers and bounce messages, and the playbook that investigates each one.

pass
The connecting IP matched an authorizing mechanism. DMARC still needs the envelope domain to align with the visible From domain. SPF passes but DMARC fails →
none
No SPF policy was found for the evaluated domain, which is often a bounce subdomain rather than the domain you checked here. Find the domain that was checked →
neutral
A ?all or another ? mechanism matched. The policy makes no assertion either way, and DMARC does not count it as a pass. Investigate an SPF neutral result →
softfail
The ~all mechanism matched: the IP is not authorized, but the domain asks receivers not to reject on SPF alone. Softfail vs hardfail →
temperror
A DNS lookup failed temporarily during evaluation. Receivers usually defer with a 4xx reply and retry. Investigate an SPF TempError →
permerror (lookups)
Evaluation needed more than 10 DNS-querying mechanisms or hit more than 2 void lookups. Find empty answers in the chain →
permerror (include)
An include target publishes no SPF record, so evaluation stops when it reaches that mechanism. Fix a missing include target →
permerror (syntax)
The record does not parse, often because two TXT strings were joined without a space. Check split TXT strings →

Common questions

What is the SPF 10-lookup limit?+

RFC 7208 caps SPF evaluation at 10 DNS lookups (mechanisms like include, a, mx, ptr, and exists each count). Go over it, and the SPF check is required to return a "permerror" — many mail servers treat that as an outright SPF failure, which can land legitimate mail in spam or get it rejected.

Why is my lookup count so high?+

Every email tool you connect — your CRM, invoicing software, marketing platform, helpdesk — typically asks you to add an include: mechanism to your SPF record. Each include is itself a lookup, and if that included record has its own includes, those count too. It adds up fast without anyone noticing.

How do I fix an SPF record that's over the limit?+

The standard fix is "flattening": resolving all the includes down to their actual IP addresses and listing those directly instead, which removes the lookups those includes were causing. It works, but the IPs of your email providers can change, so a flattened record needs to be re-checked periodically or it silently goes stale.

Does this tool check void lookups too?+

It flags include and redirect targets that return no SPF record, which catches the most actionable unresolved targets in a recursive chain. SPF macro expansion and live evaluation of a particular sending IP can create additional runtime behavior, so this is a structural DNS check rather than a full mail-server simulation.

I don't have an SPF record at all — is that better or worse than being over the limit?+

Worse. No SPF record means there's no list at all of who's allowed to send mail for your domain, which is a bigger gap than a record that's merely over-provisioned. Either way, the fix starts with seeing your actual record, which is what this tool shows you.