JA4 t13d091000_f91f431d341e_978abd8b448c

t13d091000_f91f431d341e_978abd8b448c

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

9

Extensions offered

10

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 9

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Extensions 10

• status_request
• compress_certificate
• signature_algorithms
• key_share
• server_name
• supported_groups
• ec_point_formats
• extended_master_secret
• supported_versions
• psk_key_exchange_modes

Named groups 3

• SecP256r1MLKEM768
• secp384r1
• secp256r1

Point formats 1

• uncompressed

771,4866-4867-4865-49196-49195-52393-49200-49199-52392,5-27-13-51-0-10-11-23-43-45,4588-24-23,0

Seen in live traffic

Connections

3

First seen

2026-09-15 03:20 UTC

Last seen

2026-09-15 03:37 UTC

Transport

TCP

JA3 hashes absorbed

3

The same client, 3 different JA3s

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

• 8f8debfe17bc73a2505a55ab4ea7edf0
• 24762ca00655a7ffe83368459b74a957
• ee63d572f6a33db17b581a9560172b6b

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.