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.
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
- 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.
- 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.
- 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.
- 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.
- 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
- Google and Yahoo's sender rules, in plain wordsSince February 2024 Gmail and Yahoo require authentication, easy unsubscribing and low spam complaints from bulk senders. What each rule means if you send cold email.
- How many cold emails can you send per inbox per day?A common safe range is about 15 to 30 cold emails per mailbox per day after a gradual warm-up. Why there is no fixed limit and how to find yours.
- How to find your first 10 B2B customersPick one narrow type of buyer, find the companies that have a reason to need you right now, and write to each one personally. The steps in order.
- Only two in three fast-growing startups enforce DMARCWe checked the public email records of 561 hiring B2B startups. 94.3% publish DMARC, but only 65.6% use a policy that acts on failures. What the gap looks like.
