SPF has both redirect= and an all mechanism
What this check looks for
Your record contains a redirect to another domain's policy and also its own closing rule. The closing rule wins and the redirect is never used, which is almost never what was intended.
Why it matters
The policy you believe is in force — the one at the redirect target — is being ignored entirely.
When the check passes, your report says: “The record uses redirect= or an all mechanism, not both”.
What it costs your score
When this check fails it removes 6 points from your Email authentication score, before the status, confidence and repeat multipliers are applied. Email authentication carries a weight of 15 in the overall score.
It shares the email-auth.spf family ceiling of 35 points: however many findings that family produces, together they cannot remove more than that from Email authentication. One underlying problem showing up in several places is still one problem.
- Severity
- medium
- Default confidence
- confirmed
- Status when triggered
- warn
- Deduction
- 6 points
- Family cap
- email-auth.spf · 35
- Category
- Email authentication
- Module
- Email spf
- Fix owned by
- dns host
- In the ruleset since
- 2026.09
How to fix it
Decide which one you want and remove the other.
As written, the redirect is dead configuration and the policy in force may not be the one you think.
To use the other domain's policy, delete the
allmechanism and keepredirect=‹redirect domain›.To keep your own policy, delete the
redirect=modifier and keepall.
How to confirm it worked
dig +short TXT ‹domain› — expect either redirect= or all, not both
A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.
Technical detail
The record for ‹domain› contains both redirect=‹redirect domain› and an all mechanism. RFC 7208 §6.1 states that redirect is only used when the record contains no all mechanism; where both appear, redirect is ignored.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other email spf checks
- SPF authorises the whole internet through an address range
- SPF record lists the same sender twice
- SPF include chain contains a loop
- SPF include target has no SPF record
- SPF is close to the 10 DNS lookup limit
- More than one SPF record published
- SPF record has no all mechanism
- No SPF record published
- SPF authorises a very large block of addresses
- SPF ends in +all — anyone may send as your domain
- SPF uses the deprecated ptr mechanism
- SPF ends in ?all (neutral)