Evidence chain
Check the number without trusting the page.
The manifest lists every published file and its SHA-256. FreeTSA signed the manifest under RFC 3161. The commands below reproduce both checks on your own machine.
Token facts
- Authority
- FreeTSA.org
- Time
- Nov 1 17:18:10 2026 GMT
- Serial
- 0x09A16F3F
Verified against the FreeTSA chain
Two commands
1. Recompute the manifest hash.
sha256sum hu-2026-10.manifest.jsonExpected: 4717cf53c2222a648b6fcd5fe1dd65704e0c22e03c2609aad1a2414328ebe528
2. Verify the timestamp token.
openssl ts -verify -in hu-2026-10.manifest.tsr -queryfile hu-2026-10.manifest.tsq -CAfile freetsa-cacert.pem -untrusted freetsa-tsa.crtFreeTSA publishes the CA and TSA certificates on its site. The token must print “Verification: OK”.
What this proves
It proves that the published files are the files that existed when the manifest was timestamped. It does not prove that the scan method is correct or that a DNS record still looks the same today. Re-run the scanner to check the present.