Email authentication
Cached DMARC policy and reporting analysis for this domain.
Record found
Policy
reject
Subdomain policy
none
Alignment
{ "dkim": "r", "spf": "r" }
Enforcement percentage
100
DMARC record
v=DMARC1; p=reject; sp=none; pct= 100; ri=86400; rua=mailto:[email protected]
Reporting
mailto:[email protected]Warnings
relaxed alignment is enabledTool switcher
Same target (2ip.io) — open the next tool without retyping.
Practical guides for common DMARC Analyzer tasks — DNS records, troubleshooting steps, and links to our free tools.
dmarc policy, p=reject, email authentication
Understand p=, sp=, pct=, and how policy changes affect spoofed mail before you move from monitoring to enforcement.
Read article →dmarc alignment, spf dkim dmarc, email deliverability
Why valid SPF or DKIM can still fail DMARC when envelope, header From, and signing domains do not align.
Read article →dmarc record tags, dmarc syntax, v=DMARC1
Decode v=DMARC1, p=, sp=, pct=, rua, ruf, fo, aspf, adkim, and common formatting mistakes in TXT records.
Read article →dmarc rua, dmarc ruf, aggregate reports
How to publish rua and ruf mailto targets, what reports contain, and why forensic reports are often disabled.
Read article →dmarc sp tag, subdomain dmarc policy, sp=reject
When sp= matters for mail.example.com, how it inherits from p=, and why separate subdomain senders need explicit alignment.
Read article →dmarc reject migration, dmarc enforcement, dmarc rollout
A staged rollout using reports, pct= sampling, and alignment fixes before full spoofing protection.
Read article →