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-03T10:22:29.051Z 2026-05-03 10:26:35 tth_v1_addb1a755dc92e1f
2026-05-03T10:26:35.797Z 2026-05-03 10:32:49 tth_v1_addb1a755dc92e1f
2026-05-03T10:32:49.208Z 2026-05-05 01:57:29 tth_v1_3d0e42933b084e8c
2026-05-05T01:57:29.349Z 2026-05-05 02:38:39 tth_v1_75d4903fe8b700f4
2026-05-05T02:38:39.598Z 2026-05-05 02:40:09 tth_v1_75d4903fe8b700f4
2026-05-05T02:40:09.623Z 2026-05-06 14:21:41 tth_v1_75d4903fe8b700f4
2026-05-06T14:21:41.343Z 2026-05-07 16:56:09 tth_v1_c55b3cd5b70cec27
2026-05-07T16:56:09.090Z 2026-05-18 11:16:18 tth_v1_012345c880ee928e
2026-05-18T11:16:18.493Z — active — tth_v1_44ad49f14fe6c0a2

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/curriculum-vitae-a-note-for-the-newly-self-issued 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.