You counted the include: mechanisms in your SPF record, you are well under 10, and a checker still says permerror. The cause is often a second limit that gets far less attention.

The two limits in RFC 7208

  1. At most 10 DNS-querying terms in total (include, a, mx, ptr, exists, and redirect). Nested includes count.
  2. At most 2 "void lookups": DNS queries that come back NXDOMAIN or with an empty answer. Past that, the evaluator should return permerror.

Most guides only cover the first one.

How you end up with void lookups

  • An include: pointing at a vendor domain that was retired or mistyped (include:spf.protecton.example instead of protection).
  • An a: or mx: mechanism for a hostname whose record was deleted during a migration.
  • A vendor's own SPF record that nests an include which no longer resolves. You did not write it, but it counts against you.

None of this shows up when you eyeball the record. The text looks fine and the failure only exists at evaluation time.

Find them

Walk the record yourself, one level at a time:

dig +short TXT yourdomain.com dig +short TXT _spf.vendor.example dig +short A some-host.yourdomain.com 

Any include: target that returns nothing, or NXDOMAIN in the full dig output, is a void lookup. Count them across the whole tree, not just your top-level record.

Fix

  • Delete includes for vendors you no longer use. Dead includes are the usual culprit.
  • Correct typos in the domain name.
  • If a vendor's nested record is broken, ask the vendor, and in the meantime replace their include with the specific IP ranges they publish, noting the date so you can revisit it.
  • Re-test from a real receiver: send to a Gmail address, open Show original and read the Received-SPF line.

Why it comes back

SPF is evaluated live against other people's DNS. A vendor can break your record without you touching it, and a record that passed last quarter can permerror today. The failure mode is silent: mail still flows, it just gets scored a little worse until someone notices a pattern.

So the real fix is to re-check the whole tree on a schedule, not once at setup.

Inspect your live SPF, DKIM & DMARC alignment free in 5 seconds: https://email-fix-pack.pages.dev/?src=devto