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-13, updated 2026-06-27; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-05-13T09:46:24.100Z | 2026-05-13 09:47:45 | tth_v1_8b4f1897d868c7a6 |
| 2026-05-13T09:47:45.229Z | 2026-05-18 11:39:29 | tth_v1_8b4f1897d868c7a6 |
| 2026-05-18T11:39:29.017Z | 2026-06-27 04:43:58 | tth_v1_56ae5e338926ebb6 |
| 2026-06-27T04:43:58.090Z | — active — | tth_v1_ce05adb8065e60e1 |
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/three-and-six-for-the-same-question 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.