{"id":58011,"date":"2026-08-13T21:54:09","date_gmt":"2026-08-13T19:54:09","guid":{"rendered":"https:\/\/truescreen.io\/verify-acquisition\/"},"modified":"2026-08-13T22:05:27","modified_gmt":"2026-08-13T20:05:27","slug":"verifier-une-certification","status":"publish","type":"page","link":"https:\/\/truescreen.io\/fr\/verify-certifications\/","title":{"rendered":"V\u00e9rifier une certification TrueScreen"},"content":{"rendered":"

Verify a TrueScreen certification<\/h1><\/div><\/section>

Check that a certification is intact and sealed, directly from your browser. Nothing is uploaded: the files you select never leave your device.<\/p>

<\/div>

You do not have to take our word for it<\/h2>

This page is a convenience, not an authority. A TrueScreen certification is sealed with open, published standards, so anyone can verify it independently with third-party tools, without using this page and without asking us for anything. The European Commission provides the reference validator for electronic seals in the EU.<\/p>

European Commission DSS validator<\/a><\/p>

Upload the XML exactly as you downloaded it: reopening and saving it changes the file.<\/p><\/div>

What a TrueScreen certification is<\/h2><\/span><\/summary>

A TrueScreen certification is a package that records how a digital content was acquired and shows that nothing has changed since. It holds a sealed XML report, the certified files and a readable report in PDF or JSON. The seal is a qualified electronic seal under eIDAS, and it covers a SHA-256 hash of every certified file.<\/p>

The package is built to be checked by anyone, at any time, without asking TrueScreen. Hashes, seal and timestamp are written in published formats, so the same verification can be run here, by a third party validator, or by a technical consultant appointed by a court.<\/p>

This page runs that check locally. Nothing is uploaded: the files stay on the device and the whole verification happens in the browser.<\/p><\/div><\/details>

How this verification works<\/h2><\/span><\/summary>

Three checks run on the package, each against a published standard. The seal on the report is an XML Signature in XAdES form, verified with RSA-SHA256 against the certificate carried inside the file. The qualified timestamp is an RFC 3161 token, checked to confirm that it covers exactly that seal. The integrity of the certified files is verified by recomputing a SHA-256 hash on each file and comparing it with the hash declared inside the sealed report. When the three agree, the chain from the sealed XML to the report, and from the report to every certified file, is complete.<\/p><\/div><\/details>

What this page does not check<\/h2><\/span><\/summary>