Dev.to Security 🔐 Cybersecurity 👁 0 📖 2 min read

Verifiable uptime claims: stop trusting screenshots, start re-fetching receipts

Every status page is a promise. Every screenshot of a green dashboard is a promise with a timestamp you can't check. If you've ever had to prove to a client, a customer, or an auditor that your endpoint was actually reac

Every status page is a promise. Every screenshot of a green dashboard is a promise with a timestamp you can't check. If you've ever had to prove to a client, a customer, or an auditor that your endpoint was actually reachable at 03:14 last Tuesday, you already know the problem: the proof lives on the same machine that makes the claim.

The cheap version of the idea

A reachability receipt is just this:

  1. Fetch a URL, record status code, latency, TLS expiry, and a timestamp.
  2. Hash that record (SHA-256) and sign it.
  3. Store nothing about the requester — no accounts, no cookies, no stored payloads.
  4. Publish the receipt so anyone can re-fetch the same URL and compare.

The important property is step 4: a receipt you can't independently re-derive is marketing, not evidence. The verifier doesn't have to trust the issuer — it just repeats the fetch and checks the hash.

What a re-verifiable receipt looks like

{
  "url": "https://example.com/health",
  "checked_at": "2026-11-15T19:27:17Z",
  "status": 200,
  "latency_ms": 184,
  "tls_expires": "2027-02-03T00:00:00Z",
  "sha256": "9f2c..."
}

Anything that changes the bytes changes the hash — which means a tampered receipt fails the check loudly instead of quietly.

Three places this actually helps

  • Client handoffs. Instead of "we monitor it, trust us", hand over a receipt the client can re-fetch themselves.
  • Vendor due diligence. Ask for a receipt, not a PDF. Re-fetch it during the call.
  • Embedded badges. A status badge that carries its own verification URL is worth more than a static green dot, because the reader can click through and re-derive it.

The tool

I've been building a small free tool around exactly this shape: no signup, no stored data, signed SHA-256 receipts you can re-verify by re-fetching the URL yourself. There's a free badge and embed helper, and a $9 Pro tier if you need more than occasional checks — the point isn't the price, it's that the free path is genuinely verifiable end to end.

If you want to poke at it, try the /try endpoint with a URL you own and see whether the receipt you get back survives your own re-fetch. If it doesn't, that's a bug worth telling me about — that feedback loop is the only reason the thing is useful.

Takeaway

Before you add another dashboard, ask what a skeptic could independently check. If the answer is "nothing", you have a poster, not proof.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.