JA4 t13d2309h2_bc6434d430c8_2977e3beeb43

t13d2309h2_bc6434d430c8_2977e3beeb43

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

23

Extensions offered

9

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 23

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_CCM_SHA256
• TLS_AES_128_CCM_8_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 9

• server_name
• extended_master_secret
• signature_algorithms
• ec_point_formats
• supported_groups
• supported_versions
• application_layer_protocol_negotiation
• psk_key_exchange_modes
• key_share

Named groups 5

• x25519
• secp256r1
• secp384r1
• secp521r1
• ffdhe2048

Point formats 1

• uncompressed

771,4865-4866-4867-4868-4869-49195-49199-49196-49200-52393-52392-49161-49171-49162-49172-158-159-156-157-47-53-10-255,0-23-13-11-10-43-16-45-51,29-23-24-25-256,0

Seen in live traffic

Connections

133

First seen

2026-08-24 07:54 UTC

Last seen

2026-10-09 20:49 UTC

Transport

TCP

JA3 hashes absorbed

3

The same client, 3 different JA3s

This one JA4 covers 3 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 3 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

• 133e24b7641cba6242249229374d88fb
• 8d2da38d73b3904ef23dc62220d682be
• b3278df1e4d901e1ffd85ce6f09e6931

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.