Classical certificate analysis.
Your session is protected by a classical certificate because your client cannot yet verify a post-quantum one. That is a statement about the client, not about this server — and it has consequences worth reading. This is the complete report of the certificate you are actually using.
CLASSICAL AUTHENTICATION
Signature algorithm and key exchange are read from this session below.
01 · Certificate presented
Fields extracted from the served certificate chain (not from the user agent).
| Subject | … |
| Issuer | … |
| Key algorithm | … |
| Signature algorithm | … |
| Subject alternative names | … |
| Validity | … |
| Chain | … |
| Session key exchange | … |
| Cipher suite | … |
02 · What this protects — and what it does not
Today's adversary
A classical attacker cannot break this session. Confidentiality rests on the negotiated key exchange; with a hybrid group the session key already includes ML-KEM and is quantum-safe.
Authentication
The certificate is signed with ECDSA. A quantum computer running Shor's algorithm can forge that signature, so an attacker could impersonate this host to a client that still accepts it.
Harvest now, decrypt later
Traffic captured today and stored can be decrypted once a quantum computer exists — unless the session key was hybrid. That is why key exchange moves first and certificates move second.
Reference. ML-DSA and ML-KEM are specified in FIPS 204 and FIPS 203; X.509 encoding in RFC 9881.
03 · Install the post-quantum trust anchor
Needed to verify this service's ML-DSA certificate. Only for clients that support post-quantum cryptography.
Download CA certificate (.crt) PEM format
| Chrome / Edge / Brave | Settings → Privacy and security → Security → Manage certificates → Authorities → Import → select the .crt → enable "Trust for identifying websites". Then restart the browser. |
| Firefox | Settings → Privacy & Security → Certificates → View Certificates → Authorities → Import → tick "Trust this CA to identify websites". |
| macOS (Chrome / Safari) | Double-click the .crt → Keychain Access → System → trust "Always Trust". Note: Safari still will not verify ML-DSA certificates. |
| Windows | Double-click the .crt → Install Certificate → Local Machine → "Place all certificates in the following store" → Trusted Root Certification Authorities. |
| curl / OpenSSL 3.5+ | curl --cacert qdfs-pq-ca.pem https://qsotest.qdfs.io/ or openssl s_client -CAfile qdfs-pq-ca.pem … |
Not offered for Safari, iOS/iPadOS and unknown clients. They cannot verify an ML-DSA certificate and have no supervised path for a private root in this context, so installing an anchor would add risk without adding protection. Their hybrid key exchange still protects the session secret.
Why a private CA. No public certificate authority may yet issue ML-DSA certificates for TLS. Until the CA/Browser Forum permits it, the only honest option is a private post-quantum CA whose certificate you can inspect — which is exactly the file above.
04 · Known limits of this fallback
| Impersonation | Possible for a quantum-capable attacker (ECDSA signature). |
| Key exchange | Quantum-safe only if the negotiated group includes ML-KEM — check the handshake table on the test page. |
| Certificate size | ML-DSA certificates are ~30× larger than ECDSA; the post-quantum profile on this host is measured and published. |
| Browser trust | None of the mainstream browsers verify ML-DSA in TLS as of November 2026. |