How to fix: SPF include target publishes no SPF record
An include: mechanism names a domain that resolves but publishes no v=spf1 TXT record. That makes the whole SPF evaluation a permanent error, not just the one mechanism.
Why it matters
An include whose target has no SPF record produces permerror, and permerror is not a partial failure: the receiver abandons SPF evaluation for the entire message. Every other mechanism in your record, including the -all at the end, stops being applied, so the policy you published is not the policy being enforced.
This normally happens when a vendor is decommissioned and their SPF include domain is retired, or when an include hostname is mistyped and happens to resolve to a real domain with no SPF record. Because the failure is silent, the record can be broken for a long time before anyone notices, and DMARC aggregate reports are usually where it first shows up. A lookup that simply did not answer is treated as unknown here and does not produce this finding.
How to fix it
- 1Remove the include if the service is no longer used.
- 2If it is still in use, check the exact include hostname against the vendor's current documentation; these change more often than people expect.
- 3Audit the rest of the record at the same time, since a stale include usually has stale company.
Code examples
Check every include target
for d in $(dig +short TXT example.com | tr ' ' '\n' | grep -o 'include:[^ "]*' | cut -d: -f2); do
printf '%s: ' "$d"; dig +short TXT "$d" | grep -c 'v=spf1'
doneReferences
Detected automatically by VulnRadar. The check id is email-spf-include-unresolvable, stable across every scan so you can filter or diff on it.
More email checks
- LowDMARC Forensic Report URI (ruf=) Missing
- MediumDMARC Aggregate Report URI (rua=) Missing
- MediumMTA-STS (SMTP Strict Transport Security)
- LowTLS-RPT Record Missing rua= Reporting URI
- HighSPF Exceeds 10 DNS Lookup Limit
- HighSPF Redirect Loop
- LowDMARC pct= Below 100
- MediumDMARC Policy Set to Monitor-Only (p=none)
Questions
- How severe is SPF include target publishes no SPF record?
- VulnRadar rates this medium severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id email-spf-include-unresolvable, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does SPF include target publishes no SPF record map to?
- It maps to CWE-16. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.