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-03T09:50:41.952Z 2026-05-03 09:51:05 tth_v1_98d39d681824e075
2026-05-03T09:51:05.349Z 2026-05-03 09:52:07 tth_v1_98d39d681824e075
2026-05-03T09:52:07.535Z 2026-05-05 01:56:34 tth_v1_98d39d681824e075
2026-05-05T01:56:34.084Z 2026-05-05 02:38:34 tth_v1_a9869cf6efb95832
2026-05-05T02:38:34.308Z 2026-05-05 02:40:05 tth_v1_a9869cf6efb95832
2026-05-05T02:40:05.507Z 2026-05-06 14:20:26 tth_v1_a9869cf6efb95832
2026-05-06T14:20:26.648Z 2026-05-07 16:55:17 tth_v1_79e1cfc3b161390e
2026-05-07T16:55:17.926Z 2026-05-18 11:15:02 tth_v1_0f5948a4df37558c
2026-05-18T11:15:02.677Z — active — tth_v1_620284d49894d552

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/when-you-start-believing 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.