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:57:32.802Z 2026-05-05 01:56:44 tth_v1_c40053743ba90326
2026-05-05T01:56:44.433Z 2026-05-05 02:38:35 tth_v1_5567d332de571f3b
2026-05-05T02:38:35.741Z 2026-05-05 02:40:06 tth_v1_5567d332de571f3b
2026-05-05T02:40:06.359Z 2026-05-06 14:20:43 tth_v1_5567d332de571f3b
2026-05-06T14:20:43.109Z 2026-05-07 16:55:26 tth_v1_a3096a9ba9cfe1e4
2026-05-07T16:55:26.279Z 2026-05-18 11:15:18 tth_v1_c4e4f68adc06eb07
2026-05-18T11:15:18.646Z — active — tth_v1_e88c29c1b38ad3fd

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/the-confident-wrong 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.