SafeBind.ai
Check The Evidence by hand.
Drop the whole Evidence zip and every file in it is checked against the record’s signed hashes — or check one file, and compare its SHA-256 with the number beside it in manifest.txt.
Drop The Evidence zip, or any of its files
the zip as you downloaded it, several files at once, or just one — a component, a saved page, a screenshot. The zip is unpacked here, in your browser. With session-replay.json you can also watch the session.
Session replay
or paste the contents
optional — add the record to check against
Drop the record’s export
legal-export.json, from the same archive (a dropped zip loads it for you) — the page checks its signature and timestamp, lists every component, and tells you which one each file above is
Follow the signature, step by step
What was checked on this record, and the value each check rests on.
Download the DigiCert token
Check the timestamp with openssl alone — no SafeBind page or server involved. Get DigiCert’s root certificate from DigiCert, put it in one folder with these two files, and run the lines below.
The last line prints Verification: OK. Change one character in
signature.txt and it fails.
Check it yourself
Your computer already has a tool that gives the same number, with no browser and no
internet. Open a terminal, go to the folder you unzipped, and type the line for your
system — putting the file’s real name where it says <file>.
For example: sha256sum components/network-and-device.json