Evidentiary Declaration

This record certifies that the evidentiary unit identified below was received, structurally verified, and deposited in an independent external system at the indicated timestamp. From that moment, the data is no longer under the control of the originating system.

Reference ID
EVIDE-20260405-0029
CWC Code
CWC-20260405-01
Status
Certified
SHA-256 Hash
d0861f8ce26faeabdb074cb9c800db6fa280e9198b4584f32f1823420919ed97
Intake Timestamp
2026-04-05 15:33:26 UTC
Published on Registry
05 Apr 2026 · 15:35 UTC

Other public records with the same hash

These records expose the same SHA-256 hash. The match may help identify repeated deposits or possible links worth examining, but it is not a chain link and does not show the same origin or the same author.

EVIDE-20260402-0010 · EVIDE-20260403-0016 · EVIDE-20260403-0017 · EVIDE-20260411-0028 · EVIDE-20260405-0030 · EVIDE-20260411-0031 · EVIDE-20260406-0033 · EVIDE-20260406-0034

The comparison only concerns the equality of the published values. Depending on the record type, the hash may refer to the bytes of a file, a text, a URL string or a canonicalized payload: EVIDE does not independently verify that the underlying materials are the same.

This record is published for public verification purposes. The evidentiary value derives exclusively from the certified forensic package, not from the content of this page.

Independent Verification

Record type: file (byte-for-byte verification)

Verifying this record requires the original file, byte for byte: the hash was computed on the bytes of the file received at intake. A converted, recompressed or re-saved copy (for example exported from another program) may have a different hash even if it looks identical.

Compute the SHA-256 hash of the original file:

# Linux
sha256sum filename.pdf

# macOS
shasum -a 256 filename.pdf

# Windows (PowerShell)
Get-FileHash filename.pdf -Algorithm SHA256

PowerShell displays the hash in uppercase: the value is the same.

Compare the result with: d0861f8ce26faeabdb074cb9c800db6fa280e9198b4584f32f1823420919ed97

What this verification covers. The hash and the intake timestamp shown here belong to the base EVIDE deposit: both are produced by the EVIDE server at intake, independently of the system that produced the content, and the timestamp is not a qualified time stamp.

FEDIS, in general. FEDIS is a separate, optional service: a forensic document that the certifier signs with a qualified electronic signature and that receives a qualified electronic time stamp (eIDAS Art. 41) issued by a third-party qualified trust service provider. The time stamp attests the moment at which it is applied to the FEDIS document: it does not make the intake timestamp above qualified, does not date the original event and does not prove that the content is true. This page does not show data from any FEDIS document relating to this record.