Skip to main content
The Truth Explorer is a public portal for inspecting the Truthlocks transparency log. Anyone can browse checkpoints, search by attestation ID or leaf hash, validate proof bundles offline, and view the issuer directory — no account required. Use it to independently verify that an attestation exists in the append-only Merkle tree, confirm checkpoint integrity, or audit issuer trust status.

​
Checkpoint timeline

The home page shows a live timeline of every checkpoint recorded in the transparency log. Each row displays:
ColumnDescription
CheckpointThe tree size at the time of the checkpoint, linking to its detail page
AgeHow long ago the checkpoint was signed
Root hashThe Merkle root hash (truncated, with copy-to-clipboard)
SignerThe key ID of the signer
StatusWhether the checkpoint carries a valid signature
Four summary cards at the top show the current tree size, log status, total checkpoints, and the age of the latest checkpoint.

​
Searching the log

Type an attestation ID or leaf hash into the search bar at the top of the timeline. The search auto-detects the query type:
  • Attestation ID — any non-hex string that identifies a specific attestation.
  • Leaf hash — a hex string (16+ characters) identifying a leaf in the Merkle tree.
When a match is found, you see the attestation ID, leaf index, event type, and a link to the corresponding checkpoint.

​
Checkpoint details

Click any checkpoint number to open a detail view. The page shows:
  • Tree size — number of leaves at this checkpoint.
  • Timestamp — when the checkpoint was recorded.
  • Merkle root hash — the full hex root hash with a copy button.
  • Signature — the Ed25519 signature (if signed).
  • Signer key ID — the key that signed the checkpoint.
  • Log ID — the unique identifier for this log instance.
Checkpoint details confirm log integrity without revealing individual attestation contents. The transparency log is an append-only structure — once a leaf is anchored, it cannot be modified or removed.

​
Validating proof bundles

The /validate page lets you verify a proof bundle entirely in your browser. No data is sent to any server.
1

Upload a proof bundle

Drag and drop (or click to select) a proof-bundle.json file. The maximum file size is 5 MB.
2

Review the four-step verification

The validator runs four checks automatically:
  1. JSON schema and content integrity — parses the bundle, verifies the bundle_hash_b64url integrity hash, and cross-checks attestation and log metadata.
  2. SHA-256 Merkle inclusion proof — recomputes the Merkle root from the leaf hash and audit path using the RFC 6962 algorithm, then compares it to the root hash in the checkpoint.
  3. Ed25519 checkpoint signature — verifies the checkpoint signature against the signing public key using the Web Crypto API.
  4. Network confirmation — fetches the live checkpoint from the transparency log API and compares root hashes.
3

Read the verdict

A pass/fail banner appears at the top, followed by a step-by-step checklist and summary cards showing the attestation ID, leaf index, and tree size.
Steps 1–3 run entirely offline using browser-native cryptography. Step 4 contacts the transparency log API to confirm the checkpoint is still live. If you are offline, the first three checks still provide strong integrity guarantees.

​
Issuer directory

The /issuers page lists every verified issuer in the Truthlocks trust registry. You can filter by name or issuer ID. Each entry shows:
  • Name and logo — with a verified badge for issuers at the “Official” verification tier.
  • Website — a link to the issuer’s public site.
  • Verification tier — “Official” or standard.
Click an issuer to view their full profile, including their issuer ID, verification tier, status, and when they were registered. Issuers with a private profile show a note that their signatures are valid but identity details are not public.

​
When to use Truth Explorer

ScenarioWhat to do
Verify a proof bundle someone shared with youGo to /validate and upload the proof-bundle.json file
Check whether a specific attestation is in the logSearch by attestation ID on the home page
Audit the log’s checkpoint historyBrowse the checkpoint timeline or click into a specific checkpoint
Look up an issuer’s trust statusOpen the /issuers directory and search by name or ID

Proof bundle specification

Schema and field reference for proof-bundle.json.

Content protection

How to protect content and generate proof bundles.