JA4 t13d120700_dd9017382ddc_13d7658266da

t13d120700_dd9017382ddc_13d7658266da

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

12

Extensions offered

7

ALPN

none offered

Same tool, different options

These 5 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.

• t00d120700_dd9017382ddc_13d7658266da
• t13d020700_9d5106e3f751_13d7658266da
• t13d030700_dd90744a70f1_13d7658266da
• t13d100700_dfb617a4bdc8_13d7658266da
• t13d110700_61af50b1aabb_13d7658266da

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 12

• 49411 (0xc103)
• 49412 (0xc104)
• 49413 (0xc105)
• 49414 (0xc106)
• 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
• 198 (0x00c6)
• 199 (0x00c7)
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 7

• server_name
• 40 (0x0028)
• key_share
• supported_versions
• signature_algorithms_cert
• supported_groups
• signature_algorithms

Named groups 5

• ffdhe2048
• ffdhe3072
• ffdhe4096
• 259 (0x0103)
• 260 (0x0104)

771,49411-49412-49413-49414-4865-4866-4867-4868-4869-198-199-255,0-40-51-43-50-10-13,256-257-258-259-260,

Seen in live traffic

Connections

9

First seen

2026-10-20 22:31 UTC

Last seen

2026-10-20 22:31 UTC

Transport

TCP

JA3 hashes absorbed

9

The same client, 9 different JA3s

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

• 3ac05473284badfcf949d692fd1b068f
• e4d52a43c7920a6bd5d6524d2db8b9db
• 0d45f2db4b5ad1c2bfa90c025e57a944
• b6369da507549226e909c9d80e957046
• bf8d34783ed083b22b1aa9c957e336e4
• c744e2fad61f0b7f0202e1abc9317d28
• c7a700d2f91334d5920afdf96b91533a
• 9915be6c703b0640963fd2e8479c753a
• cd156a66d052544e9488e34553f7bbf1

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.