FIPS 203
ML-KEM
Key encapsulation. The public scan awards full marks for a negotiated X25519MLKEM768 hybrid on TLS 1.3 — the FIPS 203 parameter set browsers actually speak.
Methodology
The public scan grade is arithmetic over a fixed table of weights — no judgement call, no language model. Each dimension is scored from what an external, passive observation can see; a dimension the scan could not measure is left out of the calculation rather than counted as a failure. The weights are versioned: a scan keeps the version it was graded under, so a later change never silently rewrites an old result.
Weights version: v2 · verified 2026-09-09
NIST standards
FIPS 203
Key encapsulation. The public scan awards full marks for a negotiated X25519MLKEM768 hybrid on TLS 1.3 — the FIPS 203 parameter set browsers actually speak.
FIPS 204
Digital signatures. The paid audit maps each signing finding to an ML-DSA parameter set (FIPS 204) rather than a generic 'use PQC' recommendation.
FIPS 205
Stateless hash-based signatures. The conservative backup when a lattice signature is not acceptable — FIPS 205, cited per finding in the report.
| Component | Weight | What earns the points |
|---|---|---|
| Post-quantum key exchange | 30 | A negotiated ML-KEM hybrid group on TLS 1.3 earns full marks; TLS 1.3 with a classical-only key exchange earns a third; no TLS 1.3 earns none. If the probe could not run, the dimension is excluded, not zeroed. |
| TLS protocol versions | 15 | SSLv2, SSLv3, TLS 1.0 and 1.1 disabled, TLS 1.3 present. Offering SSLv2 caps the grade at F and SSLv3 at D; TLS 1.0 caps it at C; missing TLS 1.3 caps it at B. |
| Cipher suites | 15 | No RC4, 3DES, EXPORT or NULL suites; forward secrecy on TLS 1.2; no known TLS-stack vulnerability such as ROBOT or Heartbleed. |
| Certificate | 15 | RSA >= 2048 or ECDSA P-256+, signature SHA-256 or stronger, complete chain, not self-signed, more than 14 days to expiry. An expired certificate forces grade F. |
| Security headers | 10 | HSTS with max-age of at least six months, Content-Security-Policy, X-Content-Type-Options and Referrer-Policy present. |
| Certificate surface | 10 | Certificate Transparency breadth: a wildcard certificate is flagged for review. Confirming that every subdomain still resolves is the paid audit's job, not an anonymous scan's, so this dimension scores what CT alone can prove. |
| Data sensitivity lifetime | 5 | How long your data must stay confidential — the driver of migration urgency. It cannot be seen from outside, so a public scan excludes it rather than guessing. |
| Condition | Grade cannot exceed | Why |
|---|---|---|
| Certificate expired | F | An expired certificate breaks the trust anchor for every other measurement, so nothing else can raise the grade. |
| SSL 2.0 enabled | F | SSL 2.0 is prohibited (RFC 6176) and enables the DROWN attack, which can decrypt even modern TLS sessions sharing the key; offering it forces grade F. |
| SSL 3.0 enabled | D | SSL 3.0 is deprecated (RFC 7568) and broken by POODLE, which recovers plaintext from the connection; offering it caps the grade at D — worse than TLS 1.0. |
| TLS 1.0 enabled | C | TLS 1.0 is formally withdrawn (RFC 8996); offering it is a material weakness regardless of the rest. |
| TLS 1.3 not offered | B | Without TLS 1.3 there is no path to a post-quantum hybrid key exchange, so an otherwise-clean host cannot reach an A. |
| PQC handshake not verified | B | When the scan could not verify the post-quantum handshake, the grade is held below A: the headline claim must never rest on something we did not observe. |
| Pre-standard Kyber draft | B | A pre-standard Kyber draft hybrid is real protection, but not the finalised standard (ML-KEM, FIPS 203). The grade is held at B until the host moves to X25519MLKEM768. |
| Grade | Score |
|---|---|
| A | 85–100 |
| B | 70–84 |
| C | 55–69 |
| D | 40–54 |
| F | 0–39 |
This is an external, passive assessment of one hostname: a TLS 1.3 handshake on port 443, Certificate Transparency logs and HTTP response headers. It does not scan ports, it does not fingerprint service versions against a vulnerability feed, and it does not reach inside your network, your application code or your email. It is an assessment, not a certification, and no regulator accepts it on our say-so. The deeper work — the full estate, internal systems and a migration plan — is the paid audit.
One passive handshake. The same weights published on this page. No payload, no account.
Scan a domain — free