Aggregate Report Reader
The daily XML from Google, Microsoft and the rest, turned into something you can act on — grouped by sender, with the reason each one failed.
Nothing is stored. The file is parsed in memory and discarded when the page finishes rendering.
Reading a report
Alignment is not authentication
A row can show DKIM pass in the auth results and fail in the policy evaluation. That means the signature verified — just not for your domain. The fix is at the sending service, not in your DNS.
Disposition can lie
A failing message shown as none may have been overridden by the receiver — forwarding, a mailing list, a local allowlist. We show the override reason next to the count, because reading one without the other reverses the conclusion.
Group by source, not by row
One misconfigured service produces hundreds of rows. Rolled up by IP, it becomes one line and one action.
Nothing is kept
The file is decompressed, parsed and dropped within the request. No database, no queue, no copy. If you want history, that is a different tool.