A Microsoft result: the From domain has no DMARC record, but SPF or DKIM passed for a matching domain, so the message would have passed DMARC if there were one. Nothing is broken — the domain is just missing a DMARC record, which bulk senders now need.
dmarc=bestguesspass action=none header.from=example.com
How other mail servers write it
With Microsoft’s composite result
dmarc=bestguesspass action=none header.from=example.com;compauth=pass reason=109
| Result | dmarc=bestguesspass |
| Usually fixed by | The sending domain’s owner |
| Written by | Microsoft 365 and Outlook.com only |
| Goes with | compauth=pass reason=109 |
Check the DMARC record
Enter the domain from header.from: we find its DMARC record, walking up from a subdomain, and explain every tag.
What it means
Microsoft computes what DMARC would have said even when the domain publishes no record. bestguesspass means authentication and alignment are already in order; only the record is missing.
Why it happens
- No DMARC record at _dmarc under the From domain.
How to fix it
- Publish a DMARC record — v=DMARC1; p=none; with an rua= address for reports — and tighten it once the reports look clean.
See it for yourself
dig TXT _dmarc.example.com +short
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Anti-spam message headers — learn.microsoft.com
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) — rfc-editor.org