JA4 Fingerprint Directory

t13d1011ht_61a7ad8aa9b6_861bc38b0be4

Seen in live traffic; not in the curated database.

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_861bc38b0be4

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

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

Named groups 3

• x25519
• secp256r1
• secp384r1

Point formats 1

• uncompressed

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

Seen in live traffic

Connections

1

First seen

2026-08-23 00:05 UTC

Last seen

2026-08-23 00:05 UTC

Transport

TCP

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.