JA4 t10i640200_a3acda31d846_c2f961105e84

t10i640200_a3acda31d846_c2f961105e84

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

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.0

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_e31a90cd0803_c2f961105e84
• t10i640200_e7b476f9520b_c2f961105e84
• t10i640200_f559eb9565fd_c2f961105e84
• t11i640200_13a2a23d501b_c2f961105e84
• t11i640200_67f0ca237a44_c2f961105e84
• t11i640200_a3acda31d846_c2f961105e84
• t11i640200_e31a90cd0803_c2f961105e84
• t11i640200_e7b476f9520b_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.0

Cipher suites 64

• TLS_RSA_WITH_ARIA_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
• 49220 (0xc044)
• 49234 (0xc052)
• 49221 (0xc045)
• 49235 (0xc053)
• TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
• TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256
• 49276 (0xc07c)
• TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
• TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256
• 49277 (0xc07d)
• TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (draft)
• 21 (0x0015)
• TLS_DHE_RSA_WITH_SEED_CBC_SHA
• 11 (0x000b)
• 13 (0x000d)
• 48 (0x0030)
• 62 (0x003e)
• 164 (0x00a4)
• 54 (0x0036)
• 104 (0x0068)
• 165 (0x00a5)
• 49214 (0xc03e)
• 49240 (0xc058)
• 49215 (0xc03f)
• 49241 (0xc059)
• 66 (0x0042)
• 187 (0x00bb)
• 49282 (0xc082)
• 133 (0x0085)
• 193 (0x00c1)
• 49283 (0xc083)
• 12 (0x000c)
• 151 (0x0097)
• 14 (0x000e)
• 16 (0x0010)
• 49 (0x0031)
• 63 (0x003f)
• 160 (0x00a0)
• 55 (0x0037)
• 105 (0x0069)
• 161 (0x00a1)
• 49216 (0xc040)
• 49236 (0xc054)
• 49217 (0xc041)
• 49237 (0xc055)
• 67 (0x0043)
• 188 (0x00bc)
• 49278 (0xc07e)
• 134 (0x0086)
• 194 (0x00c2)
• 49279 (0xc07f)
• 15 (0x000f)
• 152 (0x0098)
• 25 (0x0019)
• 23 (0x0017)
• 27 (0x001b)
• 52 (0x0034)
• 108 (0x006c)
• 166 (0x00a6)
• 58 (0x003a)

Extensions 2

• supported_groups
• ec_point_formats

Named groups 6

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

Point formats 1

• uncompressed

769,49311-49315-159-49220-49234-49221-49235-69-190-49276-136-196-49277-52394-52245-21-154-11-13-48-62-164-54-104-165-49214-49240-49215-49241-66-187-49282-133-193-49283-12-151-14-16-49-63-160-55-105-161-49216-49236-49217-49237-67-188-49278-134-194-49279-15-152-25-23-27-52-108-166-58,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.

• 6660c06945a07c9607b997eddb9c1056
• d3b255a7a10be1525299b19c5b91a217

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.