Verify a seal.

Every examination concludes with a sealed report: an immutable artifact bundle whose contents are cryptographically fingerprinted (SHA-256) and catalogued in a signed manifest. Alter a single byte of any constituent file, and the cryptographic verification fails. Each manifest carries two independent signatures issued by our signing station — classical Ed25519 and post-quantum ML-DSA-65. To defend against cryptographic downgrade attacks, a manifest sealed under the current scheme requires both signatures: omitting, stripping, or invalidating either one fails verification — neither may be stripped. Manifests sealed before 2026-08-31 carry the classical signature only and verify as legacy single-signed records, honestly labeled — eligibility for legacy status is determined from the signed manifest's own declared signature policy: only a manifest carrying no post-quantum signer identity at all may verify classical-only, and a manifest that declares one fails verification if either signature is missing or invalid. The manifest is independently time-stamped by an RFC 3161 Trusted Timestamp Authority: the timestamp attests that the signed digest existed no later than the stated time — a datum-of-existence proof, bounded by the timestamp authority's own integrity, not a statement about what happened before or after. That verified anchor, never a date printed in the report body, is the signing time enforced against the registered key's published validity window; within the authority's attestation, the chronological baseline cannot be backdated or postdated by us.

It proves byte-level integrity and attested origin: our signing station attests, under its keys and at the stated timestamp, that these exact bytes are what the examination produced — a signature proves that we signed these bytes; the provenance claim rests on that attestation and on the report's own signed evidence chain, which records how the examination was conducted. It does not act as an endorsement, a warranty, or a guarantee of future model behaviour — signatures attest the integrity of the record; the empirical evidence speaks for itself. Verification is free, permanent, and unmetered; inquiries are strictly authenticated, never anonymous, and we never disclose who checked to the commissioning client unless that client explicitly elected Verification Transparency.

Submit the seal string through the form below, or transmit it directly to our intake. A seal-string lookup establishes that a seal exists, the subject it was issued for, and whether it stands — it does not, by itself, authenticate a document in your hands. Byte-level authenticity requires the artifact itself, or its SHA-256 digest, checked against the signed manifest: a genuine seal string attached to an altered file is a mismatch, and the response will say so. We verify the signature chain, record date, and subject identifier against the active revocation registry; if current revocation status cannot be established at answer time, the response is status unknown — never clean. Before trusting any signed report, independently confirm our public signing-key fingerprints against the canonical keys published on this page and in the transmittal cover note.