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:46:14.808Z 2026-05-05 01:56:24 tth_v1_927ff06c7adfaa41
2026-05-05T01:56:24.619Z 2026-05-05 02:38:33 tth_v1_9fb69e66f75ffeff
2026-05-05T02:38:33.646Z 2026-05-05 02:40:04 tth_v1_9fb69e66f75ffeff
2026-05-05T02:40:04.709Z 2026-05-06 14:20:10 tth_v1_9fb69e66f75ffeff
2026-05-06T14:20:10.463Z 2026-05-07 16:55:08 tth_v1_df9257ed9183d601
2026-05-07T16:55:08.416Z 2026-05-18 11:14:44 tth_v1_45dcfce6ad4808e5
2026-05-18T11:14:44.186Z — active — tth_v1_cb8fa0920dcb9458

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/we-have-an-api-and-were-prepared-to-use-it 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.