JA4 t13d070600_c2f3549b8eb7_83fe30743d85

t13d070600_c2f3549b8eb7_83fe30743d85

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

7

Extensions offered

6

ALPN

none offered

Same tool, different options

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

• t13d050600_13f69f63e3fe_83fe30743d85
• t13d060600_a6485224f4b1_83fe30743d85

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 7

• 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)

Extensions 6

• supported_groups
• server_name
• signature_algorithms
• supported_versions
• key_share
• renegotiation_info

Named groups 1

• SecP256r1MLKEM768

771,4865-4866-4867-4868-4869-198-199,10-0-13-43-51-65281,4588,

Seen in live traffic

Connections

120

First seen

2026-09-17 13:53 UTC

Last seen

2026-09-17 14:19 UTC

Transport

TCP

JA3 hashes absorbed

8

The same client, 8 different JA3s

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

• 5c06a6e140b4d06398861b4043ed281c
• 5a835cb56fd547cb9b2e475447d21645
• a914c792418d079720527c7acd7e09e4
• 188ee2d33a9648c1382ec8bb325897fd
• 518dae58aac755998789b2d634d0871a
• 6ac3f2f3f61c9a013fe62af2a6232da5
• dd50834fa61add78a8c00db7ea3f2925
• 9accfbbb7b67c37aca0bef37fe7f8979

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.