Paste a code. Get a verdict.
Every CLEARSKY dossier carries an ECDSA signature and a public verification
code. Paste the code below, or visit a /v/<doc-id> URL
directly. The verifier returns the signature, the signing key fingerprint,
the signed-at timestamp and a plain-English verdict. It does not reveal
investigation contents, analyst identities or subject identities.
Or verify your copy of the file
Have the PDF in hand? Drop it in to confirm the exact bytes you received match the signed original, down to the byte. Your copy is sent over HTTPS to recompute the signature check only; it is not stored.
Three things this page proves, and three it does not
Dossier finalisation is gated on analyst confidence. The canonical dossier bytes are hashed SHA-256 and signed with an ECDSA P-256 key held by the dedicated signing service.
-
01
This dossier was signed by the 79th Unit. The ECDSA signature on the file matches our public key. The key fingerprint is shown in the verdict block above and pinned at
.well-known/clearsky-verifier-keys.json. -
02
The dossier has not been tampered with since signing. The payload hash matches what was signed. Any change to the document body invalidates the signature and the verdict shows "Tampered".
-
03
The dossier was signed at the timestamp shown. The signed-at value is part of the signed envelope. It cannot be backdated or postdated without breaking the signature.
What this page does NOT do
- It does not reveal the contents of investigations to the public.
- It does not reveal analyst identities.
- It does not reveal subject identities of ongoing investigations.
Verification requests are logged for audit: the time, the document id and the outcome. We do not publish who verifies.
Need to show this to procurement or counsel without an active investigation? See the sample dossier and verifier verdict. Both are clearly labelled as demonstrations.
What each verdict looks like
Static illustrations of the four possible outcomes. Nothing below is a live verification result.
The signature matches our published public key and the payload hash matches what was signed. The only outcome that means the document is genuine and unaltered.
The bytes do not match the signed original. Treat the file as untrustworthy.
The dossier was signed, but the issuer has since withdrawn it. The envelope shows when and why.
No document with that id exists. Check the code, or the document was never issued by CLEARSKY.
Verifier manifesto
What we promise about the verifier and what we deliberately don't promise. Plain English, no marketing.
Open manifesto →Cryptographic baseline
ECDSA P-256 and SHA-256: how canonical dossier bytes are hashed and signed, and where the public keys are published.
Open baseline →How to cite a dossier
The recommended citation format for legal filings, compliance reviews and academic work.
Open citation guide →