Point your rua= tag at Verifox
Publish a DMARC record with our rua= address, or keep your own and forward a copy. No agent to install and no mail server changes beyond the one DNS record you already control.
DMARC Monitoring
Collects DMARC aggregate reports, parses raw XML source-by-source, and tracks SPF and DKIM alignment for every service sending as your domain.
Book 30 minutes and we will read your current reports with you, free, no pitch.
No agent to install and no mail server changes beyond one DNS record you already control. Point rua= at Verifox and the reports start arriving.
Publish a DMARC record with our rua= address, or keep your own and forward a copy. No agent to install and no mail server changes beyond the one DNS record you already control.
Daily RUA reports from Gmail, Yahoo, and every other receiver are unzipped, parsed, and resolved into named services, with SPF and DKIM alignment tracked per source.
The dashboard names every unaligned sender so you can fix it during p=none, then flags the moment your alignment rate is stable enough to move to p=quarantine, then p=reject.
Providers already send you a daily accounting of your own mail. A monitor makes it readable.
Every major mailbox provider that receives your email sends a daily accounting of it back to you. These DMARC aggregate reports (RUA reports) are gzipped XML files delivered to whatever address sits in the rua= tag of your DMARC record. Inside each one: every IP that sent mail claiming to be your domain, how many messages it sent, and whether each batch passed SPF and DKIM alignment. The data is gold and the format is hostile. A domain of modest size collects dozens of these files a day, and nobody reads raw XML at that rate. A DMARC monitor receives the reports for you, parses them, resolves IPs into named services, and turns a week of attachments into one table: who sends as you, how much, and what passes.
Providers send you a daily accounting of your own mail in gzipped XML. Parsed, it answers four questions you cannot answer any other way.
Every RUA report is collected, unzipped, parsed, and merged into one source-by-source view with IPs resolved to named services. Almost every company finds senders it forgot — the billing system, the recruiting tool, an agency still running campaigns.

This is the part that trips everyone. A message can pass SPF outright and still fail DMARC, because the domain that passed is not the domain in the From line. We chart per-source SPF and DKIM alignment, which is the number enforcement actually depends on.

The engine reads your live alignment data and tells you whether to hold at p=none, step to quarantine, or commit to reject. Each move is gated on what your own mail is doing, not on a calendar or a vendor’s preferred timeline.

Forwarded mail breaks SPF but keeps its DKIM signature; a spoofer fails both. We separate the two patterns, so mailing lists and auto-forwards never scare you out of enforcement and a real impersonation attempt raises an alert the day it appears.

Publishing a DMARC record is the easy half. Reading the reports it generates is the half that gets you safely to enforcement.
Every report is parsed as it arrives, so a broken sender surfaces the same week.
Who sends as you, and which of them fails alignment.
When Google and Yahoo started requiring this of bulk senders.
The only policy that stops spoofing, reached without breakage.
Monitored free, no card, so you can start reading reports today.
1,000 free on signup. 2,500 with a work email. Pay as you go after.
Parsed in your account only. GDPR · CCPA.
Verifox ONE adds 15,000 credits to your account every month, and the ones you don't use roll over instead of resetting. Rather pay once? Credit packs never expire.
forever
1,000credits on signup
No card required
2,500 with a work email
Free includes
per month
15,000credits a month
$0.0053 each, $0.0044 billed yearly
Up to 25% less per credit than the 10,000 pack
Everything in Free, plus
one time
10,000credits
$0.0059 eachSAVE 34%
Everything in Free, plus
One credit verifies one address; a find costs 10, a company search 100 and an email reveal 50. All prices in USD, secure checkout via Dodo Payments.
Prices are before tax. Any VAT, GST or sales tax your country charges is added at checkout. Buying as a business? Enter your VAT or GST number there.
The addresses you submit are used only to run your verification. They are never sold, and nobody on your list hears from us.

The addresses you submit are never sold or shared.

We ask the mail server. Not one message is sent.

Full GDPR data-subject rights for everyone in the EU and UK.

California opt-out, do not sell and DSAR handling.
An investigation into the money leaking out of your list - and the nine checks that decide whether your email is read, or never arrives at all.

57 pages, free PDF, no signup
Common questions
What teams ask between publishing p=none and daring to type p=reject: report formats, alignment mechanics, and subdomain traps.
A DMARC aggregate report is a daily XML file that mailbox providers like Gmail and Yahoo send to the rua= address published in your DMARC record. It lists every IP that sent mail claiming your domain, the message counts, and the SPF and DKIM alignment result for each batch. Verifox receives these reports, parses the XML, and resolves the IPs into named services, so you read a dashboard instead of gzipped attachments.
RUA reports are aggregate: daily per-source counts of messages with pass and fail totals, no message content. RUF reports are forensic: redacted copies of individual failing messages. In practice RUA carries nearly all the value, because most large providers, Gmail included, decline to send RUF for privacy reasons. Verifox accepts both, but every policy recommendation we make is built from your aggregate data, which arrives reliably from every major receiver.
Two weeks is the practical minimum; domains with many sending services need longer. p=none blocks nothing, and its whole job is to collect aggregate reports until every legitimate source is identified and aligned. Move when your alignment rate is stable and high, not on a calendar date; the monitor flags the moment that holds. Start with a free DMARC, DKIM, and SPF check to see which policy your domain publishes today.
Since February 2024, anyone sending 5,000 or more daily messages to Gmail or Yahoo must publish a DMARC policy of at least p=none, authenticate with both SPF and DKIM, align the visible From domain, offer one-click unsubscribe, and keep spam complaints under 0.3%. Smaller senders still need SPF or DKIM. Mail that misses the bar gets throttled or rejected, which is why DMARC monitoring stopped being optional for bulk senders.
The sp= tag sets a separate DMARC policy for subdomains; without it, subdomains inherit your p= value. It matters because attackers deliberately spoof forgotten subdomains like mail.yourdomain.com or billing.yourdomain.com, where nobody is watching. Verifox tracks every subdomain that appears in your aggregate reports and warns you when sp=, or a missing record on a delegated subdomain, leaves one of them weaker than your organizational policy.
SPF alignment compares the Return-Path domain with your visible From domain; DKIM alignment compares the d= domain in the signature. A message passes DMARC when either one passes and aligns. The practical difference is forwarding: it rewrites the Return-Path and breaks SPF, while a DKIM signature survives intact. That makes aligned DKIM the backbone of a safe p=reject. If one source keeps failing, the free DKIM tester shows whether its signature validates at all.
pct= applies your policy to only a percentage of failing mail. At p=quarantine with pct=25, a quarter of failing messages go to spam and the rest are treated as p=none. It is a throttle for nervous rollouts. Treat it as a short ramp, not a destination: a long-lived pct below 100 leaves a permanent gap spoofed mail can ride through, and some receivers do not honor the tag at all.
Yes. Monitoring is free for one domain, with unlimited aggregate reports and no card required. Signing up also grants 1,000 free credits, or 2,500 with a work email, usable across the whole platform, and credits never expire.
Yes. Per-source alignment rates, parsed report history, policy state, and spoofing alerts are all exposed over REST and documented in the API reference. Webhooks push new-source and failure-spike events into Slack or your own tooling, and AI agents can read the same data through the native MCP server. Most teams wire it next to email verification so hygiene and authentication share one pipeline.