Count your SPF lookups before a receiver counts them for you.
SPF allows ten DNS lookups. The eleventh fails all of your mail, and nothing warns you. This checker walks every include the way a receiving server does and shows the count, the tree, and what to cut.
It evaluates the record. It does not just admire it.
A syntax check tells you the record is well formed. That is the easy part. The failures are three includes down.
- The lookup counter
- Every include, a, mx, ptr, exists, and redirect costs one DNS lookup, counted through every nested record. RFC 7208 caps the total at ten. The gauge shows where you stand.
- The include tree
- Each included domain, the record it publishes, and the includes inside that, drawn as a tree with the lookups each branch consumes. This is where you find the provider quietly using four of your ten.
- Void lookups
- Mechanisms that resolve to nothing. More than two and receivers return a permanent error. They are usually leftovers from a service you cancelled.
- How the record ends
- -all, ~all, ?all, or the catastrophic +all, each with what it tells receivers to do about servers you did not list.
- Duplicate records and bad syntax
- Two
v=spf1records, an invalid IP range, a term that is not a mechanism. Each is a permanent error on its own. The fixes are in common SPF errors. - Honest failure states
- If the DNS lookup itself fails, the result says the lookup failed. It does not tell you the record is missing, which would send you off to fix something that is not broken.
The limit is ten. Your providers spend it without asking.
SPF was designed as a guest list. The domain publishes the servers allowed to send its mail; the receiver checks the door. The designers, sensibly worried about a single email triggering hundreds of DNS queries, capped the number of lookups at ten. Then came the era in which every business sends mail through six vendors, each of which publishes an include that includes two more.
So the arithmetic matters. An include for a large mailbox provider can cost three or four lookups by itself. Add a CRM, a newsletter tool, and a help desk, and a record that looks short is over the limit. The result is not a warning. It is permerror, and receivers treat SPF as failed for every message, including the legitimate ones. If you are starting from scratch, read what SPF is first.
Passing SPF is also not the same as passing DMARC. SPF authenticates the Return-Path domain, which with many services belongs to the vendor, not to you. Unless that domain aligns with your From address, the pass does not count, and DKIM has to carry the message. That is the subject of SPF vs DKIM vs DMARC. Check the other half with the DKIM checker and the DMARC checker, or let SPF monitoring recount on a schedule.

What breaks SPF, and what to do about it.
More than ten lookups
Delete includes for services you no longer use. Replace an include that covers one or two fixed addresses with ip4 entries, which cost nothing. Move marketing mail to a subdomain with its own record. Rebuild with the SPF generator.
Two SPF records on one domain
Receivers do not pick one. They fail both. Merge every mechanism into a single record that starts with v=spf1 and ends with one all.
An include that points at nothing
If an included domain publishes no SPF record, the result is a permanent error. It is nearly always a typo or a cancelled vendor. Remove or correct it.
+all at the end
This authorizes every server on the internet to send as your domain. Change it to ~all, or to -all once every sender is listed.
SPF passes and DMARC still fails
The Return-Path domain is the vendor’s, so SPF is not aligned. Set up a custom Return-Path at that vendor, or rely on aligned DKIM. See alignment explained.
The ptr mechanism
RFC 7208 says not to use it: it is slow, and some receivers skip it. Replace it with the actual address ranges or the sending service's include.
How to check an SPF record
Validate the record and count DNS lookups the way receivers do.
- 1
Enter the domain
Use the domain in your Return-Path. For most mailbox providers this is the same as the domain in your email address.
- 2
Read the lookup gauge
Ten or fewer passes. Eight or more deserves attention, because a provider can add a nested include at any time.
- 3
Open the include tree
Find which includes consume the most lookups, and which belong to services you no longer use.
- 4
Edit and recheck
Publish the trimmed record as a single TXT record, wait for the TTL, and run the check again.
Questions about this tool
Straight answers. If yours is not here, ask us and a person will reply.
Over the limit and not sure what to cut?
Send us the domain. We will look at the include tree and tell you which entries are safe to remove and which are carrying your mail.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
The record you checked today is not the record you will have in March.
Start with a free account for DMARC reports. On the Pro plan, SpoofKiller recounts your SPF lookups every six hours and warns you when a provider's change pushes you over.
Related tools and guides
- SpoofKillerFeaturesDMARC analytics, sender identification, spoofing detection, DNS change monitoring, blacklist checks, and reports.Read
- FeatureSPF MonitoringScheduled SPF checks that count DNS lookups the way receivers do, walk every include, and warn you when a record breaks.Read
- SpoofKillerKnowledge BasePlain-English guides to DMARC, SPF, DKIM, spoofing, and deliverability.Read
- GuideCommon SPF ErrorsToo many lookups, two records, a stray +all: the SPF mistakes that break mail, and the fix for each.Read
- GuideDMARC Alignment ExplainedWhy mail can pass SPF and DKIM and still fail DMARC, and what relaxed and strict alignment each require.Read
- GuideEmail Authentication Best PracticesThe habits that keep SPF, DKIM, and DMARC working after the day you set them up.Read
