← All Tools
Tool 14 / Authentication

DMARC Report Analyzer

Open a DMARC aggregate report and see who sends email as your domain, which sources pass SPF and DKIM alignment, which ones fail, and whether your domain is ready for a stricter policy. Paste the XML or drop the .xml, .xml.gz or .zip file a receiver sent you.

Your report is read in your browser and never uploaded. Files up to 10 MB.

What this shows

Report and policy

Who sent the report, the dates it covers, and the p, sp, pct, adkim and aspf values receivers saw.

Pass rates

Total messages, the DMARC pass rate, aligned SPF and aligned DKIM, and the failing volume.

Every source

Each sending IP with its message count, disposition, SPF and DKIM results, and alignment, grouped by service.

Plain-language findings

Unidentified senders, services whose DKIM passes but does not align, and whether p=quarantine looks safe.

DMARC reports explained

The daily file nobody reads.

Every domain with a DMARC record and a rua address gets XML reports from each large mailbox provider, usually once a day. They are the only place you see every server that sends mail in your name, including the ones you forgot about and the ones that are not yours.

01

One row per source

Each record is an IP, a message count, what the receiver did with the mail, and the SPF and DKIM results.

02

Aligned is what counts

A pass only counts for DMARC when the SPF or DKIM domain matches the From domain.

03

p=none first

Start with p=none, fix every service you use, then move to quarantine and reject.

FAQ

DMARC report questions.

Fixing what a report shows? Check the SPF record with the SPF checker, the policy itself with the DMARC record analyzer, and a real message end to end with the mail tester.

What is a DMARC aggregate report?

When your DMARC record has a rua address, receivers such as Google, Microsoft and Yahoo send a daily XML file to it. It lists every IP that sent mail with your domain in the From header, how many messages each one sent, and whether SPF and DKIM passed and aligned with your domain.

Is my report uploaded anywhere?

No. The file is opened and read by JavaScript in your browser. Nothing from the report is sent to SMTPfast or anyone else, and nothing is stored after you close the page.

Why does DKIM pass but DMARC fail?

DMARC needs a pass that is aligned: the DKIM signing domain (d=) or the SPF return-path domain must match the domain in the From header. Many services sign with their own domain by default, such as sendgrid.net or amazonses.com. That signature passes, but it does not align, so DMARC fails until you set up DKIM with your own domain in that service.

When is it safe to move from p=none to p=quarantine?

When every service you send with passes DMARC, and that holds in reports from all your receivers for two to four weeks. What still fails after that should be mail you do not send: spoofing, or forwarding you accept losing. The tool says whether the report you open points that way.

Which files can I open?

The XML report itself, a gzip file (.xml.gz, as Google and Yahoo send) or a zip file (.zip, as Microsoft and others send), up to 10 MB. You can also paste the XML. A zip with several reports shows the first one.

How are sending services identified?

From the IP ranges large senders publish in their SPF records (Google, Microsoft 365, Amazon SES, SendGrid, Mailgun, Mailchimp, Mandrill, Postmark) and from the domains services sign or bounce with. No DNS or reverse DNS lookups are made, so a source we do not know shows as not identified, which does not mean it is malicious.

DMARC monitoring is coming to SMTPfast

Opening one report at a time is a start. We are building a hosted report address for your domain, a daily summary, and alerts when a new source appears or the pass rate drops. SMTPfast already sets up SPF, DKIM and DMARC for the domains you send from.

Get Started Free