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-09-14, updated 2026-09-14; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-09-14T03:53:31.243Z | 2026-09-14 05:03:27 | tth_v1_db4b9bc1cda88658 |
| 2026-09-14T05:03:27.498Z | 2026-09-14 05:47:24 | tth_v1_a61e19b2d8155400 |
| 2026-09-14T05:47:24.356Z | 2026-09-14 06:09:36 | tth_v1_bcae3b7a5f1089e9 |
| 2026-09-14T06:09:36.652Z | — active — | tth_v1_bcae3b7a5f1089e9 |
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-protected-one 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.