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-08T14:03:22.637Z | 2026-05-08 14:04:02 | tth_v1_123bec8b51cd8338 |
| 2026-05-08T14:04:02.463Z | 2026-05-08 14:04:07 | tth_v1_123bec8b51cd8338 |
| 2026-05-08T14:04:07.777Z | 2026-05-18 11:28:15 | tth_v1_123bec8b51cd8338 |
| 2026-05-18T11:28:15.216Z | — active — | tth_v1_2c856a2c283fb82c |
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/what-a-signed-blog-post-doesnt-tell-you 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.