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-03T15:29:33.267Z 2026-05-03 15:32:55 tth_v1_ae8a120aa1ea2484
2026-05-03T15:32:55.918Z 2026-05-04 10:06:21 tth_v1_ae8a120aa1ea2484
2026-05-04T10:06:21.946Z 2026-05-05 01:57:37 tth_v1_ae8a120aa1ea2484
2026-05-05T01:57:37.921Z 2026-05-05 02:38:40 tth_v1_a301ba282f28c792
2026-05-05T02:38:40.411Z 2026-05-05 02:40:10 tth_v1_a301ba282f28c792
2026-05-05T02:40:10.334Z 2026-05-06 14:21:59 tth_v1_a301ba282f28c792
2026-05-06T14:21:59.573Z 2026-05-07 16:56:18 tth_v1_c23529b0cb1ffeb0
2026-05-07T16:56:18.612Z 2026-05-18 11:16:35 tth_v1_e4dda1cd72b921db
2026-05-18T11:16:34.916Z — active — tth_v1_10ab63f586e0e571

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/notes-from-the-test-bench 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.