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-09-14, updated 2026-09-14; 4 revisions (this active certificate plus 3 prior).

IssuedSupersededContent hash
2026-09-14T03:53:29.123Z 2026-09-14 05:02:07 tth_v1_040885aa62d9d073
2026-09-14T05:02:07.222Z 2026-09-14 05:46:12 tth_v1_e21acf3c55d03977
2026-09-14T05:46:12.660Z 2026-09-14 06:09:16 tth_v1_d3f3cb797a97e46c
2026-09-14T06:09:16.609Z — active — tth_v1_d3f3cb797a97e46c

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/fractured-levee 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.