DIAGNOSTIC PLAYBOOK
SPF include target has no SPF record
An include mechanism depends on an SPF policy at its target domain. A missing target policy can make the parent evaluation fail with a permanent error when that mechanism is reached.
HealthCheck Email editorial team · · Examples are illustrative
How to investigate
- Copy the include hostname exactly and resolve its TXT records, checking for spelling errors and an accidental domain suffix.
- Confirm the target against the service's current account instructions.
- Remove an obsolete include only after confirming that the service no longer sends for you, then rerun the complete evaluation.
What this looks like
ILLUSTRATIVE EXAMPLE
A DNS editor appends your zone to an include hostname copied incorrectly. The apparent provider domain actually points to a nonexistent name in your own zone.
A mistake to avoid
The existence of ordinary TXT records at the target is insufficient; the target needs an applicable SPF policy.
Keep the result in context
SPF evaluates the SMTP client against the envelope sender domain, or the HELO identity in the applicable case. A record lookup can identify publication problems; a message result also needs the actual sending IP and identity. Keep those inputs with your investigation.
Take the next step
Use the related check to gather evidence, then compare it with the affected message or service. Keep the result and time with your notes so a later change can be distinguished from the original problem.
Sources and further reading
The protocol references below explain the underlying behavior. Your sending or DNS provider supplies the account-specific settings for its service.