DMARC Checker
Read and validate a domain's DMARC policy: what happens to mail that fails authentication, and where reports are sent.
What this tool checks
DMARC (Domain-based Message Authentication, Reporting and Conformance, RFC 7489) ties SPF and DKIM to the address people actually see: the From domain. It lets the domain owner tell receivers what to do when a message claiming to come from the domain fails authentication, and where to send reports about it.
The checker looks up the TXT record at _dmarc.<domain>, confirms that there is exactly one record starting with v=DMARC1, parses every tag and flags missing, invalid or risky values. If the domain you enter is a subdomain without its own record, receivers fall back to the record of the organisational domain (for mail.example.com, that is example.com), so check that one too.
How DMARC decides
A message passes DMARC when at least one of these holds:
- SPF passes, and the envelope sender domain is aligned with the From domain;
- DKIM passes, and the signing domain (
d=) is aligned with the From domain.
“Aligned” means the domains match. In relaxed mode (the default) they only need to share the same organisational domain, so mail.example.com aligns with example.com. In strict mode they must be identical.
If neither passes, the receiver applies the policy you published.
How to read the result
| Tag | Example | Meaning |
|---|---|---|
v |
DMARC1 |
Version. Must be first. |
p |
reject |
Policy for the domain: none (monitor only), quarantine (treat as suspicious, usually the spam folder), reject (refuse the message). Required. |
sp |
quarantine |
Policy for subdomains. If absent, p applies. |
rua |
mailto:dmarc@example.com |
Where to send aggregate reports. Strongly recommended. |
ruf |
mailto:forensic@example.com |
Where to send failure reports for individual messages. Few receivers send them, for privacy reasons. |
adkim |
r |
DKIM alignment: r relaxed (default) or s strict. |
aspf |
r |
SPF alignment: r relaxed (default) or s strict. |
pct |
100 |
Percentage of failing mail the policy applies to. Default 100. |
fo |
1 |
Which failures trigger failure reports. |
ri |
86400 |
Requested interval between aggregate reports, in seconds. |
Findings point out, for example, a missing rua (you will not learn about problems), p=none (no protection), a pct below 100 that has been left in place, or a reporting address on another domain that has not authorised it.
Examples
Monitoring only, with reports:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Full enforcement, also for subdomains:
v=DMARC1; p=reject; sp=reject; rua=mailto:dmarc@example.com; adkim=r; aspf=r
A domain that never sends mail:
v=DMARC1; p=reject; sp=reject
From none to reject
- Publish
p=nonewith aruaaddress and collect reports for a few weeks. - Identify every service that sends mail with your domain in the From address: your mail platform, newsletters, invoicing, CRM, helpdesk.
- For each one, set up DKIM signing with your own domain and, where possible, a custom envelope domain so that SPF aligns too. Check SPF with the SPF checker and DKIM with the DKIM checker.
- Move to
p=quarantine, optionally with a lowerpctat first, and keep reading reports. - Move to
p=reject.
Since 2024, Google and Yahoo require bulk senders to publish a DMARC policy alongside SPF and DKIM. A policy of none is accepted as a minimum, but enforcement is what actually protects your domain from being impersonated.
Common problems and fixes
- Record on the wrong name. It must be at
_dmarc.example.com. Many DNS panels add the domain automatically, so enter only_dmarc. - Two DMARC records. Receivers then ignore DMARC entirely. Keep one.
- Missing semicolons or wrong tag names. Tags are separated by
;. Unknown tags are ignored, so a typo such aspolicy=rejectsilently does nothing. ruawithoutmailto:. The address must be written as a URI:mailto:dmarc@example.com.- Legitimate mail failing after enforcement. A sender is missing from SPF or not signing with your domain. The aggregate reports show its IP addresses.
Related
- Email checker: DMARC together with SPF, DKIM, MX, MTA-STS, TLS-RPT and BIMI.
- TXT record guide: where DMARC records live and how they are written.
- TXT lookup: look up
_dmarc.example.comdirectly to see the raw record.
Frequently asked questions
Is p=none enough?
It is the right place to start, because it lets you collect reports without affecting delivery. But it gives no protection against spoofing: receivers are asked to take no action on failing mail. Move to quarantine and then reject once your reports show that all legitimate mail passes.
Does DMARC need both SPF and DKIM to pass?
No. A message passes DMARC if either SPF or DKIM passes and is aligned with the From domain. DKIM is more robust, because it survives forwarding, so it is wise to have both.
What are the reports I receive?
Aggregate reports (rua) are XML files, usually sent daily by each receiver, summarising how many messages claiming to be from your domain passed or failed, and from which IP addresses. Many free and paid tools turn them into readable dashboards.
Can I send reports to an address on another domain?
Yes, but the receiving domain must authorise it with a TXT record such as example.com._report._dmarc.example.net containing v=DMARC1 (RFC 7489, section 7.1). Report services usually set this up for you.