JA4 t13i130500_f6a34bea2645_193c2c6852e3

t13i130500_f6a34bea2645_193c2c6852e3

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

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.3

Server name

no server name (IP literal)

Cipher suites offered

13

Extensions offered

5

ALPN

none offered

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 13

• TLS_AES_128_CCM_8_SHA256
• TLS_AES_128_CCM_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• 49332 (0xc0b4)
• 49333 (0xc0b5)
• 199 (0x00c7)
• 198 (0x00c6)
• TLS_DHE_RSA_WITH_AES_128_CCM_8
• TLS_RSA_WITH_AES_128_CCM_8
• TLS_DHE_RSA_WITH_AES_256_CCM_8
• TLS_RSA_WITH_AES_256_CCM_8

Extensions 5

• ec_point_formats
• supported_versions
• supported_groups
• signature_algorithms
• key_share

Named groups 6

• secp256r1
• secp384r1
• secp521r1
• x25519
• ffdhe2048
• 41 (0x0029)

Point formats 1

• uncompressed

771,4869-4868-4865-4866-4867-49332-49333-199-198-49330-49328-49331-49329,11-43-10-13-51,23-24-25-29-256-41,0

Seen in live traffic

Connections

9

First seen

2026-09-07 02:39 UTC

Last seen

2026-10-09 02:35 UTC

Transport

TCP

JA3 hashes absorbed

5

The same client, 5 different JA3s

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

• bf3372e1a919e16dea0c9fbd3e8e894a
• af75dc975811f91028a69a9bdae90b94
• c37a6c62a6e779f8ea02614a7f33c1f9
• 1250ad853027dbb09f740be347daa56f
• 7ce763df7955862f14bb8d5ba5c29e7c

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.