Ingest a certificate (read-only parse)
Paste a PEM/DER certificate or load a bundled sample. The parser walks the DER just far enough to surface every AlgorithmIdentifier OID, maps it to a known type, and extracts key parameters - no private keys, no generation. Recognizes classical (RSA, DSA, ECDSA, EdDSA), PQC (ML-DSA, ML-KEM, SLH-DSA, Falcon), and hybrid/composite OIDs.
Or pick any type from the catalog
Every taxonomy entry the tool parses/analyzes. Classical = red edge, PQC = green, hybrid = purple.
Generate an identity (Qrypto Trust / ZAP)
Producing quantum-safe keypairs, sealing, and the branded entropy/hardness report is the proprietary value. Badges are honest: SHIPPED TODAY = wired in the ZAP stack now (ML-DSA, ML-KEM); ROADMAP = selected but not yet built (SLH-DSA, Falcon, composite) - previewed, never implied as shipped. ML-KEM is a KEM (key-establishment), never presented as a signature scheme.
ML-DSA-65
Metadata & key parameters
Vulnerability & posture
Standards checklist
Compare across six axes
Drop an ingested classical cert next to our PQC baseline. The classical side lights axis 3 (quantum vulnerability) and axis 5 (deprecation) red; ML-DSA-65 stays green. This is the proof.
Green = quantum-safe / standards-forward; red = quantum-broken / deprecated. The comparison reads only the parsed cert; nothing is fabricated.
Standards conformance matrix
Machine-checkable grid: rows = standards, columns = cert type. * marks a cell with an accuracy note (hover). Note the honest partials: CNSA 2.0 is ~ for ML-DSA-65 / ML-KEM-768 (NSS needs category-5, i.e. ML-DSA-87 / ML-KEM-1024) - not "meets". Falcon carries a draft (FIPS 206) flag; composite shows partial on each single-algorithm FIPS row.
Qrypto Trust