Visits.Report
A web analytics tool that publishes your traffic stats on a public page with a daily cryptographic hash chain, so anyone can verify the numbers weren't quietly edited after the fact.
🔗 Visit Visits.Report
Description
Website traffic numbers are usually a black box: a site owner can screenshot any dashboard and claim whatever number they like, and nobody outside the company can check if it's true. Visits.Report tries to fix that by turning a site's traffic report into something closer to a sealed, dated ledger than a screenshot — similar to how a notary stamps a document so nobody can quietly change it later. Anyone can open the public report page, and because each day's numbers are chained to the previous day's with a cryptographic hash, editing old data after publishing would visibly break the chain for anyone who saved an earlier copy. It's aimed at bloggers, newsletter writers, and small SaaS builders who want to show advertisers, sponsors, or potential buyers real, checkable traffic instead of a number that could have been typed into a spreadsheet.
Technically, Visits.Report counts hits server-side using a single script tag, rather than relying on a client-side script that could be spoofed or blocked. It sets no cookies and stores no raw IP addresses: each visitor is represented by a hash built from a random daily salt, the site, the visitor's IP, and their browser string, and that salt is destroyed after two days, so IPs can't be reconstructed and visitors can't be tracked across days or sites. Domain ownership is proven via a DNS TXT record, and the full report — totals, time series, and breakdowns by source, page, country, browser, device, and campaign — is also exposed through a free, keyless JSON API, plus a separate live-visitors endpoint. Reports must be explicitly published to be public; unpublished ones return a 404.
💬 Our review
The short version: it's a clever, privacy-respecting analytics tool whose real selling point isn't the dashboard itself but the fact that you can hand someone the URL and let them verify your traffic wasn't made up.
Compared to mainstream privacy analytics like Plausible or Fathom — polished, paid, self-hostable products with years of track record — Visits.Report is a brand-new, one-person Show HN launch (3 points, 0 comments as of this writing) built around a single distinctive feature, the daily hash chain, rather than a broad analytics feature set. There's no mention of segments, funnels, goal tracking, or team accounts, and pricing beyond 'free to start' isn't published anywhere, so it's unclear how the product sustains itself long-term. The privacy design itself (no cookies, no stored IPs, salted visitor hashes) is genuinely solid and matches what Plausible/Fathom already promise, so the real differentiator is tamper-evidence — a narrow but real use case for publishers who need to prove traffic to advertisers or acquirers, not just track it for themselves. Worth trying for that specific job; too early and too thin to replace a general-purpose analytics tool.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Free tier available via signup ('Start free'); no paid plans, tiers, or pricing table are published on the site as of research date.
Pros
Publicly verifiable via a daily cryptographic hash chain, not just a self-reported number
No cookies and no stored IP addresses by design
Free, keyless JSON API for report and live-visitor data
Single script tag, no complex setup
Cons
Extremely new launch (Show HN, 3 points, 0 comments) with no track record yet
No paid tier or pricing roadmap published, so long-term sustainability is unclear
No segments, goals, funnels, or team/multi-site management mentioned
No self-hosting option — you must trust their server-side counting