The SPF check did not say yes or no. Either the record ends in ?all (or has no all at all), so it explicitly asserts nothing — or, in Gmail’s “best guess record” wording, the domain has no valid SPF record. Receivers treat it like having no SPF.
spf=neutral (google.com: 192.0.2.1 is neither permitted nor denied by best guess record for domain of alice@example.com) smtp.mailfrom=alice@example.com
How other mail servers write it
Microsoft’s Received-SPF
Received-SPF: Neutral (protection.outlook.com: 192.0.2.1 is neither permitted nor denied by domain of example.com)
Exim (common on cPanel)
spf=neutral (best guess record for domain) smtp.mailfrom=example.com
| Result | spf=neutral |
| Usually fixed by | The sending domain’s owner |
| Published as | ?all, or a record with no all term |
| Treated like | No SPF at all (RFC 7208 §8.2) |
Check the sender’s SPF record
Enter the domain from smtp.mailfrom (the envelope sender): we read its SPF record, follow every include and count the lookups.
What it means
A neutral result is the domain declining to say whether the server may send — which RFC 7208 says must be treated exactly like no SPF record. Google shows the “best guess record” wording when it found no usable SPF record for the domain: SPF is not set up, or not set up correctly.
Why it happens
- The record ends in ?all.
- The record has no all term, which means an implicit ?all.
- There is no valid SPF record, and the receiver fell back to a guess.
How to fix it
- Publish one SPF record listing every service that sends as the domain, ending in ~all or -all.
- Check it with the tool above.
See it for yourself
dig TXT example.com +short
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 7208 — rfc-editor.org
- Troubleshoot SPF issues — knowledge.workspace.google.com
- Anti-spam message headers — learn.microsoft.com