Verify a record
Open the verifier
Go to klariqo.com/vcon. Nothing is uploaded to a server. The check runs locally in your browser.
Load the record
Paste the record, or upload the
.vcon.json file, or try the built-in sample to see a valid result first.What the results mean
| Result | What it means |
|---|---|
| Signature valid, signed by Klariqo’s key | The record has not been altered since signing, and it was signed by Klariqo’s published key. |
| Signature valid, not Klariqo’s key | The signature is valid, but the signer is not Klariqo. Klariqo makes no claim about that record. |
| Invalid signature | The record was altered after signing, or its signature does not match the certificate. A genuine, unaltered record passes this check. |
| No signature present | The record carries no signature to verify. |
| Not a vCon | The file is not a vCon record. |
| Encrypted | The record is encrypted and cannot be read or verified without the decryption key. |
What “signed by Klariqo’s key” means
Klariqo publishes its signing key, and the verifier confirms a record was signed by that key. This is self-asserted: we vouch for our own key, we are not a certificate authority. The strong, independent guarantee is the tamper check. A valid signature proves the record’s contents are exactly what was signed, byte for byte, including the SHA-512 fingerprint of the recording. For an outside attestation that the record existed at a point in time, see third-party witnessing.Signed vCons
How the signature makes a record tamper-evident.
The evidence chain
Where verification fits in the full story.