Lattiscan performs a real TLS 1.3 handshake against every internet-facing endpoint of your domain, checks whether it negotiates quantum-safe key exchange (ML-KEM hybrid), and gives you a board-level score, a fix list, and a CycloneDX inventory you can file as NIS2 evidence.
Encrypted traffic can be captured today and decrypted the day a cryptographically relevant quantum computer exists. Anything with a confidentiality life longer than a few years — contracts, payroll, patient data, VPN sessions — is already exposed on links that still use classical key exchange. Regulators have set the calendar:
First steps. The EU coordinated PQC roadmap expects every member state, and the organisations under it, to have a cryptographic inventory and a migration plan started by end of year.
High-risk migrated. Critical infrastructure — finance, telecom, energy, health, public sector and their suppliers — must be on quantum-resistant cryptography.
Everyone else. The transition should be complete for as many systems as feasible. NIS2 and Norway's Digitalsikkerhetsloven already require state-of-the-art, documented risk management today.
We enumerate your hostnames from DNS, Certificate Transparency logs and MX records: web, API, webmail, VPN gateways, identity portals, mail servers over STARTTLS.
Our scanner builds its own TLS 1.3 ClientHello offering X25519MLKEM768 and the other standard hybrids, then reads which group the server actually selects. It tells "supported" from "preferred" and flags TLS 1.2-only endpoints.
Mail, VPN and login endpoints weigh three times a marketing site. You get an A–F grade, prioritised remediation with vendor-specific steps, and a CycloneDX 1.6 cryptographic bill of materials for your auditor.
| Endpoint | Role | Key exchange | Action |
|---|---|---|---|
| vpn.acme.no | VPN | no TLS 1.3 | Upgrade gateway firmware; TLS 1.3 is the prerequisite for any PQ key exchange. |
| mail.acme.no | x25519 | Postfix 3.9 on OpenSSL 3.5 enables ML-KEM hybrid by default. | |
| login.acme.no | Identity | ML-KEM, not preferred | Reorder group preference so the hybrid wins whenever a client offers it. |
| www.acme.no | Web | X25519MLKEM768 | Done — served through a PQ-enabled CDN. |
Run the scan across every client tenant, hand each of them a white-labelled grade, and turn "post-quantum" from a scary word into a billable migration project you lead. Regression alerts tell you when a client's change broke the score.
You are being asked about PQC in security questionnaires, cyber-insurance renewals and NIS2 supplier reviews. Answer with a dated, reproducible inventory instead of a paragraph — and re-scan monthly so the evidence stays current.
Prices excl. VAT. Annual billing: two months free. Public-sector and non-profit discount on request.
No. Lattiscan only performs the opening of a TLS handshake, exactly like a browser. Nothing is exploited, nothing is logged in, and the load is a few kilobytes per endpoint.
No. No public CA issues post-quantum (ML-DSA) certificates yet, so certificates are reported as information, not scored. Recorded traffic is protected by key exchange, and that is what we grade.
They check one hostname once. Lattiscan finds all your endpoints including mail and VPN, weighs them by risk, tracks the score over time, alerts on regressions, and exports the inventory auditors ask for.
The current product covers the external perimeter. SSH (mlkem768x25519-sha256) and VPN tunnel checks are next on the roadmap; internal library scanning follows with an on-premise agent.
Scan results are stored on servers in the EU/EEA. We never store your traffic — there is none to store.
Usually yes, for free: putting an endpoint behind a PQ-enabled CDN or upgrading to OpenSSL 3.5, nginx 1.27, Caddy 2.9 or Windows Server 2025 enables the hybrid by default. The report tells you which.
Leave your domain and e-mail. You receive a full report within 24 hours; early-access customers keep the launch price for 12 months.