DMARC record checker

Reads the record at _dmarc on your domain and explains the policy it publishes — including the cases where a record exists but does nothing.

Gmail and Yahoo made this mandatory for bulk senders

Since February 2024, both require a DMARC record on the sending domain for bulk mail, alongside SPF and DKIM alignment and a working one-click unsubscribe. A missing record is no longer a best-practice gap; it is a delivery failure waiting for your first large send.

p=none publishes a policy that permits forgery

p=none asks receivers to report what they see and to deliver it anyway, including messages that fail both SPF and DKIM. It is the right place to start, because the reports show you which of your own senders are not aligned yet, but staying there indefinitely means a forged message addressed from your domain still lands. Move to quarantine once the reports are clean, then reject.

A record with no rua= is a policy you cannot see

The rua= tag is where aggregate reports are sent. Without it you have published an instruction and given up the only feedback that tells you whether it is working, or whether somebody is sending as you.

Other checks

  • SPF checkerReads the live SPF record, resolves every include it points at, and counts the DNS lookups. Over ten, receivers stop evaluating your SPF entirely.
  • MX lookupResolves the MX records and names the provider behind them — which decides whether an address on this domain can be checked before you send to it.
  • Deliverability auditEvery check on this site at once, for a domain you are about to send from. It takes about a second and touches nothing but DNS.