Chain of custody

Check whether a source file is still available and inspect its preservation history. A preserved file helps you audit a source; it does not by itself establish accuracy or court admissibility.

Open the evidence workbench to search prepared record passages and preserved captions, inspect source links and compare evidence coverage. Machine text and caption timing retain their review labels.

The legacy web-capture collection below covers source URLs captured between April and May 2026.

Legacy capture loss: 89 files survive; 1,333 captures were lost in the August 2026 host failure. Third-party copies may be available. Original timestamp tokens were also lost; surviving files were re-timestamped on 4 October 2026.

Legacy collection totals and preservation history

Captures were SHA-256 hashed and timestamped via RFC 3161 when taken.

1,422 URLs were captured from 485 domains. The evidence vault was lost in the August 2026 host failure. 89 (6.3%) captures survive as PDF or HTML and are linked below. 1,333 (93.7%) are lost. For those, only the SHA-256 hash recorded at capture survives: for 939 of them it is in the GPG-signed manifest, for the rest only in the published index. 1,226 lost captures have a Wayback Machine copy, which is a third-party archive copy, not ours.

The original RFC 3161 tokens were lost with the vault. The surviving files and the signed manifest were re-timestamped on 4 October 2026.

What the preservation labels mean

Preserved copy
A captured file is available here. Check its capture details and limits.
Third-party archived copy
Another archive holds a copy. It is separate from this site’s capture.
Capture lost
The file is no longer held here. A surviving hash cannot recreate or independently verify the missing file.

Preserved video recordings

This newer collection is separate from the legacy web-capture totals above. Open an incident record to see its warning, full recording, caption status and individual preservation receipt.

Complete collection manifest (JSON) · Detached GPG signature · Public signing certificate

Signer fingerprint: 78CB874267978D429847B989DC172983F4C71CAB.

The manifest lists preserved source streams, capture receipts, captions and viewing derivatives. The project operator’s signature binds those bytes; it is not a publisher signature or an independent trusted timestamp. It does not establish authenticity, factual completeness or court admissibility.

Showing 1–50 of 1422

URLCapturedCaptured asStatusCited by

Verify It Yourself

Surviving captures can be checked without trusting this site. The original timestamp tokens were lost with the vault, so the proof below dates from the 4 October 2026 re-timestamp. Lost captures cannot be re-verified; only their recorded hash survives.

1
Hash a surviving file
sha256sum snapshot.pdf
# Compare with its line in SALVAGE-MANIFEST-20261004.sha256
2
Verify the RFC 3161 timestamp on that manifest
openssl ts -verify \
  -data SALVAGE-MANIFEST-20261004.sha256 \
  -in freetsa.tsr \
  -CAfile freetsa-cacert.pem -untrusted freetsa-tsa.crt

Files: freetsa.tsr, freetsa-cacert.pem, freetsa-tsa.crt. A second token from DigiCert: digicert.tsr, verified with digicert-trusted-root-g4.pem. Certificate fingerprints: CERTS.txt.