SealedRoute
Verify a packet's signed snapshot
Upload a SealedRoute audit packet and this page extracts its embedded signed snapshot, verifies SealedRoute's Ed25519 signature, and — if valid — displays SealedRoute's own authoritative record rebuilt from the signed snapshot. The uploaded file's own layout is never trusted or shown. Everything runs in your browser; nothing is uploaded and no account is required.
Public packet checker — no login required. This page checks a packet file or snapshot you already have, or the signed demonstration sample below. Verification runs entirely in your browser: nothing is uploaded, and it never accesses customer accounts or data.
Try it now — check our sample packet
No packet in hand? Load a signed sample and verify it right here. It is a demonstration built from synthetic data — no real courier, driver, patient or customer appears in it — but the signature is real, and it is checked the same way a customer's packet is.
Option 1 — Upload a packet file
Select a downloaded SealedRoute packet (.html) or a snapshot (.json).
Option 2 — Paste a snapshot + expected hash
What a result means
- SIGNATURE VALID - SealedRoute's Ed25519 signature is valid and so the portal displays SealedRoute's own authoritative record, rebuilt from the signed snapshot. The uploaded file's own HTML, CSS, and scripts are never trusted, rendered, or shown.
- HASH-ONLY - the record is internally consistent with its hash, but a valid SealedRoute signature was not confirmed (none embedded, or signature checking unavailable here). Signer not confirmed — not shown as verified.
- INVALID - the signature or hash did not validate — the packet is unsigned by SealedRoute, altered, or corrupted. Do not rely on it.
A VERIFIED result proves SealedRoute signed this snapshot and the portal is showing SealedRoute's own record for it. It does not certify anything about the uploaded file's own layout, nor that the underlying real-world events occurred.