How quantum-ready is your public-facing cryptography?

Tell us which website to check. Quantizant connects to it, inspects the TLS handshake, certificates and keys it presents, and rates each one against a future quantum attacker. Takes about 30 seconds.

About you

Who the report is prepared for.

Full name *

Enter your name.

Work email *

Enter a valid email address, e.g. name@company.com.

Organisation *

Enter your organisation.

Designation

What to scan

A public website or API endpoint that speaks TLS.

Website URL or hostname *

Enter a public hostname, e.g. www.example.com.

Ports Optional. Up to 5, comma separated, e.g. 443, 8443. Defaults to 443.

We run one external TLS scan: protocol versions, cipher suites, key-exchange groups (including hybrid ML-KEM support) and the full certificate chain. Nothing is installed and no credentials are needed.

I confirm I am authorised to request a scan of this host on behalf of my organisation, and agree that my details are stored so the Quantizant team can contact me about the results.Please confirm before running the scan.

Scanning…

Quantizant is connecting to your host and cataloguing every algorithm, key and certificate it presents. This usually takes 20–60 seconds.

Preparing scan

Quantum readiness report

scanned

Prepared for
Designation
Organisation
Email
Scan date
Modality: network · TLS

0%quantum safe

Total assets0

Quantum safe0

Quantum-vulnerable0

Needs action0

Quantum risk

Vulnerable: broken by a large quantum computer (Shor's algorithm). Partial: not broken outright, but needs a change (e.g. larger keys, a newer protocol version or hybrid key exchange) to be quantum-safe. Hybrid: classical plus post-quantum key exchange, counted as safe.

By asset type

What we found

Asset	Used for	Severity	Quantum risk	Recommended replacement

Suggested migration path

based on this scan

Scan not completed