CyberKit

JA3 Fingerprinting

Also called JA3, JA3S, TLS client fingerprint.

Hashing TLS handshake fields to fingerprint the client software.

What it is

A method that builds a hash from selected fields of a TLS Client Hello (version, cipher suites, extensions, and curves) to fingerprint the client implementation. The server-side counterpart, JA3S, fingerprints the Server Hello.

Why it matters

Because many malware families share a TLS stack, their handshakes hash to recognizable values even though the traffic is encrypted. This gives detection a foothold without decrypting anything.

In practice

Flagging an encrypted beacon because its Client Hello produced a JA3 hash known to belong to a particular implant's networking library.

What to look for

  • Client hashes that match known malware or tools.
  • Rare hashes from inside the network.
  • One hash shared by many unrelated destinations.

Common mistake

Blocking on JA3 alone. Common libraries share hashes, and browsers randomize extensions now.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

Sources