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:27:39.084Z 2026-05-05 01:55:49 tth_v1_29c43cb576d7628f
2026-05-05T01:55:49.425Z 2026-05-05 02:38:28 tth_v1_cc6359206955b692
2026-05-05T02:38:28.911Z 2026-05-05 02:40:01 tth_v1_cc6359206955b692
2026-05-05T02:40:01.280Z 2026-05-06 14:19:14 tth_v1_cc6359206955b692
2026-05-06T14:19:14.519Z 2026-05-07 16:54:22 tth_v1_511cc104eab145ac
2026-05-07T16:54:22.187Z 2026-05-18 11:13:38 tth_v1_f1f34159e0867cc4
2026-05-18T11:13:38.809Z — active — tth_v1_17b63296f5168ced

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/late-to-class-right-on-time 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.