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

IssuedSupersededContent hash
2026-09-17T10:32:35.902Z 2026-09-18 04:40:20 tth_v1_078a009b9f8f7b30
2026-09-18T04:40:22.806Z 2026-09-18 04:40:22 tth_v1_b40c5443f2470bde
2026-09-18T04:40:22.913Z 2026-09-18 04:45:43 tth_v1_b40c5443f2470bde
2026-09-18T04:45:43.715Z — active — tth_v1_b40c5443f2470bde

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/one-week-on-looking-back-at-the-wall 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.