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; 8 revisions (this active certificate plus 7 prior).

IssuedSupersededContent hash
2026-05-03T09:38:41.953Z 2026-05-03 09:41:18 tth_v1_d555c496d7149266
2026-05-03T09:41:18.819Z 2026-05-05 01:56:16 tth_v1_d555c496d7149266
2026-05-05T01:56:16.929Z 2026-05-05 02:38:32 tth_v1_78f02298f3c5455e
2026-05-05T02:38:32.382Z 2026-05-05 02:40:03 tth_v1_78f02298f3c5455e
2026-05-05T02:40:03.943Z 2026-05-06 14:19:58 tth_v1_78f02298f3c5455e
2026-05-06T14:19:58.884Z 2026-05-07 16:54:49 tth_v1_3ba45cfb539ebd5d
2026-05-07T16:54:49.837Z 2026-05-18 11:14:30 tth_v1_3ae0dcd0840beb04
2026-05-18T11:14:30.549Z — active — tth_v1_6bcbd0e241fa0a98

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/tangent-threads-from-masked-orbits-to-quantum-resonances 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.