Free tool
DMARC report analyzer
Drop in the DMARC reports email providers send you. See who sends email as your domain, which services fail and how to fix them, and whether you're ready for p=reject.
Runs in your browser. Your reports are never uploaded.
Who sends email as you
You're here from my email. These are the same public checks I ran on your domain, live. If it helps, I'll walk you through the fixes for your setup in 20 minutes, or simply reply to my email with any question. Deepanshu, founder
DMARCLens reads whole folders of report emails on your machine, tracks new senders week by week, and we can take your domain to p=reject for you.
What DMARC reports are
When your domain has a DMARC record with a rua address, mailbox providers such as Gmail, Microsoft and Yahoo send you a daily aggregate report: an XML file listing every IP address that sent email claiming to be from your domain, how many messages, and whether each passed SPF and DKIM. They're the only reliable way to find every service that sends as you, from your mailbox provider to the helpdesk, newsletter, CRM and billing tools someone set up years ago. They're also nearly unreadable as raw XML.
What this analyzer tells you
- Every sender, by name: services such as Google Workspace, Microsoft 365, Amazon SES, SendGrid, Mailchimp, Zendesk, HubSpot and Salesforce are recognised from the domains that sign their mail or the ranges they send from.
- Three kinds of sender: your own services, forwarders and mailing lists (which often fail and aren't your problem), and senders that aren't authorised, usually spoofing.
- The fix for each failing service. Most failures are a service sending with its own DKIM signature instead of yours. The fix is to turn on DKIM for your domain in that service, or give it a custom bounce domain.
- A readiness verdict for moving from p=none to quarantine, or from quarantine to reject: at least two weeks of reports, 98% of your own mail passing, and no service of yours failing.
Why getting to reject matters
At p=none, DMARC only reports. Anyone can still send email that appears to come from your domain, and that's how most invoice fraud and phishing in a company's name works. At p=reject, receivers block those messages. Gmail and Yahoo require at least a DMARC record from bulk senders, and enterprise security questionnaires increasingly ask whether you enforce it.
How to get your reports
- Make sure your DMARC record has a rua address, for example rua=mailto:dmarc@yourdomain.com. Check it with our free email security check.
- Wait a few days. Reports arrive daily from each large provider, usually as .zip or .gz attachments.
- Save the attachments and drop them all here at once. Two to four weeks of reports gives the clearest picture.
If your reports go to a service such as Cloudflare's DMARC Management, it already shows a dashboard; this analyzer is for reports you receive yourself, or a second opinion on the readiness question.
FAQ
Questions
Are my reports uploaded?
No. They're unzipped and read in your browser; nothing is sent to us.
Why do mailing lists show as failing?
Lists and forwarders often change the message, which breaks SPF and sometimes DKIM. Receivers usually account for this, so it's shown separately and doesn't block moving to reject.
What does 'signed as' mean for an unknown sender?
The mail carried a valid DKIM signature for that domain, which identifies the service even when we don't recognise it by name.
How long should I wait before moving to reject?
At least two weeks of reports with every one of your services passing. Many teams spend a few weeks at quarantine first.
Can it read the report emails themselves?
This page reads the attachments. DMARCLens, our command-line tool, also reads .eml and .mbox exports of the emails.
Is there a limit?
Files up to 50 MB each, as many as your browser can handle. For years of reports, use DMARCLens.