Every SPF check ends in one of seven results, recorded in the message headers (Received-SPF, Authentication-Results). Only pass authorises the server; only an aligned pass counts for DMARC.
| Syntax | pass | fail | softfail | neutral | none | temperror | permerror |
| Where you see it | Received-SPF and Authentication-Results headers |
| What DMARC needs | pass, for a domain aligned with From |
| Defined in | RFC 7208 §2.6 |
What it does
pass: the server is authorised. fail: the record says it is not (-all). softfail: probably not (~all). neutral: the record makes no statement (?all, or no all).
none: the domain publishes no SPF record, or the domain could not be found. temperror: a DNS problem, try again later. permerror: the record is broken — two records, a syntax error, more than ten lookups or more than two void lookups.
SPF checks the bounce (envelope) address, not the From address people see. That is why a message can pass SPF and still fail DMARC: the domain that passed was the sending service’s, not yours.
Examples
Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning bounce@example.com does not designate 203.0.113.5 as permitted sender) smtp.mailfrom=bounce@example.com
A softfail recorded by Gmail: the server was not in example.com’s record, which ends in ~all.
See what your own SPF record says
Every term of your published record, read and explained — including this one.
Common mistakes
- Reading softfail as a pass: it is a failure the domain asked receivers to treat gently.
- Ignoring permerror, which fails every message.
What we recommend
Aim for pass on every legitimate message, and treat permerror as urgent.
Sources
Checked on 25 September 2026 against these official sources: