How to read a DMARC report

A DMARC aggregate report is an XML file sent to you by mailbox providers, usually once a day, listing who sent email using your domain and whether it passed SPF and DKIM.

19 November 2026

Reading a few weeks of them tells you whether it is safe to tighten your policy.

Where the reports come from

When you publish a DMARC record with a report address, for example rua=mailto:dmarc@yourdomain.com, receiving providers such as Google and Microsoft send a summary of the mail they saw claiming to be from your domain. You can generate that record with the DMARC record generator.

What is inside

Each report has three parts:

  • Report metadata: who sent the report and the time range it covers.
  • Policy published: the DMARC policy the provider found for your domain.
  • Records: one row per sending source, with the sending IP address, how many messages, and what the provider did with them.

Each record row also shows the SPF and DKIM results and whether they aligned with your From address. Raw XML is hard to read, so most people load the files into a free DMARC report viewer or use a service that collects them.

Five things to look for

  1. Your own services passing. Your mail provider, your billing tool, your support desk and your newsletter should all show as passing. If one fails, fix its SPF include or DKIM key before you tighten the policy.
  2. Sources you do not recognise. An unknown IP with a large message count may be a forgotten service of yours, or someone sending as you.
  3. Passing SPF but failing alignment. SPF can pass for a different domain than your From address. DMARC needs alignment, so this counts as a fail.
  4. DKIM missing on a service. If a tool signs with its own domain only, it will not align. Many tools let you add your own DKIM key.
  5. Volume. The message counts tell you which sources matter. Fix the biggest legitimate failures first.

When to tighten

When every legitimate source you know of passes for a few weeks, move from p=none to quarantine. Watch the reports again, then move to reject. Our data on 561 startups shows how many stop at p=none.

Related

DMARC, SPF and DKIM in the glossary, and the deliverability checklist.

Keep reading

Get back to your real work
We will find your customers

First 10 buyers free, no card

Rather talk to a person first? WhatsAppEmail