XML and CSV parsing
Reads RUA feedback/record XML or header-led CSV rows. Bad rows are reported with their row number and skipped; DOCTYPE and ENTITY are rejected.
Paste DMARC aggregate report XML or CSV rows and get a ranked list of failing mail sources, a ramp-step verdict and a before/after diff.
Decide which failing senders to fix first and whether your domain may move to the next DMARC policy step, without reading RUA rows by hand.
An illustration of the workflow, not a measurement. Run your own input to see actual findings.
xml for RUA XML, csv for header-led CSV rows.
csv
Reads RUA feedback/record XML or header-led CSV rows. Bad rows are reported with their row number and skipped; DOCTYPE and ENTITY are rejected.
Groups by source IP, header_from and DKIM/SPF domain, with integer basis-point shares that never round up past the total.
Each source is split into both, spf-only, dkim-only and neither message counts, with a fix type for the dominant failing class.
Failing sources ordered by failing messages, with share and cumulative share, so the biggest gaps are fixed first.
Compares aligned basis points with the fixed 95, 97, 98, 99 and 99.5 percent thresholds and states the gap and messages needed.
Compare two batches after a DNS change. Download lossless JSON and spreadsheet-safe CSV.
Check whether a domain at p=none can move to quarantine 10 after a DNS change.
Hand a client a ranked list of senders that still fail SPF and DKIM alignment.
Check the field guidance and usage limits before you run the tool.
Use the workspace to submit your input.
Read the output and return to the workspace for your next task.
No. It only analyses the text you paste; no DNS or outbound requests are made.
Up to 524288 bytes of JSON body and 5000 records per batch.