How Integrity Verification Works
This page verifies that files for this site match a signed manifest published by the operator.
- Step 1: It downloads
manifest.json, manifest.sig, and integrity_pubkey.pem.
- Step 2: It verifies the Ed25519 signature over the exact manifest bytes.
- Step 3: It downloads each listed file, computes SHA-256 in your browser, and compares with the manifest hash.
What this achieves: It detects tampering, partial uploads, cache corruption, and unexpected file changes for the files listed in the manifest.
Important limitations:
- If an attacker can change both site files and the trusted public key shown here, this check can be bypassed.
- This only verifies listed static files; it does not prove endpoint trust, runtime browser integrity, or network privacy metadata.
- It is a trust signal, not a replacement for transport security, secure infrastructure, and protocol-level cryptography.
Best practice: compare the public key fingerprint against an out-of-band source (release notes/repo/docs) when high assurance is required.