Why verification exists
A tracking page is just words on a screen — anyone can fake one. TrackJet seals every tracked history into a SHA-256 hash chain at ingest (spec: tjvt2), so the claim "this history was never rewritten" becomes checkable instead of trusted.
Verify a timeline
Open /verify and paste the shipment's UUID (it is on the result page). The verdict tells you:
- valid — the events in the database are byte-identical to what was sealed, link by link;
- broken at N — something was altered after sealing, and the position of the break is the evidence.
Shipment passports
A passport is a signed, self-contained export of one shipment: the full timeline plus the cryptographic material to check it. Export it from the shipment card and hand it to anyone — a customer, an insurer, an auditor. They can verify it without a TrackJet account, and even offline.
Public anchoring
Sealed histories also anchor into a public, append-only Merkle transparency log (spec: tjmt1). The practical effect: if anyone — including TrackJet — silently rewrote a past timeline, the old proof would stop matching the published root, and any holder of that proof could demonstrate the rewrite. Auditors: see transparency for auditors.