# Is your website ready for post-quantum? Check it in a minute

In the [last post](https://pqc.hashnode.dev/harvest-now-decrypt-later) we looked at "harvest now, decrypt later": encrypted traffic recorded today can be read once quantum computers are big enough. The first practical question that follows is simple. **Is the connection to my website already protected against that?**

The padlock in a normal browser won't tell you. It shows that the connection is encrypted, not whether that encryption would hold up against a quantum computer. And because post-quantum protection only works when both sides support it, a connection can quietly fall back to the old method without anyone noticing.

Here's how to see it, in three steps.

## What "ready" means

A secure web connection does two jobs, and each can be post-quantum or not:

- **The key exchange** agrees on the secret keys for the session. If it's post-quantum (usually "hybrid": a classical and a post-quantum method together), recorded traffic can't be decrypted later. This is the part that matters for "harvest now, decrypt later".
- **The certificate** proves the site is who it says it is. If it's post-quantum too, the site's identity can't be forged with a quantum computer either.

That gives three levels:

| Level | Key exchange | Certificate | What it means |
|---|---|---|---|
| **Quantum-safe** | post-quantum | post-quantum | Recorded traffic stays private, and the identity can't be forged. Every .pqc site is at this level. |
| **Quantum-safe encryption** | post-quantum (hybrid) | classical | Recorded traffic can't be decrypted later; the identity check is still classical. |
| **Not quantum-safe** | classical | classical | Traffic recorded today could be decrypted once large quantum computers exist. |

For an ordinary website, "Quantum-safe encryption" is the level to aim for first, because it closes the "harvest now" gap.

## Step 1: Check any site you visit

Open the site in [PQC NOW Browser](https://pqcnow.com/downloads). On desktop, the address bar shows a label next to the address: **Quantum-safe** or **Quantum-safe encryption** in green, or **Not quantum-safe** in amber.

The label comes from the connection the browser actually made, not from a database, so it's what your visitors get today.

## Step 2: See all the sites you use

One site is a spot check. The bigger picture is every service your team relies on: email, cloud storage, CRM, payroll, your bank.

Type `pqcnow://quantum` in the address bar to open the **Quantum readiness** report. It lists the https sites you've visited with:

- their protection level, the number of visits and the last visit
- a count of sites at each level at the top
- a filter by name or by level
- **Export CSV**, so you can share the list or keep it with your migration plan

The list stays on your device, and Incognito windows aren't recorded. You can clear it at any time.

A practical way to use it: browse normally for a week, then filter for **Not quantum-safe**. That's your list of suppliers to ask about their post-quantum plans.

## Step 3: Check your own server

If your own site shows **Not quantum-safe**, the browser isn't the side that's missing support. The server is. The usual places to look:

1. **Your TLS library and web server version.** Recent versions of the common libraries support a hybrid post-quantum key exchange; older ones don't. Often the fix is an update.
2. **Your configuration.** Some servers support it but don't offer it until it's switched on in the list of allowed key exchange groups.
3. **Whatever sits in front of your server.** If you use a CDN, load balancer or reverse proxy, that's what the browser talks to. Check its settings or ask the provider.

After a change, reload the site and look at the label again.

If you'd rather have someone look at it, we offer a **free check**: we look at the handshake your server actually performs and tell you whether it already offers a hybrid post-quantum key exchange. [Request a check](https://pqcnow.com/services#check). There's no obligation to buy anything afterwards.

## What the check doesn't cover

The label is about one connection: between the browser and the first server it reaches. It doesn't tell you about:

- connections behind that server, such as calls to your database, APIs or other services
- VPNs, file transfers and backups that don't go through a browser
- data that's already stored

Those belong in the inventory from the [previous post](https://pqc.hashnode.dev/harvest-now-decrypt-later). The browser check is the quickest place to start, not the whole job.

## Where .pqc fits

The top level, **Quantum-safe**, also needs a post-quantum certificate. Every [.pqc name](https://pqc.hashnode.dev/what-is-a-pqc-name) gets one, and a .pqc site never falls back to classical encryption: if the post-quantum connection can't be made, it doesn't open. You can put your existing site behind a .pqc address without changing your server.

- Get the browser: [pqcnow.com/downloads](https://pqcnow.com/downloads)
- Free check of your server: [pqcnow.com/services#check](https://pqcnow.com/services#check)

Questions: info@pqcnow.com

---

*Written with AI help and checked by the PQC NOW team. PQC NOW is a product of ZincirX.*

