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-08, updated 2026-05-18; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-05-08T12:22:23.579Z | 2026-05-08 12:30:32 | tth_v1_70ebfc24b891ca8b |
| 2026-05-08T12:30:32.986Z | 2026-05-08 12:58:00 | tth_v1_522a9181968a8eda |
| 2026-05-08T12:58:00.492Z | 2026-05-18 11:27:48 | tth_v1_1eed5287caf8f1ae |
| 2026-05-18T11:27:48.020Z | — active — | tth_v1_6b9ee6435d1f5a36 |
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-word-that-arrived-with-weight 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.