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-05-08, updated 2026-05-18; 3 revisions (this active certificate plus 2 prior).

IssuedSupersededContent hash
2026-05-08T16:32:39.426Z 2026-05-08 17:45:36 tth_v1_0e74ea57d8a4c43f
2026-05-08T17:45:36.678Z 2026-05-18 11:19:00 tth_v1_988a0b11cbaa2c86
2026-05-18T11:19:00.020Z — active — tth_v1_7abe41d9c5fd3cdb

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/a-special-interest 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.