JA3/JA4 Fingerprint

JA3 Open external link and JA4 Open external link Fingerprints help you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.

If you want to use JA4 fingerprints and Signals Intelligence, your script must be able to handle the absence of any field in the array, including:

• The possibility that the JA4 fingerprint could be missing.
• The possibility that the ja4Signals array could be missing.
• Results with NaN or Infinity values will be excluded from the array.

​​ Analytics

To get more information about potential bot requests, use these JA3 and JA4 fingerprints in:

• Bot Analytics
• Security Events and Security Analytics
• Analytics GraphQL API, specifically the HTTP Requests dataset
• Logs

​​ Actions

To adjust how your application responds to specific fingerprints, use them with:

• WAF custom rules
• Transform Rules
• Cloudflare Workers

​​ Use cases

​​ Block or allow certain traffic

A group of similar requests may share the same JA3 fingerprint. For this reason, JA3 may be useful in blocking an incoming threat. For example, if you notice that a bot attack is not caught by existing defenses, create a custom rule that blocks or challenges the JA3 used for the attack.

Alternatively, if existing defenses are blocking traffic that is actually legitimate, create a custom rule with the Skip action allowing the JA3 seen across good requests.

JA3 may also be useful if you want to immediately remedy false positives or false negatives with Bot Management.

​​ Allow mobile traffic

Often, mobile application traffic will produce the same JA3 fingerprint across devices and users. This means you can identify your mobile application traffic by its JA3 fingerprint.

Use the JA3 fingerprint to allow traffic from your mobile application, but block or challenge remaining traffic.