Verification steps

  1. Load ToneThread Root public key…
  2. Verify Tenant Site Certificate signature…
  3. Verify Post Certificate signature…
  4. Recompute ToneHash of post content…
  5. Compare recomputed hash to certificate…

Revision history

Originally published 2026-09-14, updated 2026-09-14; 4 revisions (this active certificate plus 3 prior).

IssuedSupersededContent hash
2026-09-14T03:53:32.599Z 2026-09-14 05:04:20 tth_v1_4f0496a4eb3d3e6c
2026-09-14T05:04:20.232Z 2026-09-14 05:48:19 tth_v1_310d933ea3ee1b9a
2026-09-14T05:48:19.124Z 2026-09-14 06:09:47 tth_v1_f99197e11e2357ba
2026-09-14T06:09:48.004Z — active — tth_v1_f99197e11e2357ba

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-morning-after 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.