Verify an erasure certificate
Confirm that a FileX erasure certificate is genuine and unaltered. Drop in the .html or .json certificate and FileX checks its integrity hash and, if present, its post-quantum signature.
How it works
- Open the Verify Cert tool and drop in the certificate file (the
.htmlreport or the.json). - FileX recomputes the SHA-256 integrity hash over the certificate's canonical contents and compares it.
- If the certificate was signed, FileX verifies the ML-DSA-65 signature and shows the signer's FileX ID.
- Read the result: integrity valid/invalid, and signature valid, invalid, or unsigned.
Forge-resistant, even against quantum computers
Certificates are signed with ML-DSA-65, a NIST-standardized post-quantum signature. A signature that verifies today will still be unforgeable in a post-quantum world — the right property for audit evidence you may need to defend years from now.
The same check as the desktop CLI
The certificate format and its hash are byte-identical between this browser tool and the downloadable FileX Eraser Tool, and both verify the same ML-DSA-65 signature. A certificate produced by either verifies with the other.
Frequently asked questions
Is the certificate uploaded to check it?
No. Verification runs entirely in your browser — the certificate never leaves your device.
What does an unsigned certificate mean?
It still has a SHA-256 integrity hash proving it has not been altered, but no cryptographic proof of who issued it. A signed certificate additionally proves authorship via the issuer's FileX ID.