The signed record.

The signature authenticates the exact bytes of its matching file. Page export JSON also records a SHA-256 digest for its corresponding PDF. These are dated snapshots: current HTML, Markdown and llms text have their own reading editions.

PhishDestroy signs as the collection compiler. Authors and research agents are attributed separately in the records. File integrity does not establish the truth of a claim or change an annex’s evidence status.

During this check, 35 JSON files differed from their signatures because a later link rewrite had replaced GitHub addresses with GitLab addresses. The original bytes were recovered, then matched against the existing SHA-256 files and verified against the original signatures.

No new signature or historical date was created. The recovery applies to the signed snapshots. Current reading pages keep their current links. This verification report is unsigned.

Download a file and its matching .asc signature from the register. For page exports, open the JSON to find the PDF filename and expected digest.

Download the public key

129F C7F3 9C40 C69D 2EF3
C329 BFCF 9E8D D295 EE01

Example: the historical English main dossier.

gpg --import pgp-key.txt
gpg --fingerprint 129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01
gpg --verify index.content.json.asc index.content.json
sha256sum -c index.content.json.sha256

JSON · Signature · SHA-256 · PDF