Every other post-quantum checker answers one question about one host: does it speak ML-KEM. This one runs eight steps against every hop a transaction actually traverses, separates the two clocks that PQ migration runs on, and fails closed at the exact step. Posture is not inherited: a quantum-safe front door in front of a classical hop is classical end to end. Verification runs entirely in your browser — the handshakes happen in a local probe, this page only verifies and renders the receipt. The one exception is the optional live scan, which sends the hostname you type to this site and performs the handshakes there.
Produce one with pqprobe -chain chain.json -out receipt.json.
The probe opens the TLS connections; this page never does. Verification is Ed25519 over the
canonical receipt body, in WebCrypto, in this tab.
Hostname only — no scheme, no path, no IP addresses. Port 443. One scan is roughly fifteen outbound handshakes, so the endpoint is rate limited and results take a few seconds. Unlike the other two tabs, this one does send the hostname to this server, which performs the handshakes on your behalf. Live results are returned unsigned; only curated chains are signed.
Confidentiality is retroactive. Traffic recorded today under a classical key agreement is decryptable the day a cryptographically relevant quantum computer exists. The exposure window opened the moment the data crossed the wire. Key agreement is therefore urgent now, and the deadline is set by how long your data stays sensitive — not by Q-Day.
Authentication is not retroactive. Forging a signature requires a quantum computer at the moment of the attack. A classical certificate chain is not a harvest risk. It is a cliff: it must be migrated before Q-Day, not before your data ages out. Tools that collapse these into one score mislead in both directions — they panic about certificates and under-price the KEM.
Step 08 is the Mosca inequality, wired to live measurements rather than a questionnaire:
if shelf-life + migration-time > time-to-Q-Day
and step 04 did not negotiate a hybrid group, the exposure has already started and no future
remediation closes it.
Pick a fault and watch the engine stop at the step that catches it. The same eight steps run whether the endpoint is a VASP settlement rail or an agent's tool endpoint — the check does not care who holds the connection, only what the handshake proves.
Withholds capabilities from the client side, one rung at a time, and records the worst handshake this hop will still complete. Nothing is intercepted or injected — each rung is an ordinary outbound connection with a restricted ClientHello, which is the only thing a client can measure.