Published SHA-256 fingerprints of every HTML page on this site. Anyone can verify that page content matches the reference hash, computed locally using the W3C Web Crypto API. Nothing is uploaded.
Click the button below to fetch each page and compute its SHA-256 fingerprint in your browser. The result is compared against the published reference hash. A mismatch indicates the page has been modified since publication.
| Page | Reference SHA-256 | Live SHA-256 | Status |
|---|
This site can operate offline once your browser has stored the sealed pages. Open it once while connected, then turn off Wi-Fi and mobile data, reload, and run the checks below. The stored copy is exactly the sealed set — nothing is added to it while you browse.
Every fingerprint in the table above is listed in SITE-SHA256SUMS. The SHA-256 of that file is the site root, and the site root is the value anchored on Bitcoin and Ethereum. One value fixes the entire site at a point in time.
Revision r11, anchored 25 August 2026 on both chains.
Bitcoin block 964001, 12:17:30 UTC ·
Ethereum block 25833895, 18:06:47 UTC.
Each transaction commits a Merkle root, not this hash directly; the inclusion path is published as
Bitcoin proof and
Ethereum proof.
Replaying a path is one rule applied repeatedly: node = SHA-256(ASCII(left hex) || ASCII(right hex)),
from the leaf up to the root written in the Bitcoin OP_RETURN or the Ethereum calldata.
The full anchor history is on the verification page.
If the site root shown above differs from the anchored root, the site has been re-sealed since its last anchor and the current root will be anchored at the next deployment. That is the expected state between a deployment and its anchor, not a fault: a page cannot contain the digest of a file set that includes itself, so the published anchor is always the preceding one. What must never happen is a stale root presented as current, which is why both values are shown separately.
| Property | This website | An IIC card |
|---|---|---|
| Works with no network | Once the browser has stored it | Always |
| Needs an HTTPS origin | Yes | No |
| Needs a service worker | Yes | No |
| Runs as a standalone file | No | Yes |
| Can be evicted by the browser | Yes | No |
| Needs one connected visit first | Yes | No |
| Needs a browser | Yes | Yes |
A card is independent of any origin, server or cache. It is not independent of a browser: it is an HTML file and needs one to run. This page applies the card's discipline to the website. It does not stand in for the card, and the two should not be read as the same claim.
A successful match between the locally-computed SHA-256 hash and the published reference provides:
This verification confirms page integrity only. It does not constitute legal recognition, certification, accreditation, or endorsement by any authority. Internet Identity Card ™ is a private software-based identity and verification platform developed by Https Card — Internet Identity Card Ltd.