← Knowledge base

Google Chrome

Chrome uses its own TLS implementation. Enterprise policy, platform, and the server all influence a particular connection.

Evidence to collect

1. Record the browser version and applied enterprise policies.
2. Use the browser check for the connection to CheckPQC. For another website, use its own connection details or server evidence.
3. Do not infer the readiness of every website or native application from one browser result.

Record the scope and result

Record the tested component, client, peer, protocol, selected algorithm, and date. Keep observed negotiation, documented capability, and unknown distinct. A failed check can reflect local tooling, certificate validation, network policy, or configuration; it does not prove that all PQC is unsupported.

Official references

• BoringSSL and Chromium TLS architecture

Guidance reviewed 24 September 2026. Verify documentation for your deployed release; vendor capabilities and defaults change.