Lookup count
Includes are followed recursively, because going past ten lookups makes SPF fail.
Monitor
Protect
Manage
By role
Security
Renewals
Monitoring
Free tool · No signup
Fetch a domain's SPF record and test it: one record only, no more than ten DNS lookups once includes are followed, and a sensible ending.
No domain handy?
Lookups run live and are not stored.
Every result is pulled live, so you see the state of the domain right now.
Includes are followed recursively, because going past ten lookups makes SPF fail.
More than one SPF record is a permanent error. The tool counts them.
Reads whether the record ends in -all, ~all, ?all or the unsafe +all.
| Ending | Meaning | Verdict |
|---|---|---|
| -all | Reject mail from servers not listed | Strict, good once the list is complete |
| ~all | Mark unlisted senders as suspicious | Common and safe default |
| ?all | Neutral, no opinion | Weak |
| +all | Anyone may send as the domain | Never use |
| No "all" | No policy for unlisted senders | Incomplete |
The domain in your From address.
Each include, a, mx, exists and redirect counts. Going past ten makes the whole record fail.
Merge multiple SPF records into one and end with ~all or -all.
RFC 7208 allows at most ten DNS-lookup mechanisms (include, a, mx, ptr, exists, redirect) while evaluating a record. More than that is a permanent error and mail can fail SPF.
No. Publishing more than one makes SPF return a permanent error. Merge them into a single record.
~all is a soft fail that marks unlisted mail suspicious. -all asks receivers to reject it. Start with ~all and tighten once you know every sender.
No. SPF checks the envelope sender, not the visible From address. DMARC ties the checks to the From domain.
Every new email service adds an include and pushes you toward the 10-lookup limit. Aepto DNS monitoring flags when your TXT records (SPF, DKIM, DMARC) are removed or loosened.
