Try
BROWSER TOOLS TLS uses todaySince 2026-11-07

TLS client fingerprint

Before loading an HTTPS site, your browser sends a ClientHello listing the protocol versions, cipher suites and extensions it supports. The content and order of that list form a TLS fingerprint, which sites and anti-abuse systems use to tell a real browser from a script or a proxy. This page connects straight to our probe and shows the handshake your browser just sent.

This handshake

Protocol
 
Cipher suite
 
Key exchange
 
Application protocol (ALPN)
 
  • Testing

    The probe accepts TLS 1.2 and 1.3; this is the version your browser and the probe agreed on.

  • Testing

    Suites flagged in the list below are only offered for compatibility with old servers; this line states the one actually used.

  • Testing

    Each deprecated version has a port that accepts nothing else. A modern browser should fail to connect; success means the client or a proxy in between still accepts the old protocol.

  • Testing

    Recent Chrome, Edge and Firefox offer X25519MLKEM768 by default. Its absence does not weaken today’s connection.

  • Testing

    ECH encrypts the site name in the handshake. The browser needs the configuration from a resolver that serves HTTPS records, usually DoH; otherwise it sends only a placeholder.

Client fingerprints

Computed from the ClientHello
JA4Sorted, then hashed; stable
 
JA4_rJA4 before hashing
 
JA4_oJA4 in offered order
 
JA4_roOffered order, before hashing
 
JA3MD5; changes with extension order
 
JA3 FullThe JA3 input string
 
JA3_nJA3 with sorted extensions; stable
 
JA3_n FullThe JA3_n input string
 

Chrome has shuffled extension order on every handshake since version 110, so JA3 can differ between connections. JA3_n and JA4 sort before hashing and stay stable for a browser version. A matching fingerprint means matching handshake parameters, not a unique device.

Protocol versions

One dedicated port per version
TLS 1.3

No connection; not proof of missing support

TLS 1.2

No connection; not proof of missing support

TLS 1.1

Deprecated; refusing it is expected

TLS 1.0

Deprecated; refusing it is expected

Offered in the ClientHello

Cipher suites

#IDName
1
2
3
4
5
6
7
8

Extensions

#IDName
1
2
3
4
5
6
7
8

Key exchange groups

#IDName
1
2
3
4

Signature algorithms

#IDName
1
2
3
4

Other observations

SNISite name sent in clear in the handshake
 
Offered ALPNApplication protocols the browser offers
 
Session resumptionWhether an earlier session was resumed
 
EC point formatsec_point_formats
 
Mixed content · scriptAn HTTP script on an HTTPS page
 
Mixed content · imageAn HTTP image on an HTTPS page
 
User-AgentBrowser identifier on the same request
 

These results describe the connection that reached the probe. Behind a proxy or security product that terminates TLS, the handshake shown here is theirs, not the browser’s.

How to use this tool

How this works

See your browser’s JA3, JA3_n and JA4 TLS fingerprints with every cipher suite, extension, key exchange group and signature algorithm, plus live tests for TLS 1.0–1.3, ECH and post-quantum key exchange.

Steps

  • The test runs when the page opens. Keep the proxy or VPN state you want to inspect.
  • Start with “This handshake”: the negotiated version, suite and key exchange, and five checks.
  • Copy JA4 or JA3_n to compare fingerprints; use the suite and extension tables when investigating compatibility.

What the result tells you

A matching fingerprint means matching handshake parameters. Browsers of the same version usually share one; it is not a unique device identifier.

Behind a proxy or security product that terminates TLS, the handshake recorded is theirs.

Suites flagged CBC or No PFS are kept for compatibility with old servers. Every modern browser offers them; they do not make the connection insecure.

Common questions4

How do JA3 and JA4 differ?

JA3 hashes values in the order sent. Chrome has shuffled extension order on every handshake since version 110, so its JA3 keeps changing. JA4 and JA3_n sort first and stay stable for a browser version, which makes them better for comparison.

What if the fingerprint does not match the User-Agent?

Anti-abuse systems compare the two. A client that claims to be Chrome but sends a different handshake is typical of scripts with an edited User-Agent, anti-detect browsers or intermediary proxies, and can trigger challenges or blocks.

Why is it normal for TLS 1.0 and 1.1 not to connect?

Both versions are deprecated by RFC 8996 and disabled in mainstream browsers. The probe has a dedicated port for each. A failed connection can also mean network filtering or an unavailable endpoint; it alone cannot confirm that the browser disabled that version.

What is GREASE?

Placeholder values defined in RFC 8701. Browsers insert a few reserved numbers into the suite and extension lists at random so servers stay tolerant of unknown values. JA3 and JA4 ignore them.

mimetic
mimetic
mimetic