DMARC record checker

Looks up the exact domain first, then correctly walks to the organizational domain (via the real Public Suffix List) if nothing is published directly.

1 · Input


What DMARC adds on top of SPF and DKIM

SPF and DKIM each authenticate email in their own way, but neither one, on its own, tells a receiving server what to DO with a message that fails, or requires the failure to be about the domain the recipient actually sees in their inbox. DMARC closes both gaps: it sets a policy for failures, and requires the authenticated domain to align with the visible From address.

The policy tag (p=)

  • none - take no action, just report. A common (and reasonable) starting point while a domain is confirming DMARC will not misfire on its own legitimate mail.
  • quarantine - treat a failure as suspicious, typically routed to spam.
  • reject - refuse the message outright. The strongest setting, appropriate once a domain is confident every legitimate source of its mail is properly authenticated.

Why the rua= address matters

Without an aggregate-report address, failures are evaluated by receivers but never reported back to the domain owner - a policy running with no visibility into what it is actually catching, or breaking.

Related tools

See SPF and DKIM, the two mechanisms DMARC's alignment check builds on.

Rate this tool

Was this tool useful? Your feedback helps us improve it.

No ratings yet — be the first to rate this tool.
Your rating (required)
0 / 2000

Please do not include passwords, payment details or other sensitive information.

Your feedback is sent privately to the A2Z.Tools team and will not be posted publicly.