DMARC checker

Check a domain's DMARC policy, report address and syntax.

What is DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance, RFC 7489) ties SPF and DKIM to the domain in the visible From address. A message passes DMARC when SPF or DKIM passes for a domain that matches the From domain.

The DMARC record tells receivers what to do with mail that fails (the policy, p=) and where to send daily aggregate reports (rua=).

Why it matters

Without DMARC, anyone can put your domain in the From address and receivers have no instruction to reject it. Phishing with an exact copy of your domain depends on that gap.

The reports are the other half. They list every server that sent mail as your domain and whether it passed, so you can find forgotten services before you tighten the policy. p=none with reports is the safe start; p=quarantine or p=reject is the goal.

What a correct record looks like

Publish one TXT record at _dmarc.example.com. It must start with v=DMARC1, set a policy and name a report address.

DNS record

_dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Move from p=none to p=quarantine and then p=reject once the reports show that all legitimate mail passes. If reports go to another domain, that domain must publish an authorization record.

Common problems

p=none
Mail that fails DMARC is still delivered. Use the reports to fix your senders, then move to p=quarantine.
No rua address
Nobody receives the aggregate reports, so failures go unnoticed. Add rua=mailto: with an address that is read.
More than one record
Receivers ignore DMARC completely when two records exist. Keep one.
Invalid policy
p must be none, quarantine or reject, and v=DMARC1 must come first. Any other value makes the record invalid.
Reports to another domain without authorization
If rua points to another domain, that domain must publish example.com._report._dmarc.<its domain>. Otherwise reports are not sent.