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-01, updated 2026-05-18; 9 revisions (this active certificate plus 8 prior).

IssuedSupersededContent hash
2026-05-01T16:03:58.316Z 2026-05-02 08:18:20 tth_v1_9375015a8517ec02
2026-05-02T08:18:20.170Z 2026-05-03 08:34:20 tth_v1_9375015a8517ec02
2026-05-03T08:34:20.147Z 2026-05-05 01:54:51 tth_v1_9375015a8517ec02
2026-05-05T01:54:51.104Z 2026-05-05 02:38:23 tth_v1_9440ab6e825dd620
2026-05-05T02:38:23.665Z 2026-05-05 02:39:55 tth_v1_9440ab6e825dd620
2026-05-05T02:39:55.126Z 2026-05-06 14:17:55 tth_v1_9440ab6e825dd620
2026-05-06T14:17:55.570Z 2026-05-07 16:53:24 tth_v1_9440ab6e825dd620
2026-05-07T16:53:24.031Z 2026-05-18 11:12:03 tth_v1_b730b7d44d06ab72
2026-05-18T11:12:03.510Z — active — tth_v1_847f8bd8e3a5c1a3

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-miracle-and-the-pattern 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.