Verify visits.report

How to recompute it

Each day's digest is the SHA-256 of a single line joining the site id, the date, the three counters and the previous day's digest with pipe characters. Nothing else goes in. Take any row below and run:

What this proves

That the published figures for a past day have not been edited since that day was sealed. Because each digest folds in the one before it, changing a single historical number changes every digest after it — so anybody who wrote down an older digest can show the mismatch. Days are sealed once complete and are never re-sealed.

What this does not prove

That the counters were honest at the moment of sealing. We run the collector, so in principle we could seal a wrong number in the first place. No self-hosted analytics tool can rule that out, and any product claiming otherwise is overselling. What the chain removes is quiet revisionism after the fact — the thing that actually happens when somebody wants their traffic to look better later.

It also says nothing about traffic quality. A visitor is a browser that loaded the page, not a customer, and we do not filter anything beyond obvious bots by user-agent.

Domain ownership

Verified on 2026-08-25 — the owner published a DNS TXT record on the domain itself, which nobody else could do.