Verify a sealed document
Every document TrustNav (trustnav.health) sends carries a seal on its face — a content hash (“root”) computed over its exact bytes. Paste that root to confirm the copy you hold is authentic and current.
42 edition roots resolve through this page as of the registry export: 23 currently standing · 14 withdrawn · 12 superseded · 1 invalidated candidate. The correction states overlap — 8 roots carry both a withdrawal and a supersession — so those terms account for all 42 roots only once the overlap is subtracted, not by adding them. Each root answers with its recorded custody state — and with what that state does, and does not, establish.
“Currently standing” is derived positively: a root counts as standing only when it carries no correction state and no other recorded lifecycle state. An invalidated candidate is registered as invalidated rather than removed from the registry, and is not counted as standing — deriving the figure the other way round, as everything not marked withdrawn or superseded, would silently count it, and would silently count every lifecycle state added after this page was written.
No titles, no contents, no recipients — a hash reveals nothing about a document. For a sealed edition this page answers exactly one question: is the copy you already hold the sealed edition.
A signed governance instrument is public by design, so its seal is kept in a separate, named register: hash the signed PDF and the answer tells you which policy, which version, effective when, and who adopted it. The same box answers both — you should not have to know which register your hash belongs to. The hash is held outside the document, because a file cannot contain a hash of its own bytes: inserting it changes the bytes it was computed over. Our policies and their status: /policy/carrier-funding-independence.
Corrections are published as new sealed editions, never silent edits. If your root shows superseded, the sender owes you the current one — corrections@trustnav.health.
A withdrawn root is authentic: it is our document, sealed on the date shown. Its content has been retracted and no corrected edition exists in its place. We withdrew our own flagship finding set this way on 2026-08-04 — the reasons, the numbers, and the limits are published at /record/network-integrity.
Bundle-sealed exhibits also carry an embedded verifier that recomputes their own artifacts in your browser — this page is the quick outer check; the exhibit itself is the deep one.