Nautiq PQC compatibility demo

A modern or post-quantum client talking to a genuinely old HTTPS application.

Client → Nautiq → legacy Node.js

Frontend: automatic selection among qsc, hybrid, default and legacy profiles, based on the new connection’s ClientHello.

Origin: Node.js 0.12.18 / OpenSSL 1.0.1u, constrained to TLS 1.2 with ECDHE-ECDSA-AES128-GCM-SHA256. Nautiq verifies its private CA and server name.

Inspect the origin’s runtime and cipher · Download the demo PQ CA

The origin does not know your frontend tier. Verify it using your TLS client and Nautiq’s native evidence. Node 0.12 lacks an actual negotiated-protocol reporting API; a configured version is not substituted for that observation.

Not end-to-end quantum-safe. The backend remains classical TLS. PQ profiles use a separate ML-DSA lab CA that controlled test clients must explicitly trust. Ordinary classical-authentication profiles use a public ECDSA certificate.

Developer demonstration only. The intentionally EOL application has no credentials, database or sensitive data and is isolated from outbound networks. Do not submit personal information. This is not production, FIPS, or end-to-end PQ qualification.