Rosetta Q-Ready · live measurement · QEX-1.0
Your cryptographic exposure, measured today.
Enter your domain once. From outside, we measure everything a third party can see: your website, your email, your sensitive servers and your certificate. Then we show you what it means and why it matters now.
Quantum Console
- Surface
- Endpoints
- Edge
- Certificate
- Waiting for a domain. Every query and every TLS handshake will appear here, with its timing.
1 · The data
What you have today
Each channel your data travels over, measured separately. A channel we could not measure says “not measured”, never “not protected”.
Your report for your domain is ready. Download it now or get it by email.
Download my reportYour QEX today
—/ 100
Your public surface
Sensitive endpoints
| Name | Class | DNS | Port 443 | Detail |
|---|
Your edge and the post-quantum key exchange
| TLS handshake | What we offered | What your edge chose | ms |
|---|
Your certificate
Email and reporting channel
| Item | What there was | What there is | Status |
|---|
2 · The consequence
What someone can store today
“Harvest now, decrypt later”: traffic encrypted with classical methods can be copied today and read once a sufficiently capable quantum computer exists. This is a real capture, taken by us, of what it looks like.
Capsule A · classical channel
opens in the futureloading the capture…
Capsule B · hybrid channel
stays closedThe same message, encrypted with X25519MLKEM768. Copying it today is useless: the post-quantum part resists the quantum computer.
3 · The mechanism
Why it matters now
The capsule is opened with Shor’s algorithm. It is not theory: here it runs, at small scale.
Shor finds the period and breaks the key
The risk window is the lifetime of your data
If a piece of data must stay secret beyond the day that machine exists, the risk has already started today. No date is a guaranteed deadline; 2030 is NIST’s firm date.
✓ · The proof
Your snapshot of today, sealed
Everything above is kept in a snapshot with its hash. Your next measurement is compared against this one, item by item.
Today’s snapshot
Everything measured, in one file with its hash. It is the baseline for comparing the next measurement: changing a single character changes the hash.
- Measured
- sha256 hash
- Integrity
- —
What we measure and what we don’t
Surface. We query the public certificate log (crt.sh) and classify each name with the same rules as every edition of the index: non-production environments, legacy, sensitive infrastructure and critical services.
Endpoints. For each sensitive name we ask DNS whether it is still published and, if it is, we send a single TLS handshake to port 443. We complete no connection and send no data.
Edge and certificate. Three TLS 1.3 handshakes decide whether your edge supports and chooses the hybrid key exchange; a TLS 1.2 handshake shows us the certificate, which travels unencrypted in that version.
HNDL posture. Not measured: it is a value for your sector (how many years the data must stay protected and how long migration takes). We label it as a model.
What cannot be seen from outside. The leg from your edge to your origin server, your HSMs, your internal cryptography and your providers’. That is why the index is capped at 84: no external measurement can claim an organization is ready.