No integration, no software to install, and the file never leaves your computer
Seal a file today. Prove later that nobody changed it.
An advice note, a signed contract, an email you sent, a report you filed: choose the file below, or the folder that holds them, and press Seal. Your browser computes its fingerprint; we record only a salted fingerprint of that, in a log nobody can edit, including us. You download a small receipt and keep it next to the file. Years later, anyone you give both to can check, on this page or with the free offline verifiers, that the file is exactly the one sealed, and when.
Seal
No account, no form, no email. The first seal takes a free sandbox key for you, kept in this page only; sandbox keys seal up to 50 files a day.
The receipt holds the folder’s list of files and their fingerprints.
Download the list on its own to check the folder later with
sha256sum -c (Linux) or shasum -a 256 -c (Mac), run inside it.
Keep the receipt with the file. It holds the salt that links them; without it nobody, including us, can show which file was sealed. This page does not keep a copy.
When you send the file to someone who may need to rely on it, send the receipt with it. They can check both at riskrouter.eu/check, with no account, and the file still never leaves their computer.
Your sandbox key, to seal more files later
Shown once and not recoverable: only its SHA-256 is stored. This page reuses it until you close it; to seal from another visit, paste it under I already have an API key.
I already have an API key
Check
Given a file and its receipt, this checks that the file is the one sealed, that the log recorded it, and that we signed the log’s state, against our published key. A folder is checked file by file: anything missing or changed fails. One file from a sealed folder can be checked against the folder’s receipt. Nothing is uploaded.
What a seal proves, and what it does not
- It proves
- that this exact file existed no later than the moment its seal entered the log, and has not changed by a single byte since. The log’s signed state is time-stamped by two independent authorities (not qualified under eIDAS) and anchored in Bitcoin.
- It does not prove
- who wrote the file, that what it says is true, or that it satisfies any law. It shows the file is the one you had at the time; whether that file is enough is yours to judge.
- Checkable without us
- The receipt is a standard record bundle. The open-source verifiers check it
offline:
python3 riskrouter_verify.py receipt.json --key anchors/. Verifiers and keys - A folder
- is one entry in the log, however many files it holds (up to 10,000). The receipt lists
each file’s path inside the folder and its SHA-256, in the format
sha256sumwrites, and that list is what is sealed. It proves those files were there, as they were; a file added later is not covered, and is said so when you check..DS_Store,Thumbs.dbanddesktop.iniare left out: the system rewrites them when a folder is only opened. - For many files
- Sealing by hand suits a few files a day. For every advice note your software writes, the same seal is one API call from inside it. Integrate