Table of Contents
- Introduction
- 1. Count Your Current Lookups with an SPF Checker
- 2. Remove Unused Sender Includes
- 3. Replace mx and a Mechanisms with ip4/ip6 Entries
- 4. Delete ptr and Unnecessary exists Terms
- 5. Consolidate Overlapping and Nested Includes
- 6. Move Marketing Senders to a Subdomain
- 7. Use Managed SPF Flattening as a Last Resort
- FAQ
- Conclusion
Introduction
What the 10-lookup limit means for your email
Most ‘Too many DNS lookups’ errors come from chained includes stuffed in by email vendors, not you. Here’s the quickest way to cut lookups, keep mail flowing, and stop the PermError without swapping providers.
Why a PermError can cause DMARC to fail
DMARC treats that PermError as an SPF fail, which puts your email deliverability at risk.

1. Count Your Current Lookups with an SPF Checker
Which mechanisms count toward the limit
Run your domain through an SPF checker that reports lookup count. These terms each use one lookup:
- include
- a
- mx
- ptr
- exists
- redirect
How nested includes inflate the total
The limit is ten lookups, not ten includes. One include can cost seven on its own, because everything inside it counts.
Google’s include is one lookup, but its record includes others, and those count too.
2. Remove Unused Sender Includes
Auditing old vendors and retired tools
List every include in your SPF record and match each one to a live service. Delete any for tools you have dropped.
Also remove includes for services that send with their own bounce domain, since they don’t need your SPF entry.
Confirming who still sends on your behalf
Check DMARC reporting to see which sources actually send as your domain. If a vendor never appears, its include is dead weight.
3. Replace mx and a Mechanisms with ip4/ip6 Entries
Finding the real sending IP addresses
If your own servers have fixed IP addresses, swap mx and a for ip4 or ip6 entries. IP addresses don’t use lookups.
Check your mail server settings for the addresses that actually send your email, then list them directly.
Keeping static entries current
Static entries don’t update themselves. If you change servers or hosting, edit the SPF record at the same time, or legitimate mail will fail.

4. Delete ptr and Unnecessary exists Terms
Why ptr is discouraged
RFC 7208 discourages the ptr mechanism. It is slow and unreliable. Delete it and list the real sending IP addresses with ip4 or ip6 instead.
Spotting void lookups
A void lookup is a DNS query that returns nothing. RFC 7208 allows only 2 of them.
Check every exists term and each include for domains that no longer resolve. Remove any that return empty answers.
5. Consolidate Overlapping and Nested Includes
Merging vendors that share infrastructure
Some vendors nest the same provider inside their own include. Expand each include and look for duplicates.
If two includes resolve to the same ranges, keep one and delete the other.
Checking redundant redirect usage
The redirect= modifier fetches another domain’s SPF record and continues there. That costs a lookup, and the target’s own terms count too.
If the redirect points to a record you could copy, merge its terms into one record.
6. Move Marketing Senders to a Subdomain
Giving each subdomain its own SPF record
Send marketing mail from a subdomain such as news.yourdomain.com. Publish a separate SPF record there.
Each domain gets its own 10 lookups, so heavy senders stop competing with your main record.
Keeping DMARC alignment intact
Under relaxed alignment, a subdomain can still align with your organisational domain. Check your DMARC reporting to confirm the subdomain’s mail passes.
7. Use Managed SPF Flattening as a Last Resort
How automatic flattening works
Flattening swaps include statements for the IP addresses behind them, so the record needs fewer DNS lookups. Managed SPF, such as EasySPF from EasyDMARC, keeps those addresses updated for you.
Risks of stale IP ranges
If a vendor changes its ranges and your record doesn’t follow, legitimate mail fails SPF. Try the earlier steps first, and use flattening only if the record still exceeds ten lookups.
FAQ
What causes SPF PermError too many DNS lookups?
Your SPF record needs more than 10 DNS lookups, usually because of stacked include statements from many vendors.
Does SPF PermError fail DMARC?
Yes. DMARC treats it as an SPF fail. Mail can still pass if DKIM passes and aligns.
How do you reduce SPF DNS lookups?
Remove unused includes, swap mx and a for ip4 or ip6, delete ptr, split senders across subdomains, then flatten if needed.
Conclusion
An SPF PermError is fixable. Count your lookups, prune what you no longer use, and split heavy senders onto subdomains.