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

IssuedSupersededContent hash
2026-09-23T17:02:47.818Z 2026-09-23 17:04:25 tth_v1_168a1091880887c2
2026-09-23T17:04:25.157Z 2026-09-23 17:06:19 tth_v1_168a1091880887c2
2026-09-23T17:06:19.640Z 2026-09-23 17:09:24 tth_v1_168a1091880887c2
2026-09-23T17:09:24.802Z — active — tth_v1_168a1091880887c2

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/fourteen-songs-fifty-years-one-verifiable-record 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.