JA4 Fingerprint Directory

t12i1004h2_61a7ad8aa9b6_c0fedda59e3e

Presented a User-Agent we cannot attribute to a known client.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.2

Server name

no server name (IP literal)

Cipher suites offered

10

Extensions offered

4

ALPN

h2

The hello it was computed from

Recovered because the proxy now stores the pre-hash JA3 string alongside the digest. Every number below came out of this client's ClientHello; anything we cannot name in the IANA registry is shown as its raw value rather than guessed at.

Version

TLS 1.2

Cipher suites 10

• TLS_AES_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 4

• application_layer_protocol_negotiation
• status_request
• key_share
• session_ticket

771,4866-4865-4867-49196-49195-52393-49200-49199-52392-255,16-5-51-35,,

Seen in live traffic

Connections

1

First seen

2026-08-23 13:10 UTC

Last seen

2026-08-23 13:10 UTC

Transport

TCP

User-Agents seen on this fingerprint

• Mozilla/5.0 (compatible; Qwantbot/1.0_5800367; +https://help.qwant.com/bot/) 1×

A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.

This entry is an observation, not a policy decision. It is here because the edge saw it, not because anyone reviewed it, and it blocks nothing on its own. Only the curated tier drives classification and banning.