JA4 t13d740800_57a946f9b90a_790092838e5c

t13d740800_57a946f9b90a_790092838e5c

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

74

Extensions offered

8

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 74

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
• TLS_DHE_RSA_WITH_AES_256_CBC_SHA
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA
• 49229 (0xc04d)
• 49228 (0xc04c)
• 49221 (0xc045)
• TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256
• TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
• TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256
• TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
• 49220 (0xc044)
• 49213 (0xc03d)
• TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256
• TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
• TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256
• 49212 (0xc03c)
• TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
• TLS_DHE_RSA_WITH_SEED_CBC_SHA
• TLS_RSA_WITH_SEED_CBC_SHA
• TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
• TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_ECDHE_RSA_WITH_RC4_128_SHA
• TLS_RSA_WITH_RC4_128_SHA
• TLS_RSA_WITH_RC4_128_MD5
• 21 (0x0015)
• 9 (0x0009)
• 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_ECDSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• 49224 (0xc048)
• 49225 (0xc049)
• TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
• 163 (0x00a3)
• 162 (0x00a2)
• 106 (0x006a)
• 64 (0x0040)
• 50 (0x0032)
• 56 (0x0038)
• 49219 (0xc043)
• 195 (0x00c3)
• 135 (0x0087)
• 189 (0x00bd)
• 49218 (0xc042)
• 68 (0x0044)
• 153 (0x0099)
• 19 (0x0013)
• 18 (0x0012)
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 8

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

Named groups 30

• x25519
• x448
• secp256r1
• secp384r1
• secp521r1
• 26 (0x001a)
• 27 (0x001b)
• 28 (0x001c)
• 22 (0x0016)
• 10 (0x000a)
• 9 (0x0009)
• 12 (0x000c)
• 11 (0x000b)
• 14 (0x000e)
• 13 (0x000d)
• 8 (0x0008)
• 7 (0x0007)
• 6 (0x0006)
• 21 (0x0015)
• 20 (0x0014)
• 5 (0x0005)
• 4 (0x0004)
• 19 (0x0013)
• 18 (0x0012)
• 2 (0x0002)
• 3 (0x0003)
• 1 (0x0001)
• 16 (0x0010)
• 17 (0x0011)
• 15 (0x000f)

Point formats 1

• uncompressed

771,4865-4866-4867-49200-49199-159-158-52392-52394-157-156-49192-49172-49191-49171-107-57-103-51-61-60-53-47-49229-49228-49221-196-136-190-69-49220-49213-192-132-186-49212-65-154-150-22-49170-10-49169-5-4-21-9-49196-49195-52393-49188-49187-49162-49161-49224-49225-49160-49159-163-162-106-64-50-56-49219-195-135-189-49218-68-153-19-18-255,43-11-10-0-13-23-45-51,29-30-23-24-25-26-27-28-22-10-9-12-11-14-13-8-7-6-21-20-5-4-19-18-2-3-1-16-17-15,0

Seen in live traffic

Connections

5

First seen

2026-09-10 15:48 UTC

Last seen

2026-10-26 12:50 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.

• b1179b4364af89be0558f0772ead2102
• 457f5b94fa97aaf5f67e524f36360a30

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.