Troubleshooting7 min read · Updated Jun 2026

Fixing SPF PermError and the 10-lookup limit

If your DMARC reports show SPF results of permerror, your record is exceeding the DNS lookup limit. Here’s what that means and how to fix it.

What the 10-lookup limit is

The SPF specification (RFC 7208) caps the number of DNS lookups a record may trigger at 10. Every include:, a, mx, ptr and redirect mechanism counts, and includes nest, so one provider’s include can cost several lookups on its own. Cross 10 and conformant receivers return permerror, which DMARC treats as an SPF failure.

The hidden cost

A single include:_spf.google.com can expand to three lookups. Add Microsoft 365, a CRM, a marketing tool and a helpdesk and you’ll quietly blow past 10, often without realising it.

How to diagnose it

  • Run your domain through the SPF surveyor to expand every include and count lookups.
  • In ClearDMARC, open a source and check its SPF result: permerror confirms you’ve hit the limit.
  • Watch for void lookups too: includes that resolve to nothing still count against you.

The manual fixes (and why they don’t last)

You can remove unused includes, drop mx/a mechanisms you don’t need, or hard-code IP ranges. All of these work briefly. Then a provider changes its sending IPs and your hand-tuned record silently breaks again.

A fix that keeps up: flattening

Flattening resolves every include down to its underlying IP ranges and serves them as one compact record, turning many lookups into one or two. ClearSPF does this automatically and keeps it current. It keeps your record under the 10-lookup limit without manual edits, and tells you in the app if it ever goes over the limit.

Was this guide helpful?