SPF void lookup limit exceeded — dead includes in your record
A void lookup is a DNS query made during SPF evaluation that returns NXDOMAIN or no records. RFC 7208 §4.6.4 allows at most two before evaluation fails with PermError.
Void lookups almost always mean an include: points at a vendor that has shut down or changed their SPF hostname. The record looks fine to a human and is broken to a receiver.
How to fix it
- 1Identify which include: or redirect= targets return no SPF record.
- 2Remove every one belonging to a service you no longer use.
- 3For services you still use, get the current include hostname from their documentation — vendors do rename these.
- 4Re-scan and confirm the void count is back to zero.
Check whether your domain has this problem
Free, no signup, about two seconds. You get the exact record to paste.
Related guides
- DKIM record with empty p= — a revoked key still in use
- SPF include points at a domain with no SPF record — a silent PermError
- DMARC record syntax errors that make receivers skip your policy
- DMARC external destination not authorized — why you receive no reports
- Two DMARC records at _dmarc — why your policy is being ignored