What an email check can tell you A fictional report for atelier.example. It compares an office mailbox and a website form before and after a proposed correction. These are separate illustrative observations, not messages sent by this page or a live scan. Fictional data, not a client case. No DNS lookup, configuration change or email send. No copy-and-paste DNS records. Actual headers, delivery and provider behaviour must be tested on authorised accounts. Office mailbox Visible sender: devis@atelier.example SPF passes and matches: Yes DKIM passes and matches: Yes DMARC passes: Yes Inbox placement: Not tested SPF and DKIM both pass and match the visible sender domain. DMARC passes. That establishes authentication in this example, not whether a customer opened the message or found it in the inbox. Website form: before Visible sender: site@atelier.example SPF passes and matches: No DKIM passes and matches: No DMARC passes: No Inbox placement: Not tested The provider is authorised for its own sending domain, so SPF passes, but that domain does not match the visible sender. DKIM fails too. DMARC therefore fails: an SPF pass on its own is not enough here. Website form: after Visible sender: site@atelier.example SPF passes and matches: No DKIM passes and matches: Yes DMARC passes: Yes Inbox placement: Not tested A proposed correction gives the form a valid DKIM signature matching the sender domain. DMARC can pass through that signature even while SPF fails. The remaining SPF issue still needs investigation; passing DMARC is not a clean bill of health.