Generating and reading the report.

Before you start

• Your credentials are for the people your organization designated for the pilot. Do not share them outside that group or leave them saved on third-party machines.
• Only analyze domains that belong to your organization or for which you have the holder's express authorization.
• Pilot accounts have a limited number of reports (credits). The counter appears at the top of the product page; reports that fail do not consume credit.

Generating a report

• Enter the organization's main domain (e.g. yourcompany.com, without https://) and click Generate report. Collection is passive (TLS, DNS, HTTP headers, and subdomains) and usually takes two to four minutes.
• Select the company's sector. It is what allows your result to be compared with the median of similar companies; with no selection, the sector is inferred from what the domain exposes.
• For a more precise diagnosis, answer the optional questions (declarative layer). None requires technical knowledge; when in doubt, choose the most likely option.

How to read the result

• The score ranges from 0 to 100 and estimates the organization's exposure to cryptography breakable by a quantum computer, in the harvest-now-decrypt-later scenario: data intercepted today, decrypted once a capable quantum computer exists. The higher the score, the greater the exposure; the signal coverage shown indicates how much of the expected evidence the collection was able to observe, and therefore how firm the estimate is.
• The sector comparison shows your position relative to your sector's median, measured over GWK's reference cohort — 80,182 organizations, all assessed by the same model and on the same scale as your domain.
• The risk factors list only the problems found on the assessed host, from the heaviest to the lightest. On each bar, the white tick marks how common that same problem is in the sector: near the end, almost every peer has it; near the start, few do.
• The executive PDF report carries the full reading: your position against sector peers, the breakdown of what weighs most in the index, the technical evidence observed on your domain (certificate issuer, cipher suites, DNS policies) and the actions split between short cycle and program. Generation takes a few minutes and runs in the background.

Exporting the data

• The download buttons deliver the complete evidence: bruto.jsonl carries the signals collected on the network and calculado.jsonl, the metrics that make up the score. The results are yours and can be used freely, including for your own audit.

Support

• Questions, access problems or exhausted credits: [email protected]. Use of the pilot is governed by the Pilot Terms.

Decisions it supports

The question changes by audience. The evidence doesn't.

Boards, security, risk, migration, and research teams ask different questions. The same quantitative structure answers each one; every card leads to the answer and the application behind it.

• Board and executives. I need to explain the risk without a cryptography lecture. See what reaches the board
• Security and infrastructure. I want to see the evidence behind the number. See CISO priorities
• Risk and compliance. Is my sector better or worse than average? Explore sector benchmarks
• Migration program. What does a migration program change in the result? See the PQC Readiness Track
• Research and audit. I want to review the method before relying on it. See the criterion and its provenance

Other IEQ products

The Sector Benchmark compares the result with sector aggregates. The PQC Readiness Track shows what a migration program changes in the score. The IEQ definition and the methodology explain how the index is built and where its limits are.

• Sector Benchmark
• PQC Readiness Track
• What IEQ is
• Methodology

Next steps

The sample report shows the same result screen on a fictitious domain. With an account, the product opens in the analysis area.