Network

JA4

A TLS client fingerprint built from ClientHello fields, sorted to resist randomisation, used to identify client software regardless of IP.

JA4 (FoxIO, 2023) fingerprints the TLS ClientHello. Its readable prefix encodes transport (t TCP, q QUIC), TLS version, whether SNI is a domain or IP, cipher and extension counts and the first ALPN value; two truncated SHA-256 hashes follow, one of the sorted cipher list and one of the sorted extensions plus signature algorithms. The JA4+ family adds server, HTTP, SSH and other fingerprints.

It replaced JA3, whose hash of fields in wire order broke once Chrome began randomising extension order. Sorting makes JA4 stable for a given client build.

Uses: spotting bots that claim to be Chrome in the User-Agent but present a Python or Go TLS stack, and tracking malware families across changing infrastructure. Limits: many clients share a fingerprint (all users of one browser version), and capable attackers can mimic a browser stack, so treat it as one feature in a risk score, never a sole block rule.

JA4 structuretext
t13d1516h2_8daaf6152771_02713d6af862
| | | | | |  |            +- hash of sorted extensions + signature algorithms
| | | | | |  +- hash of sorted cipher suites
| | | | | +- ALPN first value (h2)
| | | | +- 16 extensions
| | | +- 15 cipher suites
| | +- d = SNI is a domain
| +- TLS 1.3
+- t = TCP

Learn it properly

Also used in

Related terms