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-30, updated 2026-06-01; 3 revisions (this active certificate plus 2 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-05-30T05:31:20.385Z | 2026-06-01 16:47:46 | tth_v1_95ec467347974410 |
| 2026-06-01T16:47:46.838Z | 2026-06-01 16:48:26 | tth_v1_cc8f719d68b4f346 |
| 2026-06-01T16:48:26.915Z | — active — | tth_v1_7c6f08af6a70cdc4 |
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/have-we-always-been-getting-dumber- 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.