JA4 t13d060700_a150a9413979_241b3681de17

t13d060700_a150a9413979_241b3681de17

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

6

Extensions offered

7

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 6

• TLS_EMPTY_RENEGOTIATION_INFO_SCSV
• TLS_AES_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_CCM_SHA256
• TLS_AES_128_CCM_8_SHA256

Extensions 7

• key_share
• ec_point_formats
• supported_versions
• server_name
• signature_algorithms_cert
• supported_groups
• signature_algorithms

Named groups 8

• x25519
• x448
• secp521r1
• secp384r1
• secp256r1
• 33 (0x0021)
• 32 (0x0020)
• 31 (0x001f)

Point formats 1

• uncompressed

771,255-4866-4865-4867-4868-4869,51-11-43-0-50-10-13,29-30-25-24-23-33-32-31,0

Seen in live traffic

Connections

4

First seen

2026-08-26 02:15 UTC

Last seen

2026-08-26 02:15 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.

• 2f8ab4e846536235e3a043f3c5635ac8
• 292a23d18e391ecdb06c8dccedd524d2

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.