Every result comes from three layers of evidence, from a quick capability check to cryptographic proof. This page explains each test, how sites are graded, how the India study is run, and what a scan cannot see.
A scan opens about 15 short connections to the site. Each is an ordinary encrypted handshake, the same opening exchange a browser makes before loading a page. No pages, logins or forms are touched.
We test seven key-exchange methods one at a time: the hybrid X25519MLKEM768 (used by Chrome, Firefox and Cloudflare), two other standard hybrids, two pure ML-KEM methods, the obsolete pre-standard Kyber draft, and classical x25519 as a baseline. For each, we offer the server only that method with no key data. Under TLS 1.3 rules a server that supports it must reply asking for a key of that type; one that does not, refuses.
For every server that passes Layer 1 we perform a real exchange:
The decryption uses authenticated encryption (AES-GCM), which only succeeds if both sides calculated exactly the same secret. A server cannot pass by merely claiming support. Our test suite confirms the check fails when the secret is deliberately corrupted.
We offer exactly what Chrome offers, post-quantum and classical together, and record which one the server picks. A server that can do post-quantum but chooses the classical option leaves its real visitors unprotected, even though Layers 1 and 2 pass.
We also record whether TLS 1.3 (required for post-quantum) is supported, whether obsolete TLS 1.0 and 1.1 are still enabled, and whether the certificate is trusted, strong enough and not about to expire.
One normal web request lets us read the response headers, which usually reveal what serves the site (Cloudflare, Akamai, AWS, Google Cloud, Azure, nginx, Apache, IIS and others). That decides which step-by-step fix plan the site owner sees.
| Check | Points |
|---|---|
| Post-quantum proven with a real handshake (Layer 2) | 30 |
| Real visitors get it (Layer 3) | 10 |
| TLS 1.3 supported | 20 |
| TLS 1.0 and 1.1 switched off | 10 |
| Certificate trusted | 10 |
| Certificate key strong enough | 10 |
| Certificate valid for 14 or more days | 10 |
A is 90 or more, B 75, C 60, D 40, F below. Two rules are stricter than the points: a server that claims post-quantum support but fails the real handshake is treated as not protected, and a server that gives real visitors the classical option cannot receive an A.
.gov.in and .nic.in are government; .ac.in, .edu.in and .res.in are education), by the hand-checked list, or by keywords in its name (for example "bank", "hospital", "news"). Sites that match no sector are grouped as Business & other. Each sector has a fixed share of the list, so no single sector dominates..gov.in, .nic.in and .ac.in domains), because name keywords alone sometimes misfile a site, for example a job portal whose name contains "times". All other sites are shown together in one row, "Other sites (sector not confirmed)", so the sector table adds up to the national total.tls-v1-2.badssl.com:1012) fails.