JA4 t13d1011ht_61a7ad8aa9b6_37eac399f7d8

t13d1011ht_61a7ad8aa9b6_37eac399f7d8

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

10

Extensions offered

11

ALPN

ht

Same tool, different options

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

• t13d1011h2_61a7ad8aa9b6_37eac399f7d8

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 10

• TLS_AES_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_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
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 11

• psk_key_exchange_modes
• extended_master_secret
• status_request
• ec_point_formats
• supported_groups
• server_name
• key_share
• supported_versions
• signature_algorithms
• application_layer_protocol_negotiation
• pre_shared_key

Named groups 3

• x25519
• secp256r1
• secp384r1

Point formats 1

• uncompressed

771,4866-4865-4867-49196-49195-52393-49200-49199-52392-255,45-23-5-11-10-0-51-43-13-16-41,29-23-24,0

Seen in live traffic

Connections

2

First seen

2026-08-30 01:44 UTC

Last seen

2026-08-30 01:48 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.

• 2e72d8f7a9fd647dc92d4a6a927c1dea
• 1b9811f8d87e6e226eaca3ec65bfc2c3

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.