SPF void lookup
What is SPF void lookup?
A void lookup, defined in RFC 7208 section 4.6.4, is an SPF DNS query that returns an empty answer or NXDOMAIN; the RFC recommends capping these at two, separate from SPF's overall 10-lookup limit. AdminKit's SPF guide covers both limits, including the stale includes that typically trigger a void lookup.
By AdminKit team, Netbase JSC · Updated
A void lookup is a specific category of SPF evaluation outcome, defined in RFC 7208 section 4.6.4 — also on its IETF Datatracker page, and covered in M3AAWG’s guidance on managing SPF records, which warns that exhausting SPF’s DNS lookup budget “results in exhausting that limit and failing to authenticate some or all of the domain’s mail” — tracked separately from the record’s overall 10-lookup budget: a DNS query during SPF evaluation that returns either a positive answer with an empty answer set, or a Name Error (NXDOMAIN). RFC 7208 recommends — a SHOULD, not the hard MUST governing the 10-lookup cap — limiting void lookups to 2 for the entire evaluation, a distinction RFC 4408, the original SPF specification RFC 7208 obsoletes, never drew, so a record can’t force a receiving server to keep querying names that plainly don’t resolve. In practice the limit gets tripped by stale includes: a mechanism like include:oldvendor.com left in a record long after that vendor deleted its SPF record or let the domain lapse. Each one burns through the 2-void budget, and a third stale or missing name can turn the whole check into a PermError, the same outcome as exceeding the 10-lookup limit. Microsoft’s SPF setup guide for Microsoft 365 describes that other limit from the sender’s side: if the number of DNS lookups is greater than 10, the message fails SPF with a permanent error (permerror).
AdminKit groups sPF void lookup under its email authentication cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What counts as a void lookup in SPF evaluation?
A DNS query made during SPF evaluation that returns either a positive answer with an empty answer set, or a Name Error (NXDOMAIN).
How many void lookups does RFC 7208 recommend allowing?
2, tracked separately from SPF's overall 10-lookup limit.
Is the void-lookup cap a hard requirement?
No -- RFC 7208 states it as a recommendation, not the hard limit that governs the 10-lookup cap.
What commonly triggers void lookups in practice?
Stale includes left in a record after a vendor deletes its SPF record or lets its own domain lapse.
Sources
- RFC 7208 -- Sender Policy Framework (SPF), section 4.6.4
- RFC 4408 -- Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail
- IETF Datatracker -- RFC 7208 document page
- M3AAWG -- Best Practices for Managing SPF Records
- Microsoft Learn -- Set up SPF to identify valid email sources for your Microsoft 365 domain