SPF / DKIM / DMARC Checker
Check SPF, DKIM and DMARC alignment for a domain — the three pillars of email authentication.
About Mail Auth Check
Checks SPF, DKIM, and DMARC configuration for a domain together and evaluates whether they're properly aligned — not just present, but consistent with each other in the way DMARC alignment actually requires. A domain can have valid SPF and a valid DKIM key independently and still fail DMARC if the alignment between the From header domain and the authenticated domains doesn't match up. Complements the SPF Builder and DMARC Builder tools — build the records there, then verify the full picture actually aligns here.
DKIM selectors aren't publicly discoverable by design — if the default selector guess doesn't find a key, that doesn't mean DKIM isn't configured, only that this particular guess missed; check with the domain's mail administrator for the exact selector in use.
DKIM Selectors
default, google, mail, smtp, dkim, k1, s1, s2, selector1, selector2, pm, mimecast
Related Tools
How SPF, DKIM and DMARC fit together
- SPF checks whether the sending IP is authorized for the envelope-sender (Return-Path) domain.
- DKIM checks a signature made with a key published under the signing domain (the
d=tag). - DMARC passes when at least one of the two passes and its domain is aligned with the domain in the visible
From:header. Relaxed alignment accepts the same organizational domain (mail.example.comaligns withexample.com); strict alignment needs an exact match.
Why "SPF pass" can still mean "DMARC fail"
Newsletter platforms and help-desk tools usually send with their own bounce domain. SPF then passes, but for their domain, not yours, so it isn't aligned. Two fixes: set up a custom return-path (bounce) domain under your domain if the service offers one, or, better, have the service sign with DKIM as your domain. DKIM survives forwarding; SPF does not.
Checklist for every service that sends as you
- Add it to SPF, and watch the 10-lookup limit. The SPF builder counts lookups.
- Publish the DKIM record the service gives you, so it signs as your domain.
- Send a test message and check
Authentication-Resultswith the email header analyzer: you wantdmarc=pass. - Only then tighten the policy with the DMARC generator.
Since February 2024, Gmail and Yahoo require bulk senders to have SPF, DKIM and a DMARC record with alignment.
Finding the DKIM selector
Open a message the domain sent and look at the DKIM-Signature header: the s= tag is the selector. Common defaults are google for Google Workspace and selector1 / selector2 for Microsoft 365.