TLS / JA3 Fingerprint Test

Inspect the TLS handshake your browser presents: protocol version, cipher suite, and (when available) JA3/JA4 hashes used by bot detection to spot automation.

Handshake Details

TLS versionUnknown

Cipher suiteUnknown

HTTP protocolUnknown

Bot score (Cloudflare)N/A

JA3/JA4 hashes are computed on the edge during TLS handshake. On Cloudflare deployments, we capture them in the worker; in local dev they may show as unavailable. Deploy to see full fingerprints.

Why it matters

JA3/JA4 hashes stay stable across IP changes, letting detectors link sessions.
Mismatch between TLS stack and headers/UA is a strong automation signal.
Outdated TLS versions/ciphers correlate with headless browsers and bots.

Align TLS with the rest of your fingerprint: if you claim Chrome 120 on Windows, your cipher suite and ALPN list should match Chrome’s defaults. Pair with Headers and WebGL for consistency.

Need full TLS + JA3 capture?

Deploy to Cloudflare Pages/Workers and rerun—edge handshakes provide complete fingerprints.

Deploy guide Run other tests