Skip to content
DMARC Pulse

Email errors

SPF PermError: Fix Too Many DNS Lookups and Other Causes

SPF permerror means the receiver could not interpret your SPF record. Check the 10 DNS lookup limit, duplicate records and syntax, then fix the cause.

What this means

SPF permerror means the receiving server could not interpret your domain's SPF record, the DNS record that lists which servers may send its mail. Resending will not clear it, because the record itself must change. Microsoft lists too many DNS lookups and duplicate SPF records as the likely causes.

The bounce wording depends on the mail server. Microsoft documents two texts for the lookup limit: The message exceeded the hop count. and The message required too many lookups. Google warns that a provider's message can even say you have no SPF record when you do.

The receiver decides whether to reject or deliver the message. DMARC, the policy check built on SPF and DKIM, can then pass only through DKIM.

Why it happens

SPF too many DNS lookups

A single SPF check may use at most 10 terms that cause a DNS query: include, a, mx, ptr, exists and redirect. The eleventh returns permerror. ip4, ip6 and all cost nothing.

SPF too many included lookups

Terms inside included records count too, so an include pointing to a record with three more includes costs four. RFC 7208 uses neither "too many DNS lookups" nor "too many included lookups", so the wording depends on the server or tool.

Other causes of permerror

If the count is 10 or lower, look for one of these:

  • Two v=spf1 records on one name (multiple SPF records).
  • A syntax error, such as the space in include: spf.protection.outlook.com. Receivers validate the whole record first, so every message checked against it is affected.
  • An include or redirect pointing to a name with no SPF record.
  • An mx term that needs more than 10 address lookups.
  • More than two void lookups (queries that return no data), on receivers that apply the limit RFC 7208 recommends.

fail and softfail mean the record was read and did not authorize the sending server (softfail vs fail).

How to fix it

  1. Find the domain that was checked. In the Authentication-Results header, read the domain in smtp.mailfrom= beside spf=permerror. That is the envelope sender (the bounce address), which can differ from the From address. If it belongs to a vendor, ask the vendor to fix it.
  2. Count the lookups. Run the SPF checker on that domain to see each lookup. If the name has two v=spf1 records, merge them into one before deleting the other, then count again. If the total is 10 or lower, fix the matching cause above and go to the last step.
  3. Remove what no longer sends. Delete repeated includes and includes for retired services. Caution: a sender listed only in what you delete stops passing SPF, so check recent DMARC aggregate reports first.
  4. Review ptr, a and mx. RFC 7208 says ptr should not be published. Drop a or mx if those hosts send no mail, or use ip4: or ip6: if their addresses are stable. Caution: any sending server you leave out stops passing SPF.
  5. If still over 10, move a third-party sender to a subdomain. news.example.com gets its own SPF record with the vendor's include, and its own limit of 10. Caution: publish that record before moving the vendor's envelope sender to the subdomain. Remove the include from the main record only after a test shows smtp.mailfrom=news.example.com, spf=pass and dmarc=pass.
  6. Flatten only as a last resort. SPF flattening replaces an include with the vendor's IP addresses. Microsoft advises against it for include:spf.protection.outlook.com and for any service whose addresses change often. Caution: when a vendor changes an address, that mail stops passing SPF until you update the record.
  7. Publish one record. Edit the existing v=spf1 record and keep its all term. Caution: a second record to hold the overflow causes permerror by itself.

Confirm the fix

  1. Allow for DNS delay. Google says SPF fixes can take 24 to 48 hours to take effect globally.
  2. Run the checker again. You want 10 lookups or fewer and a single record.
  3. Send a test from each service to a mailbox you control. Each must show spf=pass.
  4. Check the next DMARC aggregate reports. The SPF result for that source should change from permerror to pass.

Check it now

Validate SPF and count DNS lookups

Frequently asked questions

Is SPF permerror temporary?
No. RFC 7208 defines permerror as a problem in the published records that needs a DNS change, so resending the message will not clear it. A transient DNS problem returns temperror instead, and a later retry may succeed.
Is a record with exactly 10 DNS lookups still valid?
Yes. RFC 7208 sets the limit at 10, and permerror applies only when a check exceeds it. The eleventh term that causes a lookup triggers the error. Leave some room, because your vendors can add lookups to their own records.
Do ip4 and ip6 entries count toward the limit?
No. The ip4, ip6 and all mechanisms cause no DNS query during the check, so they do not count. An include costs at least one lookup, plus every lookup inside the record it points to.
Why do some of my messages pass SPF while others show permerror?
Receivers read the record from left to right and stop at the first match. A source that matches before the limit is reached can pass. A source listed after that point gets permerror. Microsoft describes the same behavior in its SPF documentation. A checker that follows every branch can report more than 10 lookups while some mail still passes.
Does SPF permerror make DMARC fail?
SPF cannot help that message pass DMARC, because alignment requires an SPF pass. The message still passes DMARC if a DKIM signature passes and aligns with the From domain. If none does, the message fails DMARC and the receiver decides how to handle it, and it may take your DMARC policy into account.
Will every receiver reject a message with this error?
No. RFC 7208 treats this as local policy. A receiver can reject the message or deliver it, perhaps with an annotation or a log entry. If it rejects during the SMTP session, RFC 7208 says it should use reply code 550, and RFC 7372, which updates it, assigns enhanced status code 5.7.24 (SPF validation error) in place of 5.5.2. The bounce text varies by provider.

Sources consulted

RFC 7208 §2.6.7 Permerror
checked 2026-11-08
RFC 7208 §2.6.6 Temperror
checked 2026-11-08
RFC 7208 §4.6.2 Mechanisms
checked 2026-11-08
RFC 7208 §5.2 include
checked 2026-11-08
RFC 7208 §5.5 ptr
checked 2026-11-08
RFC 7208 §6.1 redirect
checked 2026-11-08
RFC 7208 §8.7 Permerror
checked 2026-11-08
RFC 8601 §2.7.2 SPF results
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.