Check a file or a receipt
Drop a file, or enter a receipt ID. The file is read and digested by your browser and compared against the digest one sample evidence record commits to. Nothing is uploaded and no request is made.
This page is a demonstration of the interface, not the service. It answers for one sample record, runs one check, and reports every other check as not performed, with the reason it was not performed. The application runs the rest against sealed bytes and a key directory that a static page does not have.
The sample record this public page answers for.
This page runs one check, in your browser, against one sample record. It is a demonstration of the interface, not the service.
Are these the bytes the record commits to?
The digest is computed in your browser. Your file is not uploaded, and no part of it reaches Steganosaur or anyone else.
- Exact bytes sha-256 over the file you choose, against the digest the sample record commits toNot checked
Choose a file to run this check.
Does the evidence record hold together?
These checks read sealed bytes and a key directory. The application runs them; this page does not have them.
- Receipt structure the receipt decodes under own-receipt/1 and its canonical encoding profileNot checked
Not performed here. The public demonstration carries a rendering of a receipt, not receipt bytes.
- Signature over the record body the signature across the canonical record bytes, under the suite the receipt namesNot checked
Not performed here. Nothing on this page holds a signature or a key to check one against.
- Timestamp attachment an RFC 3161 token over the record digest, from an external authorityNot checked
No timestamp attachment is held for this sample.
Do content-derived signals relate these two things?
Fingerprints and publication provenance are derived from what a file contains, so they need the file to be read by the service that holds the record.
- Perceptual fingerprint distance between the candidate's fingerprint and the one the record carriesNot checked
Not performed here. This page reads no file content; it computes one digest and stops.
- Publication provenance packet a per-copy handle written into a publication copy's metadata, read back and resolvedNot checked
Not performed here. A publication copy's handle is read by the command line's publication-verify, which this page does not have.
There is no overall verdict here. Each check reports its own outcome, its own reason and what it was about.
A digest comparison answers one question: whether two sequences of bytes are the same sequence of bytes. It does not establish who made either of them.