Verification steps
- Load ToneThread Root public key…
- Verify Tenant Site Certificate signature…
- Verify Post Certificate signature…
- Recompute ToneHash of post content…
- Compare recomputed hash to certificate…
Revision history
Originally published 2026-08-02, updated 2026-08-02; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-08-02T14:12:56.246Z | 2026-08-02 14:14:52 | tth_v1_880128435beb32e9 |
| 2026-08-02T14:14:52.258Z | 2026-08-02 18:44:50 | tth_v1_1f35e11932c6fa4d |
| 2026-08-02T18:44:50.557Z | 2026-08-02 18:46:17 | tth_v1_928bb3ca17aea508 |
| 2026-08-02T18:46:17.104Z | — active — | tth_v1_032f9c86690bc7c5 |
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/the-defect-was-in-the-description 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.