From a page on the web to an evidence report
The chain has nine links. Each one produces a file that can be checked on its own. None of it sits with us.
This page follows a capture in the order the software works. The lines set in monospace come from a sample order, number 4711.
The evidence chain, read from top to bottom
The axis on the left: dark dots for capture, green for integrity and time. On the right, the order as the log records it.
The page on the web
The crawler requests the address with a fixed user agent, waits for the page to finish loading, and logs every response with status code and headers.
WARC record
Every response is stored unchanged, with request, response, headers and time. This is the archive itself, not a picture of the view.
Full page screenshot
The page is photographed at full height in three widths, so what a visitor actually saw is on the record.
Extracted text
The visible text is stored as UTF-8 with a reference to the record it came from, so it can be quoted and searched later.
Hash per file
Every single file gets a SHA-256 hash, written into a hash list. Change one byte and the hash changes.
Merkle root
The hashes are combined in pairs until one value remains. That root stands for the whole capture.
Qualified timestamp
Only the root goes to the trust service provider, never any content. What comes back is a token that binds the time in law.
WORM storage
Capture, hash list and token are written to write once storage. Administrators cannot change anything there either.
Evidence report
The report states the order, scope, hashes, root, timestamp and verification result, with the exhibits attached.
A deployment your IT team can follow
Containers, storage, directory service. The installation guide runs to 42 pages and is open before you buy.
Two states every capture can be in
The status is recalculated on every check, never stored. Colour is never the only signal: shape, wording and the verification log say the same thing.
Verify without Webichive
Verification does not depend on our software. Hash list, Merkle root and timestamp token sit beside the archive in the open and can be recomputed with standard tools. That is deliberate: evidence that only holds up inside the vendor's software is poor evidence.
Verification guide as PDF, 6 pages