A passing test answers one part of the question
CheckDMARC helps you investigate authentication for a message and sending route. It does not observe the recipient’s inbox, measure your sending reputation or predict how a different mailbox provider will classify your next campaign.
If a message passes at our receiving service but goes to spam elsewhere, inspect the original headers from that destination too. Different routes, forwarding and receiver decisions can produce different evidence.
Read the receiving provider’s requirements
Google’s guidance for personal Gmail accounts includes authentication, DNS, TLS, complaint rates and message formatting. Its bulk-sender requirements also cover DMARC alignment and unsubscribe support for marketing and subscribed messages. These are broader than an authentication pass.
Treat provider thresholds and definitions as current requirements to check at the source. A general diagnostic cannot certify that your full sending program meets them.
Build a small evidence pack
Keep the affected message’s original headers, sending service, destination provider and time of delivery. Record whether the problem happens for every message or only one campaign or destination. Check your provider’s delivery logs and the recipient provider’s available reputation and complaint tools.
Use an authentication report as one part of that investigation. After any configuration change, repeat the same sending route so the comparison is useful.
Sources
Sources checked on 6 November 2026. Provider guidance can change.