A practical guide to DMARC reports

Understand your reports, without becoming a DNS expert.

What aggregate reports tell you

Receivers send XML summaries of the mail they saw using your domain. Each record groups a source IP, a message count and authentication results. SPF checks the sending server; DKIM verifies a signature. DMARC passes when either one passes AND aligns with the domain in the visible From address.

Start receiving reports

Ask your DNS administrator to add rua=mailto: to your existing _dmarc TXT record, followed by a mailbox you control or a report-collection service. Do not create a second DMARC record. For an address outside your domain, the receiving domain may need an external reporting authorisation record. The address below is an example, not a working mailbox.

v=DMARC1; p=none; rua=mailto:dmarc@your-domain.example;

Read your dashboard

Start with the verdict and high-priority actions. Rates are weighted by message count, not rows. Expand a sending service to inspect its IPs and authentication domains. A passing DKIM signature is not enough if it signs with a different, unaligned domain. Forwarded mail often fails SPF while aligned DKIM keeps DMARC passing.

Move to protection, safely

01

p=none — Observe

Collect reports and inventory every legitimate sender. Fix alignment first. Monitoring does not block spoofing.

02

p=quarantine — Contain

Ask receivers to treat failing mail as suspicious. Check that legitimate mail still passes; increase pct to 100.

03

p=reject — Protect

Ask receivers to reject failing messages. Keep monitoring new senders, forwarding and policy overrides. Receivers make the final delivery decision.

Book a free 20-minute call with Joel