LatticeScan

Index

Are the quantum companies quantum-safe?

The companies below are building the machines that will one day break today’s encryption. So we scanned every public server they run for the defence against exactly that: post-quantum key exchange. The result is its own kind of answer. Of 259 servers at 14 companies, 167 have it. 1 of 14 companies protect every server.

GradeCompanyPost-quantum serversFix first
A
ionq.com
38/38
0Follow
B
xanadu.ai
1 server without post-quantum key exchange
  • codebook-grader.xanadu.ai
16/17
0Follow
B
atom-computing.com
1 server without post-quantum key exchange
  • staging.atom-computing.com
7/8
0Follow
B
quantinuum.com
7 servers without post-quantum key exchange
  • hello.quantinuum.com
  • hqapi.quantinuum.com
  • hqsapi.quantinuum.com
  • qapi.quantinuum.com
  • qrng.poc.quantinuum.com
  • sg-grandchallenge.quantinuum.com
  • vpn.quantinuum.com
20/27
1Follow
B
quera.com
4 servers without post-quantum key exchange
  • corpvpn.quera.com
  • forum.quera.com
  • link.quera.com
  • ukvpn.quera.com
10/14
0Follow
B
alice-bob.com
4 servers without post-quantum key exchange
  • alice-bob.com
  • les-houches-ftqc-workshop.alice-bob.com
  • staging3.alice-bob.com
  • www.alice-bob.com
6/10
0Follow
B
infleqtion.com
4 servers without post-quantum key exchange
  • ir.infleqtion.com
  • oqtant-docs-dev.infleqtion.com
  • oqtant-docs.infleqtion.com
  • vpn.infleqtion.com
6/10
1Follow
B
oxfordquantumcircuits.com
2 servers without post-quantum key exchange
  • oxfordquantumcircuits.com
  • www.oxfordquantumcircuits.com
3/5
0Follow
B
psiquantum.com
11 servers without post-quantum key exchange
  • circuits.psiquantum.com
  • construct.psiquantum.com
  • dev.alerts.psiquantum.com
  • git.construct.psiquantum.com
  • git.staging.construct.psiquantum.com
  • griffithlab.psiquantum.com
  • merch.psiquantum.com
  • open-docs.construct.psiquantum.com
  • opsgenie.alerts.psiquantum.com
  • staging.circuits.psiquantum.com
  • staging.construct.psiquantum.com
17/28
0Follow
B
dwavesys.com
12 servers without post-quantum key exchange
  • cloud.dwavesys.com
  • configdb-stage.dwavesys.com
  • configdb.dwavesys.com
  • confluence.dwavesys.com
  • docs.dwavesys.com
  • docs.ocean.dwavesys.com
  • dwavesys.com
  • eu-central-1.cloud.dwavesys.com
  • jira.dwavesys.com
  • na-east-1.cloud.dwavesys.com
  • na-west-1.cloud.dwavesys.com
  • www.dwavesys.com
15/27
0Follow
B
quantumcomputinginc.com
6 servers without post-quantum key exchange
  • careers.quantumcomputinginc.com
  • qatalyst.quantumcomputinginc.com
  • qrng.quantumcomputinginc.com
  • quantumcomputinginc.com
  • showcase.quantumcomputinginc.com
  • www.quantumcomputinginc.com
6/12
0Follow
C
pasqal.com
13 servers without post-quantum key exchange
  • api.pasqal.com
  • click.comm.pasqal.com
  • comm.pasqal.com
  • community.pasqal.com
  • docs.pasqal.com
  • eye.comm.pasqal.com
  • img.comm.pasqal.com
  • insights.pasqal.com
  • login.pasqal.com
  • n8n-workflow.pasqal.com
  • nexus.pasqal.com
  • pasqal.com
  • www.pasqal.com
10/23
2Follow
C
meetiqm.com
5 servers without post-quantum key exchange
  • academy.meetiqm.com
  • docs.meetiqm.com
  • meetiqm.com
  • support.meetiqm.com
  • www.meetiqm.com
3/8
0Follow
C
rigetti.com
22 servers without post-quantum key exchange
  • api.dev.qcs.rigetti.com
  • api.frc.outpost.rigetti.com
  • api.lab.outpost.rigetti.com
  • api.lakeshore.outpost.rigetti.com
  • api.production.qcs.rigetti.com
  • api.qcs.rigetti.com
  • api.staging.qcs.rigetti.com
  • auth.qa.qcs.rigetti.com
  • auth.qcs.rigetti.com
  • auth.staging.qcs.rigetti.com
  • docs.infra.rigetti.com
  • grpc.qcs.rigetti.com
  • jamf.rigetti.com
  • netbox.infra.rigetti.com
  • op-scim-bridge.it.rigetti.com
  • qcs.rigetti.com
  • rigetti.com
  • staging.qcs.rigetti.com
  • time.rigetti.com
  • vpn.rigetti.com
  • www-dev.rigetti.com
  • www.rigetti.com
10/32
7Follow

What was checked. Every hostname each company has a public certificate for, taken from Certificate Transparency logs, plus common service names under the domain and under every wildcard certificate, kept only where the name resolves to a public address, then tested with post-quantum-only TLS 1.3 handshakes. A server that completes one supports hybrid ML-KEM key exchange, the protection against harvest now, decrypt later. Highlighted names are production login, API, VPN, payment and developer hosts: the ones to fix first. A hostname shows what a server is called, not what traffic it carries, and this is the outside view only.

Scanned between November 10, 2026 and November 10, 2026. Every company is re-scanned weekly on the same schedule as Fleet Watch customers. Method: how grades are produced. Press Follow on any row to be emailed when its grade changes.

Often the classical servers are not the quantum hardware or the cloud API. They are the careers site, the marketing host or a partner portal, which is exactly the kind of gap an outside scan surfaces and an inside inventory misses.

Want the same read on your own domain, or on your suppliers? Fleet Watch runs this scan privately every week, with an alert when anything gets worse and a report your auditor can verify. The first scan is free.

Scan your own domain