Almost everything written about SPF stops at "publish the record and end it in -all". That is fine, but it leaves out the most common way a correct SPF stops working: using up the DNS lookup budget.
What the rule says
RFC 7208, section 4.6.4 requires that evaluating an SPF record cost no more than 10 DNS lookups. The include, a, mx, ptr, exists and redirect mechanisms count. ip4 and ip6 do not, because they are literal addresses and there is nothing to ask.
What almost nobody notices: every include drags along the lookups of the record it includes. If you include your email provider and that provider in turn includes three of its own services, you have already spent four and not one.
Why it is a silent failure
Once you go past 10, the receiving server does not say "your SPF is too long". It returns PermError, and the RFC is explicit that a PermError is treated as if the domain had no SPF.
You published SPF, it looks perfect in any superficial checker, and for practical purposes it does not exist.
There is no bounce to warn you, no alert, no error in your panel. All that happens is that some of your legitimate email starts landing in spam. And because it arrived by accumulation — you signed up for a campaign tool, then a CRM, then an invoicing system — nobody connects the problem to the day it broke.
What we found in Mexican brands
We measured the SPF of ten large US domains by resolving the full include chain, just as a mail server would. On 16 August 2026 it looked like this:
| Domain | Lookups | Headroom | Situation |
|---|---|---|---|
| ebay.com | 10 / 10 | 0 | no headroom |
| airbnb.com | 8 / 10 | 2 | on the edge |
| uber.com | 7 / 10 | 3 | comfortable |
| walmart.com | 5 / 10 | 5 | comfortable |
| ups.com | 5 / 10 | 5 | comfortable |
| salesforce.com | 4 / 10 | 6 | comfortable |
| target.com | 3 / 10 | 7 | comfortable |
| fedex.com | 2 / 10 | 8 | comfortable |
| delta.com | 1 / 10 | 9 | comfortable |
| nike.com | 1 / 10 | 9 | comfortable |
None of them is broken today. But two out of ten are at 8 or more, and eBay has not a single lookup of headroom. For eBay, signing up for one more marketing tool — just one — breaks its SPF completely. With no warning.
If this happens to eBay, with thousands of engineers, it is worth asking how the record of a thirty-person company is doing after adding services without keeping count.
How many lookups does your domain spend?
Our checker resolves the whole chain and tells you in seconds. It asks for no sign-up and no access to anything.
How to count them yourself
By hand: take your record, count the mechanisms that query DNS, and for each include repeat the exercise with the included record. A real example, eBay's:
v=spf1 include:c._spf.ebay.com include:p._spf.ebay.com
include:p2._spf.ebay.com ~all
include:c._spf.ebay.com 2 (1 + 1 from its own chain)
include:p._spf.ebay.com 5 (1 + 4 from its own chain)
include:p2._spf.ebay.com 3 (1 + 2 from its own chain)
──────────────────────────────────
total 10
The ~all at the end does not count: it queries nothing. It is a detail that breaks many home-made counters, ours included when we wrote it — it inflated the total and declared healthy domains broken until we fixed it.
How to fix it
1. Remove what you no longer use
It is the first thing to do and often enough on its own. SPF records accumulate providers that were cancelled years ago and nobody removed. Each one costs at least one lookup.
2. Flatten what doesn't change
An include can be replaced by the ip4 addresses that record authorises, and ip4 entries are free in lookup terms. The downside is serious: if the provider changes its IPs and you don't find out, your email stops passing. Flattening works for stable providers and requires periodic review. Don't do it with Google or Microsoft, which rotate addresses.
3. Split by subdomain
The limit is per record evaluated, not per company. If your campaigns go out from envios.[your-domain].com, that subdomain carries its own SPF with its own budget of 10, and the main domain is freed up. It is the cleanest solution when there are many services, and the one we use by default.
include and redirect, counting the mechanisms that query DNS as per RFC 7208 §4.6.4. These are public lookups: anyone can repeat them and get the same thing. The data is from 16 August 2026 and changes as soon as each company touches its record.Keep reading
- SPF, DKIM and DMARC explained without jargon What each one does and why the three together are what decides whether your email arrives.
- Your DMARC on p=none is not protecting you Publishing it is not the same as switching it on. Three of ten Mexican brands stopped halfway.