Volume and pass rates
How much mail was sent as your domain, and how much of it passed SPF, DKIM and DMARC alignment.
Every account now comes with a free mailbox, warmed automatically, no domain to buy. See how it works
Free with any Warmerly account
Mailbox providers send a daily DMARC report for your domain as an XML attachment nobody can read in an inbox. Point those reports at Warmerly and see who is sending as your domain, how much of it passes SPF, DKIM and DMARC, and which senders are failing. Free for up to 10 domains.
Just want to look up a record? Use the DMARC checker, no signup.
Setup
One change at your DNS host. You edit the DMARC record you already have, Warmerly does the rest.
Create a Warmerly account and open the DMARC reports page. Add up to 10 domains per workspace.
acme.comWarmerly shows your current record with our reporting address added to its rua= tag. Paste it over the existing value at your DNS host. Keep one record, not two.
v=DMARC1; p=none; rua=mailto:dmarc@acme.com,mailto:reports+<code>@dmarc.warmerly.comOnce the address is live in DNS, Warmerly sees it and marks the domain verified. Nothing to click.
Google, Microsoft, Yahoo and others send daily aggregate reports, usually starting within 24 to 48 hours. Warmerly unpacks them every 30 minutes.
In the app
How much mail was sent as your domain, and how much of it passed SPF, DKIM and DMARC alignment.
Each server that sent mail as your domain, by IP address and hostname, with its own results.
Failing and unknown senders sit at the top, so the source that would break under a stricter policy is the first thing you see.
Since 2024, Google and Yahoo require bulk senders to publish DMARC. Publishing a record is the easy part. The reports are what tell you whether the record is doing its job: which servers are sending mail as your domain, and whether each one passes.
They also answer the question that keeps most domains on p=none: would moving to p=quarantine or p=reject break legitimate mail? If a billing system, help desk or newsletter tool sends as your domain and fails alignment, the reports show it before a stricter policy sends its mail to spam. The rollout plan on the DMARC checker walks through the steps.
The catch is the format. Each provider sends its report as an XML attachment, often zipped, once a day. Read in an inbox they are close to useless, which is why the rua= address on many domains points at a mailbox nobody opens.
Before you edit DNS
A domain can have only one DMARC record. Receivers treat two as no record at all, so adding a new TXT record at _dmarc next to your old one switches DMARC off. Warmerly gives you your existing record with our address added to rua=, separated by a comma, so any reporting address you already use keeps working.
Not sure what is published today? Look it up with the DMARC checker.
DMARC passes only when SPF or DKIM passes for your From domain, so a failing source in the reports usually leads back to one of those records. Check them with the SPF checker and the DKIM checker, or all of them at once with the deliverability checker.
If you send cold email or outreach, the same account also runs email warmup and checks DNS on the domains you send from. Those are separate from DMARC monitoring; see pricing for what each plan includes.
When your DMARC record has a rua= address, mailbox providers such as Google, Microsoft and Yahoo send a daily aggregate report to it. Warmerly receives those reports for your domain, unpacks the XML and shows how much mail was sent as your domain, how much passed SPF, DKIM and DMARC alignment, and every sending source by IP address and hostname, with failing and unknown senders first.
Nothing. DMARC report monitoring is free for any Warmerly account, for up to 10 domains per workspace. What the rest of Warmerly costs is on the pricing page.
No. You keep your record and edit it. Warmerly shows your current record with our reporting address added to the rua= tag, next to any address you already have, so you change one TXT record instead of publishing a second one. A domain with two DMARC records is treated by receivers as having none.
Once the reporting address is live in DNS, Warmerly verifies the domain automatically. Providers send aggregate reports once a day, and the first ones usually arrive within 24 to 48 hours. Warmerly checks for new reports every 30 minutes.
No. Warmerly only accepts aggregate (rua) reports, never forensic (ruf) reports. Aggregate reports contain counts, sending IP addresses and SPF, DKIM and DMARC results, not message content. Report data is kept for 90 days.
Publish one first. A starting record is v=DMARC1; p=none at _dmarc.yourdomain.com; the DMARC checker explains each tag and what to publish. Then add the domain in Warmerly and add our reporting address to it.
Providers send aggregate reports as XML attachments, either plain or compressed as .gz or .zip. Warmerly reads all three, so you never have to open one.
They list every source sending as your domain and whether it passes. When every legitimate source passes with alignment, tightening the policy will not block your own mail. If a source you use is failing, fix its SPF or DKIM first. Sources you do not recognize are what the stricter policy is there to stop.
Check any domain's SPF, DKIM, DMARC, and MX records in seconds.
Validate an SPF record: one record, 10-lookup limit, and a safe ending.
Look up a DKIM key by selector and check its type, size and test mode.
Look up a DMARC policy, reporting address, pct and alignment.
Check a domain or mail server IP against Spamhaus, SURBL, URIBL and more.
Scan a subject line and email body for spam-trigger phrases.
Get a day-by-day sending ramp schedule for a new or existing mailbox.
Check text-to-HTML ratio, images, links, and tracking pixels in an email.
Add your domain, edit one DNS record, and read your DMARC reports in plain numbers instead of XML. Free for up to 10 domains.