Why a missing include: or redirect= target, or more than two void DNS lookups, makes SPF return permerror, how to find the broken term, and how to fix typo includes, retired vendors and empty exists lookups.
Home › Guides › SPF include not found / void lookups
Last updated 17 November 2026
Two different RFC 7208 rules produce an SPF permerror when DNS comes back empty. They are easy to confuse.
include: or redirect= target is immediately a permerror. Section 5.2's table says a recursive check_host() result of none causes the include mechanism to return permerror (and that fails the whole evaluation). Section 6.1 says that if a redirect= target has no SPF record, the result is permerror rather than none. One typo, one retired vendor include, or one redirect to a name you never published is enough.Run the domain (or a draft record) through the SPF Record Checker. It expands every include and redirect, flags void lookups, and reports when the void count goes over two. This is a different failure from going over 10 DNS lookups, which is also a permerror.
include:vendor.example does not paste that vendor's mechanisms into your record. It runs a full SPF evaluation of vendor.example and, if that evaluation returns pass, your include matches. RFC 7208 section 5.2 is explicit about the other outcomes:
| Recursive result | What the include does |
|---|---|
pass | Match (your include succeeds). |
fail, softfail, neutral | Do not match; evaluation continues with the next term. |
temperror | The whole evaluation returns temperror. |
permerror | The whole evaluation returns permerror. |
none (no SPF record at the target) | The whole evaluation returns permerror. |
So a name that exists in DNS but has no v=spf1 TXT record, or a name that does not exist at all, is not a harmless miss. Receivers stop and return permerror, and DMARC treats that as an SPF fail. Common ways to get there:
include:spf.protection.outl0ok.com, a missing hyphen, or an old hostname a vendor retired.v=spf1 record.redirect=_spf.example.com you published before creating the record at _spf.example.com.The TXT lookup for your own top-level record is a different case: if that lookup finds no v=spf1 record, RFC 7208 section 4.5 returns none, not permerror. Two v=spf1 records at the same name are permerror.
RFC 7208 section 4.6.4 (which points at section 11.1) defines void lookups as terms whose DNS queries return:
The terms that cause DNS queries, and can therefore consume the void budget, are include, a, mx, ptr, exists and redirect. ip4, ip6 and all do not. Nested includes count. A third void lookup should produce permerror. The RFC says implementations may make the limit configurable, with a recommended default of two, so you should treat two as the budget you design for.
Void lookups often come from:
include: or a: / mx: names that no longer exist (these may already have permerror'd via the include-none rule if they were includes).exists: mechanisms, especially with macros such as exists:%{i}._spf.example, which query a different name for every sending IP. Two misses and the next one can permerror the message. RFC 7208 warns that sender-specific macros in more than two terms can exhaust the void limit easily.mx: or a: of a name with no records.If the include target exists and returns other TXT records but no SPF record, that TXT query may not be void (it did return answers), but the include still permerrors because the recursive result is none.
v=spf1 record for an include or redirect target. NXDOMAIN, or TXT records that do not start with v=spf1, is the problem.spf=permerror for a domain you own, open them in the DMARC Report Analyzer and fix the record before you tighten policy.spf=permerror in Authentication-Results. That tells you the evaluation failed; the checker tells you why.redirect=, verify it, then add the redirect on the domains that should share it.ip4 / ip6 for a handful of your own servers instead of a, mx or exists of names that might disappear. Those mechanisms are free and cannot be void.exists and macros. If you must use them, keep to names that always have a record for both authorized and unauthorized clients, so evaluation does not spend the void budget on ordinary mail.Do not flatten a vendor include just to hide a missing target. If the vendor's record is gone, flattening an old snapshot will authorize the wrong hosts. Remove or replace the include.
v=spf1 record on the DNS Propagation Checker.spf=pass in the Email Header Analyzer.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Expand the live or draft record with the SPF Record Checker, rebuild it with the SPF Record Builder, and confirm publication with DNS Lookup and the DNS Propagation Checker. See the effect on a message in the Email Header Analyzer and on the domain in the Email Deliverability Checker. Related guides: SPF too many DNS lookups, SPF for Microsoft 365, Microsoft 365 inbound SPF softfail or permerror and DMARC p=none to p=reject rollout.
Yes. RFC 7208 section 5.2 says that when the recursive check of an include target returns none (no SPF record), the include mechanism returns permerror, and that ends evaluation of your record. The same is true of a redirect= target with no SPF record (section 6.1). You do not have to wait for three empty lookups.
A DNS query made for an SPF term that returns NXDOMAIN, or a successful response with no answers. RFC 7208 section 4.6.4 says implementations should allow at most two such lookups in the whole evaluation, and that a third is a permerror. include, a, mx, ptr, exists and redirect can produce them; ip4, ip6 and all cannot.
No. The ten-lookup cap counts every include, a, mx, ptr, exists and redirect, whether or not they return data. The void limit counts only the ones that return no data, and the budget is two. Either condition is a permerror. A record can fail one, the other, or both.
If you removed the vendor's hosts but left include:their-domain in your record, and they later deleted their SPF record or the hostname, receivers now get none on that include and return permerror for every message from your domain. Delete the unused include as soon as the vendor stops sending.
Yes. Paste the new record into the optional box on the SPF Record Checker. It will expand includes, count lookups and flag void lookups without touching DNS at your domain. When the draft is clean, publish one TXT record and confirm it with the DNS Propagation Checker.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.