Lorixen.
EN

Reading Your First DMARC Report Without Panicking

Short answer: A DMARC aggregate report is an XML file that a mail provider sends to the address in your DMARC record, usually once a day. Each row lists a sending server, how many messages it sent for your domain, and whether those messages passed SPF and DKIM in a way that matches your domain. Rows that fail usually belong to a tool you forgot, not to an attacker. Sort the failures by sender, fix the legitimate ones, and only then move your policy from none to quarantine to reject, one step at a time.

What the file contains

The report is written in XML, which is hard to read by eye. Most owners use a free report viewer or a converter, but the fields are the same in every tool. The useful parts of each record are:

  • Source IP: the address of the server that sent the messages.
  • Count: how many messages that server sent during the reporting period.
  • Disposition: what your policy told the receiver to do, such as none, quarantine or reject.
  • SPF result and DKIM result: whether each check passed.
  • Alignment: whether the domain that passed SPF or DKIM matches the domain in the visible From address.

A message passes DMARC when at least one of SPF or DKIM passes and that check is aligned with your From domain. Keep that rule in mind, because a report can show a pass for SPF and still fail DMARC if the domains do not match.

A sample row

Here is an invented example, with a small invoicing tool that sends on behalf of a bakery:

Source Messages SPF DKIM Aligned Verdict
Your mail server 412 Pass Pass Yes Good
Invoicing tool (example) 96 Fail Pass Yes Fine, DMARC passes
Old website contact script 14 Fail Fail No Fix it
Unknown server, one region 3 Fail Fail No Investigate

The invoicing row looks alarming, but DMARC passes because DKIM is aligned. The contact script row is a real problem: a form that sends mail from your domain without signing it. The unknown row needs a lookup of the IP address before you decide.

Find the senders you forgot

Most legitimate failures come from services that send mail for your domain and that someone set up years ago. Make a list of what you use: your email provider, the website host, the online store, the newsletter tool, the helpdesk, the accounting package, the booking system and any printer or scanner that emails documents. Match each sending source against the report. Anything that appears in the report but not on your list needs an owner before you change the policy.

A staged plan to enforcement

Do not jump straight to reject. Move through three stages, and stay on each one long enough to see a full cycle of reports, which usually means at least two weeks for a small company:

  1. Monitor. Publish a DMARC record with p=none and an address to receive reports in the rua tag. Nothing is blocked, so this stage is safe.
  2. Quarantine. When every legitimate sender passes, change to p=quarantine. Failing messages may land in spam. You can use the pct tag to apply it to a portion of mail first.
  3. Reject. Once quarantine has run cleanly for a few weeks, move to p=reject, which asks receivers to refuse failing messages outright.

Each step changes only one tag. Write down the date of every change, so you can roll back if a supplier complains.

Signs that a change is safe

Before you move a stage, check that failing mail volume has dropped to a level you can explain, that every row with a large count has an owner, and that nobody on the team reports missing invoices or delayed quotes. A report from the last seven days is more useful than one from a month ago, because you will have fixed some senders since.

Who should read the reports

The reports are most useful when one person owns them. In a small business that is often the office manager or the person who manages the domain registration, with the IT helper checking unusual rows. Agree a simple routine: a glance once a week at the totals, a closer look at any sender with more than a few dozen failures, and a note in a shared document for each change to the DNS records.

Do not send the raw reports to a group inbox that nobody reads. Reports that arrive every day and pile up unread are the same as no reports. If the volume is too much for one person, ask your report viewer to send a weekly summary instead of the full files.

When the report looks wrong

Sometimes a row shows a large volume from a server you do not recognise. Look up the IP address with a reverse lookup tool. If it belongs to a major provider, it may be a forwarding service, a shared host or a mailing list. If it belongs to nobody you know, treat it as suspicious and keep the policy at monitor or quarantine until you understand it.

Keep a log of every change

Write each change to the DMARC record in a shared log, with the date, the tag changed, the reason and the person who made it. When a report shows a spike of failures weeks later, the log tells you whether your own change caused it or whether a supplier changed its sending servers. Save the previous record text as well, so a rollback is a copy and a paste rather than a search through old emails.

FAQ

Is a DMARC report an email I need to read?

Not individually. The reports arrive in machine-readable form, and you only need a summary. Most owners use a viewer that groups results by sender.

Why do I see reports from providers I have never heard of?

Large mailbox providers send reports for every domain whose mail they see, including yours. The provider name in the report tells you who sent the report, not who sent the message.

Can a forwarded email fail DMARC?

Yes. Forwarding can break SPF, and a list that changes the subject or footer can break DKIM. This is a known limit of DMARC, and it is one reason to check the sources before enforcement.

Do I need a paid tool to read the reports?

No. Free viewers can summarise the XML, and a spreadsheet works for a small domain. Choose the simplest method you will keep using.

If the list of senders is long or the reports keep failing after you have fixed them, tell us about your mail setup and our studio will map the senders and help you move to enforcement safely.

Sources

WhatsAppBook a call