Fingerprint a file in your browser
Choose a file and the page computes its SHA-256 locally. The file is never uploaded, because there is nowhere for it to be uploaded to.
This website. Uses the browser's own Web Crypto API. Browser
The nontechnical path: no terminal required.
Everything on this page runs as a static site. There is no account, no upload, and no server that could see your files.
In your browser
What you can try without a terminal.
See one byte change the identity
Two nearly identical texts, one byte apart, hashed in front of you. The digests share nothing.
This website.Read recorded outcomes from the reference core
Fifteen situations were put through the actual reference assurance kernel once, and its exact answers were recorded, each carrying the digest of the input it came from. These are recordings: reading one back is not the same as evaluating now, and the site says so wherever they appear.
content/kernel-fixtures/ · produced by the AC7 reference kernelDownload what you just saw
The page builds a JSON record of your session in the browser and hands it to you. No server takes part.
This website. 01 The mechanism
Why a site with no server can promise privacy.
How this works
- 01
Every page is built before publication
The HTML you receive was generated ahead of time and written to a file. Nothing is assembled per visitor, so there is no request to log.
- 02
There is no backend to receive anything
No database, no API, no account system. The deployment is a folder of files served as-is.
- 03
What runs, runs in your browser
The small amount of JavaScript here computes digests and switches panels. It issues no network requests, which the test suite asserts on every page.