Verify a file timestamp.
Load the RFC 3161 timestamp token saved in the Akta attestation. The tool reads it locally — when it was issued, which authority (TSA) issued it and for which fingerprint. Attach the file and your browser computes its fingerprint and compares it with the timestamp. The file never leaves your device.
Scope of the reading: the token fields and the fingerprint match are computed in this browser. Cryptographic verification of the timestamp authority’s signature and of the trust chain runs after you click "Verify the signature cryptographically" (only the fingerprint and the token are sent, never the file content) or through the offline verifier for the whole package. A positive result does not replace the assessment of evidence by a court or an expert.
What this verification settles
The check pairs two independent things: the file fingerprint computed on your own device and the RFC 3161 timestamp from your Akta certificate. When both agree, you hold technical proof that this exact file already existed at the moment recorded in the token.
The token carries a moment signed by an independent timestamp authority (TSA). It sets the date from which this content is documented as existing — regardless of any dates written inside the file itself.
The SHA-256 fingerprint ties the file to the token by content. The smallest change to the document yields a different fingerprint, so a similar file or another version will not pass as the same material.
Reading the token and comparing the fingerprint happen in this browser. The file is not uploaded, and the result rests on the timestamp authority’s signature — not on Akta’s assurance.
A positive result means the token matches the provided fingerprint and that the time the token was issued can be read. You should still confirm that you are examining the correct file from the correct package.
A warning or negative result does not settle the value of the material. It usually points to a wrong file, a copied token, a different version of the document or an untrusted issuer — and calls for a manual check.
The whole package, file by file
The certificate confirms one material. The entire handoff package is checked by a standalone verifier in Python — no extra installation, no connection to Akta. It recomputes the fingerprints of every file version listed in the package and checks the manifest, its seal and the link to the timestamp.
python3 akta_verify.py package.zip
The same script ships inside every package as AKTA_WERYFIKATOR.py, so the recipient runs it locally on the unpacked directory or the ZIP file and compares the report with the contents of the handoff.
A file outside the manifest, a missing material or a mismatched fingerprint holds the package for clarification. That is how substitution, an incomplete export or files added after the package was generated are caught.
Akta shows the technical link — the procedural finding stays with the court and the parties.