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-05-06, updated 2026-05-18; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-05-06T15:10:15.532Z | 2026-05-06 15:15:58 | tth_v1_c78c3d3c5342778b |
| 2026-05-06T15:15:58.683Z | 2026-05-07 16:56:57 | tth_v1_c6786e7ffe10c520 |
| 2026-05-07T16:56:57.663Z | 2026-05-18 11:18:32 | tth_v1_856604d782ddf823 |
| 2026-05-18T11:18:32.520Z | — active — | tth_v1_3feebfd6a92b322a |
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-manipulation-was-coming-from-inside-the-article 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.