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-06-27, updated 2026-06-27; 4 revisions (this active certificate plus 3 prior).
| Issued | Superseded | Content hash |
|---|---|---|
| 2026-06-27T02:56:15.594Z | 2026-06-27 02:59:42 | tth_v1_98371391525def9e |
| 2026-06-27T02:59:42.546Z | 2026-06-27 03:01:06 | tth_v1_abcf0ab9b250472f |
| 2026-06-27T03:01:06.055Z | 2026-06-27 04:50:33 | tth_v1_8e1c90896002d8c5 |
| 2026-06-27T04:50:32.906Z | — active — | tth_v1_4c83b2ce7d56e7d7 |
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/new-in-prism-tone-invaders-iii-and-stillfield 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.