Verify a certificate or a point-in-time posture statement.
An Enclave AI™ evidence integrity certificate, and a point-in-time posture statement (“this organization was recorded as met for requirement 3.1.1 at 2026-09-01, based on evidence whose SHA-256 values are listed”), are both sealed with SHA-256 over their own content and, when a signing key is provisioned, signed with Ed25519. Anyone holding one can check it without trusting or contacting us: recompute the seal, and verify the signature against the published public key. This page runs that computation for you; the same check can be done offline with the key below.
The public key
Loading the published verification key…
What a verdict means. verified (verified_signed for an evidence integrity certificate): the seal recomputes and the Ed25519 signature checks against the published key. sealed_unsigned: the content is internally consistent, but no signing key was provisioned when it was issued, so authenticity rests on where you got it. sealed_signature_unchecked: the content is consistent and signed, but no public key was available to check the signature. invalid, or a verdict beginning invalid_: the seal, the evidence root or the signature does not check, so the content was altered after sealing or was not signed with the published key. A statement is the platform’s recorded status, scored under the DoD Assessment Methodology for NIST SP 800-171 Rev 2, or unscored under a Rev 3 target. CMMC Level 2 is bound to NIST SP 800-171 Rev. 2 today: 32 CFR 170.14(c)(3) states that the CMMC Level 2 security requirements are identical to the requirements in NIST SP 800-171 R2. It is not a certification and not an assessor’s finding, and it says so in its own scope_of_attestation fields.
The security boundary, stated precisely → · Who is responsible when the AI is wrong → · What each seat sees →