parse-dmarc
DMARC aggregate report parser with a built-in dashboard. One Go binary, IMAP in, SQLite, Prometheus metrics, MCP server. Apache-2.0.
Runssource: GitHubhomepageGoApache-2.0commit cb4a8b8ca6b5
Go, Apache-2.0 licensed. The project labels itself: dashboard, dkim, dmarc, dmarc analyzer, dmarc reports, docker, email authentication and email security.
parse-dmarc runs. An Argusic agent installed it in 5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The binary builds and runs, the dashboard serves on port 9092, the API endpoints return correct JSON and HTTP 200, and all 28 unit tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go not found in container1 minute
- bun not found in container1 minute
- Node.js v18 too old (requires >=22)1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl to http://127.0.0.1:9092/ returned 200 with dashboard HTML; http://127.0.0.1:9092/api/statistics returned 200 with valid JSON; http://127.0.0.1:9092/metrics returned 200 with all Prometheus metrics; go test -v ./... passed 28 subtests
- Model tokens used
- 205,308
- Exact commit tested
- cb4a8b8ca6b5
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `GET /metrics` → HTTP 200 with all Prometheus metrics including `parse_dmarc_*` gauges
**Errors encountered**: (1) No Go installed → downloaded Go 1.25.4 tarball; (2) No bun installed → …
tokens used
205,308
Here's the final summary:
**Install & Build**: Successfully installed Go 1.25.4, bun 1.4.4, and Node.js v22. `bun install` re…
**Tests**: `go test -v ./...` passed all 28 subtests across 4 packages (imap, parser, storage).
**Launch Verification**: The server started on `127.0.0.1:9092` and all endpoints responded:
- `GET /` → HTTP 200 (full Vue dashboard HTML)
- `GET /api/statistics` → HTTP 200 + valid JSON `{"total_reports":0,"total_messages":0,...}`
- `GET /metrics` → HTTP 200 with all Prometheus metrics including `parse_dmarc_*` gauges
**Errors encountered**: (1) No Go installed → downloaded Go 1.25.4 tarball; (2) No bun installed → …Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 5 minutes, faster than the median of the 7 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 dashboard projects Argusic has installed and timed, parse-dmarc was the 3rd fastest to reach a running state, and 6 of 8 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
dashboarddkimdmarcdmarc-analyzerdmarc-reportsdockeremail-authenticationemail-securitygolangimapmcp-serverparsedmarcprometheusrfc7489self-hostedsingle-binaryspfsqlitevue3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/parse-dmarc)Questions
- Does parse-dmarc run?
- Yes. parse-dmarc runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test parse-dmarc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb4a8b8ca6b5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test parse-dmarc?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does parse-dmarc take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does parse-dmarc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing parse-dmarc?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does parse-dmarc compare with the alternatives?
- Of the 8 dashboard projects Argusic has installed and timed, parse-dmarc was the 3rd fastest to reach a running state, and 6 of 8 reached one at all.
- Where is the evidence for parse-dmarc?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.