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-03, updated 2026-05-18; 9 revisions (this active certificate plus 8 prior).

IssuedSupersededContent hash
2026-05-03T09:30:12.829Z 2026-05-03 09:30:51 tth_v1_6726442144e405d7
2026-05-03T09:30:51.610Z 2026-05-03 09:34:41 tth_v1_6726442144e405d7
2026-05-03T09:34:41.253Z 2026-05-05 01:55:58 tth_v1_6726442144e405d7
2026-05-05T01:55:58.276Z 2026-05-05 02:38:30 tth_v1_0d812572916cce77
2026-05-05T02:38:30.490Z 2026-05-05 02:40:02 tth_v1_0d812572916cce77
2026-05-05T02:40:02.119Z 2026-05-06 14:19:27 tth_v1_0d812572916cce77
2026-05-06T14:19:27.804Z 2026-05-07 16:54:29 tth_v1_be32f2031e5ef6ce
2026-05-07T16:54:29.847Z 2026-05-18 11:13:52 tth_v1_08f7d56cc7c97f97
2026-05-18T11:13:52.515Z — active — tth_v1_590e6a6992547105

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/staying-the-course-when-the-frameworks-hold- 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.