JA3
JavaScript required
TLS fingerprint test
Observe this connection’s JA3 and JA4 TLS fingerprints
View the TLS ClientHello characteristics observed for this connection.
Live result
Current TLS observation
JavaScript is required to connect from this browser and display a live JA3/JA4 result.
JA3 and JA4 summarize the ClientHello received by MyLeaks. Many clients can share the same values, and middleware can alter them.
JA4
JavaScript required
ClientHello summary
- Versions offered
- JavaScript required
- Cipher suites
- JavaScript required
- Extensions
- JavaScript required
- ALPN
- JavaScript required
- SNI
- JavaScript required
Technical details
- Availability reason
- JavaScript required
- JA3 canonical/raw representation
- JavaScript required
- Cipher suite IDs
- JavaScript required
- Extension IDs
- JavaScript required
- Supported groups
- JavaScript required
- EC point formats
- JavaScript required
- Signature algorithms
- JavaScript required
JavaScript is required to run the live TLS test.
What this test measures
MyLeaks observes the TLS ClientHello for this connection and returns JA3 and JA4 TLS Client fingerprints with the available protocol fields.
How it works
The test observes one TLS ClientHello and derives both JA3 and JA4 from that same connection. See Methodology for calculation details.
What the result means
The result summarizes TLS features offered on this connection. Many browsers and other clients can share the same fingerprint, and network software may alter it.
JA3 and JA4
JA3 and JA4 are different summaries of the same TLS ClientHello, so both are shown together.
Limitations
- TLS interception, VPN or proxy software, middleware, and configurable TLS libraries may alter what reaches MyLeaks.
- Many clients can share the same JA3 or JA4 value.
- MyLeaks has no browser-family or uniqueness database for these results.
- Many clients can share the same result.