Topic · Authentication
SPF include versus redirect
Include tests a separate SPF policy as one mechanism, while redirect delegates policy evaluation when no local mechanism matched.
How it works
Include is true only when the nested policy returns pass; redirect replaces the final evaluation with another policy's result.
What can go wrong
Treating the two as interchangeable can permit unauthorized IPs or return unexpected SPF errors.
What to check or do
Trace the result path with an SPF evaluator and document the ownership and meaning of each external record.
How to investigate SPF include versus redirect
- Signal to investigate
- A domain contains an include and a redirect that appear to grant the same provider permissions.
- Evidence to collect
- Trace the SPF evaluation order and the included record result; inspect redirect only when no prior mechanism matched.
- Common wrong conclusion
- include is conditional evaluation, whereas redirect delegates the final evaluation when no mechanism matches.
How to interpret the evidence
An include match depends on the target returning pass for the client; other results do not simply authorize the sender. Redirect replaces the terminal policy decision and should not be added casually.
What to change and how to verify it
Use include for additional authorized services and redirect only when intentionally delegating the entire record; validate the resulting DNS lookup budget.
Put this into practice
Run a focused check, then explore protection if your domain needs it.