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; 7 revisions (this active certificate plus 6 prior).

IssuedSupersededContent hash
2026-05-03T09:34:14.320Z 2026-05-05 01:56:06 tth_v1_84859af4c0087735
2026-05-05T01:56:06.939Z 2026-05-05 02:38:31 tth_v1_fea90f604519f7d0
2026-05-05T02:38:31.298Z 2026-05-05 02:40:03 tth_v1_fea90f604519f7d0
2026-05-05T02:40:03.178Z 2026-05-06 14:19:41 tth_v1_fea90f604519f7d0
2026-05-06T14:19:41.577Z 2026-05-07 16:54:40 tth_v1_55050f16979dc8f2
2026-05-07T16:54:40.248Z 2026-05-18 11:14:08 tth_v1_d73a10b26d103bc0
2026-05-18T11:14:08.867Z — active — tth_v1_cf25687673061a52

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/severance-the-metaphor-were-all-living 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.