When mail from your domain lands in spam or fails authentication, the SPF record is one of the first things to read. This page shows how to check an SPF record, what the lookup count means, and what the result cannot tell you.
Key facts:
- An SPF record is a DNS TXT record on your domain that starts with
v=spf1(RFC 7208). - RFC 7208 allows at most 10 DNS lookups per SPF evaluation, and
include,a,mx,ptr,existsandredirecteach count toward it. - A domain must publish only one SPF record, because two
v=spf1records produce a permerror (RFC 7208). - Per the BillionVerify SPF Checker, the result is the record text plus a lookup count out of 10, with nested
includeandredirecttargets followed. - Per the BillionVerify SPF Checker, each IP address can run 10 lookups a minute and 50 an hour.
How to check an SPF record
- Enter the domain that sends the mail, such as
example.com. Use a bare domain, not a URL or an email address. - Run the check. The tool reads the TXT records at that name and picks the one that starts with
v=spf1. - Read the record first, then the lookup count under it.
If a sending service handles your mail, the envelope sender may sit on the service’s domain. SPF checks that domain, not the visible From address.
What the SPF result tells you
The record exists and the count is 10 or lower
The record is there and stays within the limit. Now compare it with reality. List every service that sends for you, then confirm each one appears as an include, an ip4 range or another mechanism. A service that is missing fails SPF for its own messages.
The count is above 10
The tool adds a note that receivers can fail SPF with a permerror. In practice, mail can fail even though every include looks right. Remove senders you no longer use first. Then replace stable ranges with ip4 entries, because ip4 costs no lookups. Only flatten ranges you control, since provider ranges change.
No SPF record found
This message covers a missing record and a name that does not exist. Check the spelling of the domain, then publish a record. If you already published one, the DNS panel may have saved it on a different name.
Two records, a cut-off value or a lookup error
The tool shows the first v=spf1 record it finds and does not warn about a second one. To see every TXT value on the domain, run a TXT query in the DNS Checker. A value that looks cut off usually means the DNS panel split or trimmed a long string on save. A “DNS lookup failed” message means the query itself failed, so run it again.
What this check does not cover
The tool does not test a real message. It does not tell you whether ~all or -all suits your setup either. It shows the record, and you read the ending yourself.
SPF also protects only the envelope sender. A clean result still leaves the visible From address open to spoofing, which is the job of DMARC.
If your record is clean and bounces stay high, the problem is probably the list. Run doubtful addresses through a free email address checker. It gives 20 free full checks per IP every 24 hours, no sign-up.
What to check next
Move to DKIM, then DMARC. SPF alone rarely explains a spam-folder problem. One bad address can also look like an authentication fault, so confirm an email address is valid before you change DNS for a single stubborn bounce.