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

IssuedSupersededContent hash
2026-05-03T10:00:29.059Z 2026-05-03 10:00:43 tth_v1_b2a90d25e9af8e27
2026-05-03T10:00:43.062Z 2026-05-05 01:56:52 tth_v1_b2a90d25e9af8e27
2026-05-05T01:56:52.467Z 2026-05-05 02:38:36 tth_v1_1d8903d8c76d61ee
2026-05-05T02:38:36.534Z 2026-05-05 02:40:07 tth_v1_1d8903d8c76d61ee
2026-05-05T02:40:07.162Z 2026-05-06 14:20:58 tth_v1_1d8903d8c76d61ee
2026-05-06T14:20:58.193Z 2026-05-07 16:55:34 tth_v1_622bcc182790472b
2026-05-07T16:55:34.801Z 2026-05-18 11:15:26 tth_v1_338d4eb45b9a6006
2026-05-18T11:15:26.887Z — active — tth_v1_a923bc88fc6ba124

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/your-memory-is-not-broken-your-query-is-noisy 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.