@quantakrypto/qprobe

@quantakrypto/qprobe

Actively inspect live TLS/SSH endpoints you own for post-quantum readiness — whether they negotiate a PQC-hybrid key exchange, and what their classical exposure is — with zero runtime dependencies (Node built-ins only).

qProbe is the live-endpoint sibling of qScan (which scans code) and the infrastructure detectors in @quantakrypto/core (which scan config). It is the only package in this repo that opens network connections, and it is gated behind a mandatory ownership attestation — read THREAT-MODEL.md before using it.

Authorization required. qProbe sends nothing until you attest you are authorized to test the target. Active probing of endpoints you do not own may be unlawful. qProbe refuses CIDR blocks, IP ranges, wildcards, and target lists — it probes one host you operate at a time, and it only ever performs a benign, unauthenticated handshake. It reports the negotiated reality; it never modifies an endpoint ("engine disposes").

What it checks

• TLS — the negotiated TLS version, cipher suite, ephemeral key-exchange group, and leaf-certificate key type, plus whether the server supports the post-quantum hybrid group X25519MLKEM768 (codepoint 0x11EC). Because Node's bundled OpenSSL cannot negotiate that group, qProbe detects it with a hand-rolled raw ClientHello and reads the group the server selects.
• SSH — the offered key-exchange and host-key algorithms (from the cleartext KEXINIT), flagging classical-only servers and surfacing PQC KEX ([e-mail], mlkem768x25519-sha256) as a positive.

Findings are @quantakrypto/core Findings, so they score (readinessScore) and read exactly like qScan output and can be merged into the same posture.

Usage

# TLS 443: hybrid KEX + certificate posture (endpoint you control)
npx @quantakrypto/qprobe --i-own-this example.com

# SSH 22: KEXINIT algorithms
npx @quantakrypto/qprobe --ssh --i-own-this git.example.com

# Multiple endpoints from an ownership manifest, JSON output
npx @quantakrypto/qprobe --owned-hosts hosts.txt api.example.com:8443 --json

Options

Flag	Meaning
--i-own-this	Attest you are authorized to probe the target(s). Required (or --owned-hosts).
--owned-hosts <file>	Ownership manifest (one host per line, # comments). Every target must be listed.
--tls / --ssh / --smtp / --imap / --pop3 / --postgres	Force a probe mode. Default: auto by well-known port — SSH :22, SMTP STARTTLS :25/:587, IMAP STARTTLS :143, POP3 STLS :110, PostgreSQL SSLRequest :5432, else direct TLS (which covers HTTPS :443, IMAPS :993, and DNS-over-TLS :853).
--servername <name>	TLS SNI server name (default: the host; omitted for bare IPs).
--timeout <ms>	Per-connection timeout (default: 8000).
--format <human|json|sarif|cbom>	Output format (default: human). --json / --sarif / --cbom are aliases. SARIF 2.1.0 and CycloneDX 1.6 CBOM are the same formats qScan emits.

Exit codes mirror qScan: 0 clean, 1 findings, 2 error / not authorized.

Example

$ qprobe --i-own-this example.com

example.com:443  [tls]
  TLSv1.3 · TLS_AES_256_GCM_SHA384 · KEX X25519 · cert EC(prime256v1)-256
  PQC-hybrid (X25519MLKEM768): not negotiated
  [medium] Classical TLS key exchange (no PQC hybrid) — the session key is
           harvest-now-decrypt-later exposed …
  [low]    Classical certificate key — forgeable once a CRQC exists …

2 findings · 1 HNDL-exposed · readiness 90/100

One post-quantum posture: code + infra + live endpoints

qProbe findings are @quantakrypto/core Findings and emit the same SARIF 2.1.0 and CycloneDX 1.6 CBOM as qScan. That means the three planes compose into a single readiness picture:

• Code + infrastructure-as-code / config — qscan . (the language packs and the Terraform / Kubernetes / CI-CD / secrets / messaging / database / JOSE detectors all run in one scan).
• Live endpoints — qprobe --i-own-this ….

Because both CBOMs are CycloneDX 1.6 cryptographic-asset documents, they merge into one org-wide crypto bill of materials, and each readiness score comes from the same buildInventory math so they read on the same scale:

qscan .  --cbom  -o code-infra.cbom.json          # code + infra crypto assets
qprobe --owned-hosts hosts.txt api.example.com --cbom -o endpoints.cbom.json

Combine them into one CBOM with mergeCboms from @quantakrypto/core (components with the same bom-ref collapse to one asset whose evidence spans both planes):

import { mergeCboms } from "@quantakrypto/core";
import { readFileSync } from "node:fs";
const combined = mergeCboms([
  JSON.parse(readFileSync("code-infra.cbom.json", "utf8")),
  JSON.parse(readFileSync("endpoints.cbom.json", "utf8")),
]);

License

Apache-2.0. See THREAT-MODEL.md for the authorization model.