What a pass means
A plain-language summary of what this verifier checks. The exact rules are in the protocol description.
A pass means
The sealed content matches its recorded integrity digests. The verifier reads the receipt.json file (the receipt, the record embedded in the sealed export) and recomputes its SHA-256 digests (including a Merkle root over the events) and compares them with the digests recorded in the same file. If any sealed record or event was changed and the digests were not recomputed, the check fails. On newer receipts the outer identity fields (such as the record type and the requester role) are bound by a digest as well.
A pass does not mean
- Who sealed the export. The digital signature is not validated here, and the signing certificate is currently self-signed (a staging certificate, not issued by a certificate authority).
- When it was sealed. The timestamp is not validated here. Dates shown are the dates stated in the sealed export.
- That nobody could have produced it. The checks use public SHA-256 maths and no secret. Someone who edits the content and recomputes every digest would also pass. Only signature validation, which this verifier does not yet perform, would detect that.
- That the content is true, complete or approved. A pass is about integrity of the file, not about the accuracy of what was recorded or that any work was done.
- Anything about the cover page. Names read from the PDF cover page (such as the vessel name or who exported the sealed export) are not covered by the seal, and are labelled as such.
Other results
Cautions (amber) means at least one check needs review, for example a legacy file with no integrity block, or an older file whose digest cannot be confidently compared. Treat it as unverified. Failed (red) means the content does not match its recorded digests or its integrity block is missing or malformed.
Privacy
Every check runs in your browser. The sealed export is not uploaded and no data leaves your device.