DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that builds on SPF and DKIM. It tells receiving servers what to do when authentication fails and provides reporting so you can monitor who's sending email using your domain.
Check DMARC records for any domain using our free DNS lookup tool.
Look Up DMARC Records →
A DMARC record is a DNS TXT record published at
_dmarc.yourdomain.com that:
DMARC records are always placed at _dmarc.domain.com:
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=reject; rua=mailto:[email protected]; pct=100"
This record tells receivers to reject emails failing authentication and send aggregate reports to [email protected].
| Tag | Required | Description |
|---|---|---|
v=DMARC1 |
Yes | DMARC version (must be "DMARC1") |
p= |
Yes | Policy: none, quarantine, or reject |
rua= |
No | Aggregate report destination (mailto: URI) |
ruf= |
No | Forensic report destination (mailto: URI) |
pct= |
No | Percentage of messages to apply policy (default: 100) |
sp= |
No | Subdomain policy (defaults to p= value) |
adkim= |
No | DKIM alignment: r=relaxed (default), s=strict |
aspf= |
No | SPF alignment: r=relaxed (default), s=strict |
fo= |
No | Forensic report options (0, 1, d, s) |
ri= |
No | Aggregate report interval in seconds (default: 86400) |
The p= tag defines what to do with failing emails:
Take no action on failing emails, but send reports. Use this to start monitoring before enforcement.
v=DMARC1; p=none; rua=mailto:[email protected]
Failing emails should be treated as suspicious (typically moved to spam folder).
v=DMARC1; p=quarantine; rua=mailto:[email protected]
Failing emails should be rejected outright. Maximum protection but requires careful testing first.
v=DMARC1; p=reject; rua=mailto:[email protected]
Always start with p=none and analyze reports before moving to quarantine or reject.
Jumping straight to reject can block legitimate email from misconfigured services.
For an email to pass DMARC, it must pass either SPF or DKIM with alignment:
If either (SPF + alignment) OR (DKIM + alignment) passes, DMARC passes.
| Mode | Requirement | Example |
|---|---|---|
| Relaxed (r) | Domains must share organizational domain | mail.example.com aligns with example.com |
| Strict (s) | Domains must match exactly | example.com must match example.com |
v=DMARC1; p=none; rua=mailto:[email protected]
v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]
v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]
v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]
v=DMARC1; p=reject; adkim=s; aspf=s; rua=mailto:[email protected]
Daily XML reports showing authentication results for all emails claiming to be from your domain. These reports help you identify:
Individual reports for each failed email. These contain more detail but raise privacy concerns and many receivers don't send them. Use carefully.
sp= to control subdomains, or they inherit the main policy.To send DMARC reports to an address outside your domain, the destination domain must authorize it:
<!-- If your DMARC has: rua=mailto:[email protected] -->
<!-- analyzer.com must have: -->
example.com._report._dmarc.analyzer.com. TXT "v=DMARC1"
Common issues and solutions:
DNS Explorer — Run bulk DKIM, SPF, and DMARC lookups across thousands of domains. Built for security teams, MSPs, and IT administrators who need to audit email authentication configurations across their entire domain portfolio.
Start free DNS Explorer trial14-day full-feature trial
Use our DNS Record Finder to look up and validate DMARC records for any domain.
Look Up DMARC Records →