Paste a certificate JSON, or upload a file to check if it matches a signed certificate. Independent, public, no API key required.
Paste the full certificate JSON returned by /v1/certify.
Enter a certificate ID to look it up and verify it automatically.
Check if content matches a certificate's content hash. Paste the text or upload a file, then provide the expected SHA-256 hash from the certificate.
Content is hashed. When you certify content through CR Gateway, the content is hashed with SHA-256. This hash is stored in the certificate. If anyone changes even one character, the hash will be completely different.
Certificate is signed. The certificate (including the content hash, timestamp, and validation result) is signed with Ed25519. This signature can only be produced by CR Gateway's private key. It cannot be forged.
Anyone can verify. To verify, we reconstruct the canonical certificate data, then check the Ed25519 signature against CR Gateway's public key. If the signature matches, the certificate is authentic. If any field was changed, it fails.
Content can be checked. To prove content was not tampered with, hash the current content with SHA-256 and compare to the content_hash in the certificate. If they match, the content is exactly what was certified.