JA4 t11i640200_e7b476f9520b_c2f961105e84

t11i640200_e7b476f9520b_c2f961105e84

Probe (legacy TLS, no SNI, no ALPN) — inferred from the JA4 handshake shape.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.1

Server name

no server name (IP literal)

Cipher suites offered

64

Extensions offered

2

ALPN

none offered

Same tool, different options

These 11 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.

• t10i640200_13a2a23d501b_c2f961105e84
• t10i640200_67f0ca237a44_c2f961105e84
• t10i640200_a3acda31d846_c2f961105e84
• t10i640200_e31a90cd0803_c2f961105e84
• t10i640200_e7b476f9520b_c2f961105e84
• t10i640200_f559eb9565fd_c2f961105e84
• t11i640200_13a2a23d501b_c2f961105e84
• t11i640200_67f0ca237a44_c2f961105e84
• t11i640200_a3acda31d846_c2f961105e84
• t11i640200_e31a90cd0803_c2f961105e84
• t11i640200_f559eb9565fd_c2f961105e84

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.1

Cipher suites 64

• 29 (0x001d)
• 28 (0x001c)
• 65279 (0xfeff)
• 65278 (0xfefe)
• 99 (0x0063)
• 101 (0x0065)
• 17 (0x0011)
• 114 (0x0072)
• 19 (0x0013)
• 115 (0x0073)
• 50 (0x0032)
• 64 (0x0040)
• 162 (0x00a2)
• 116 (0x0074)
• 56 (0x0038)
• 106 (0x006a)
• 163 (0x00a3)
• 49218 (0xc042)
• 49238 (0xc056)
• 49219 (0xc043)
• 49239 (0xc057)
• 68 (0x0044)
• 189 (0x00bd)
• 49280 (0xc080)
• 135 (0x0087)
• 195 (0x00c3)
• 49281 (0xc081)
• 18 (0x0012)
• 102 (0x0066)
• 153 (0x0099)
• 143 (0x008f)
• 144 (0x0090)
• 178 (0x00b2)
• 49318 (0xc0a6)
• 170 (0x00aa)
• 145 (0x0091)
• 179 (0x00b3)
• 49319 (0xc0a7)
• 171 (0x00ab)
• 49254 (0xc066)
• 49260 (0xc06c)
• 49255 (0xc067)
• 49261 (0xc06d)
• 49302 (0xc096)
• 49296 (0xc090)
• 49303 (0xc097)
• 49297 (0xc091)
• 52397 (0xccad)
• 45 (0x002d)
• 180 (0x00b4)
• 181 (0x00b5)
• 142 (0x008e)
• 20 (0x0014)
• 119 (0x0077)
• TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
• 120 (0x0078)
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_ARIA_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• 121 (0x0079)
• TLS_DHE_RSA_WITH_AES_256_CBC_SHA
• TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

Extensions 2

• supported_groups
• ec_point_formats

Named groups 6

• secp256r1
• secp384r1
• secp521r1
• x25519
• ffdhe2048
• SecP256r1MLKEM768

Point formats 1

• uncompressed

770,29-28-65279-65278-99-101-17-114-19-115-50-64-162-116-56-106-163-49218-49238-49219-49239-68-189-49280-135-195-49281-18-102-153-143-144-178-49318-170-145-179-49319-171-49254-49260-49255-49261-49302-49296-49303-49297-52397-45-180-181-142-20-119-22-120-51-103-49310-49314-158-121-57-107,10-11,23-24-25-29-256-4588,0

Seen in live traffic

Connections

5

First seen

2026-08-27 08:43 UTC

Last seen

2026-08-27 08:49 UTC

Transport

TCP

JA3 hashes absorbed

2

The same client, 2 different JA3s

This one JA4 covers 2 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 2 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.

• 17646c610acf719534dec8972df3dc34
• 7e65b148cca26a2244514e19d228d77c

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.