Ledger Horizon Standards Agent Export Settings Star on GitHub

Loading the assay ledger

Keyassay

Know the year your TLS stops being secret.

An assay is an engineering measurement of public key material, not an audit.

Product

Assay ledger
Horizon dial
Cost model
Agent console
Export centre
Verify a seal
Settings

Live surfaces

Health check
Tool catalogue
MCP manifest
aniruddhaadak80/keyassay

Sources

Live TLS handshake, performed by this server against the host you name.
Certificate Transparency records via crt.sh.
Citation metadata via arXiv.

Keyassay · 2026 · MIT licensed

Star on GitHub

Safety and honest limits. Keyassay reports what can be measured from a public TLS handshake and published cost estimates. Break years are outputs of a stated growth assumption, not predictions, and a certificate says nothing about implementation bugs, traffic analysis or operational security. It is not a penetration test, an audit opinion or a compliance attestation. Verify independently before acting on it.

Integrity

Verify a seal

Every mutation appends to a per-assay hash chain. Replaying it recomputes each digest from scratch and reports the first link that no longer holds.

Ledger integrity

0 / 0

No assays to replay

genesis keyassay/genesis/1 · seal(n) = SHA-384(UTF-8(prevSeal) || canonicalJson(event(n))) · canonical JSON sorts object keys recursively and preserves array order, because array order is part of the data.

Assay id to replay

Replays the chain from the stored events and recomputes every digest. Finds an id in the ledger.

Every chain in this session

No assays yet, so there is nothing to replay. Run one and it appears here.

Why a stored grade can be trusted

A score on its own is an assertion. What makes this one checkable is that every event is hashed together with the seal that preceded it, so altering any earlier event invalidates every later digest in the chain. Removing an event does not help either: the following event's recorded prevSeal no longer matches the computed head.

Deleting an assay does not erase this. A delete appends its own event and tombstones the row, so a verification of a record you can no longer see in the ledger still succeeds. That is deliberate: an auditor who asks about an assay six months later should not find that the evidence vanished with the row.