Verification steps

  1. Load ToneThread Root public key…
  2. Verify Tenant Site Certificate signature…
  3. Verify Post Certificate signature…
  4. Recompute ToneHash of post content…
  5. Compare recomputed hash to certificate…

Revision history

Originally published 2026-05-08, updated 2026-05-18; 4 revisions (this active certificate plus 3 prior).

IssuedSupersededContent hash
2026-05-08T09:50:50.515Z 2026-05-08 09:50:51 tth_v1_1d9c3c687455bc31
2026-05-08T09:50:51.690Z 2026-05-08 16:29:11 tth_v1_1d9c3c687455bc31
2026-05-08T16:29:11.803Z 2026-05-18 11:26:46 tth_v1_d56908f3c11b3c7b
2026-05-18T11:26:46.116Z — active — tth_v1_48392395828ca6db

What this page exposes

Verification runs on the server. The browser only sees the public summary in the sidebar and the step-by-step ok/fail result above — never the certificate's raw signature, the tenant's raw public key, the ToneHash salt, the per-axis tonal scores, or the compact fingerprint string. Those stay on the signing host.

The public JSON at /tonehash/cert/what-a-deposition-revealed-about-pattern-recognition mirrors the same surface. To independently audit a certificate's raw signed payload you must request an authenticated cert-bundle export from the operator — how to request access.