JA3 and JA4 TLS Fingerprint Calculator (from a ClientHello)
Compute the JA3 and JA4 TLS client fingerprints from a ClientHello you captured, with the ciphers, extensions and groups decoded.
Use the tool
Why this tool exists
JA3 and JA4 summarise how a TLS client says hello (versions, cipher suites, extensions, curves) into a short hash, which defenders use to spot bot frameworks, malware and unusual clients, and which scraping teams check to understand why a request is challenged. The page cannot see your connection, so you give it a capture: hex from Wireshark ("Copy as hex stream"), tcpdump, or `openssl s_client -msg`.
GREASE values are removed as the specifications require. JA3 follows the original Salesforce definition; JA4 follows the FoxIO specification and matches the ja4plus reference port on our test hellos. Chrome and Firefox shuffle extension order, which changes JA3 per connection but not JA4. A fingerprint identifies software, not a person.
How to use it
- Capture a ClientHello and copy it as hex (a TLS record starting 16 03, or a handshake starting 01).
- Paste it; a JA3 string alone is also accepted and hashed.
- Read the JA3 MD5, the JA4 string and the decoded ciphers and extensions.
Frequently asked questions
How do I get the hex?
In Wireshark select the Client Hello, then Copy > ...as a Hex Stream. With OpenSSL, run s_client with -msg and copy the bytes of the first message.
Why does my browser give a different JA3 each time?
Modern Chrome and Firefox randomise the order of extensions. JA4 sorts them, so it stays stable.
Is this a way to bypass bot detection?
No. It only computes the published hashes of a hello you supply, which is what defenders and testers do to understand their traffic.