V · Validate an evidence record
Validate an audit record. No account needed.
A bank's auditor, a supervisor, a court: anyone holding an evidence record exported from an account page can validate it here. Integrity, authenticity and proof of existence, the three things an audit trail must show. The record's hash, the seal chain, the account's signing key as we hold it, the root all chains were bound into, and the qualified time-stamp on that root: its imprint, its CMS signature, and the authority's certificate chained to the EU trusted list of its Member State. Six checks, each with its reason. Nothing in the file is kept.
or paste its contents
What the evidence record is
The record exactly as we kept it, its seal (hash, chain link, ES256 signature), the public keys of the account that sealed it, the chain links up to the time-stamp, the root document listing every account's chain head at that moment, and the RFC 3161 token the authority signed over that root.
Without us
Every step in the file's howToVerify list can be run with openssl alone: the hashes, the signature with the keys, the chain, and openssl ts -verify against the certificates published in the authority's EU trusted list. The EU DSS validator accepts the token too. This page does the same, and also asks us whether the key in the file is truly the account's.
What it proves
Integrity, authenticity and proof of existence: that the record existed, unchanged, before the time in the token; that it was made by the account whose key signed it; and that the time came from a Qualified Trust Service Provider under eIDAS Article 41. What the record says about a certificate, a licence and a decision is then what a bank shows under RTS 2018/389 Article 29 and PSD2 Article 68.