JA4 q13d0412h3_16476d049b0b_a05e41356250

q13d0412h3_16476d049b0b_a05e41356250

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

Transport

QUIC

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

4

Extensions offered

12

ALPN

h3

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 4

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 12

• server_name
• ec_point_formats
• supported_groups
• session_ticket
• application_layer_protocol_negotiation
• encrypt_then_mac
• extended_master_secret
• signature_algorithms
• supported_versions
• psk_key_exchange_modes
• key_share
• quic_transport_parameters

Named groups 10

• x25519
• secp256r1
• x448
• secp521r1
• secp384r1
• ffdhe2048
• ffdhe3072
• ffdhe4096
• 259 (0x0103)
• 260 (0x0104)

Point formats 3

• uncompressed
• ansiX962_compressed_prime
• ansiX962_compressed_char2

771,4866-4867-4865-255,0-11-10-35-16-22-23-13-43-45-51-57,29-23-30-25-24-256-257-258-259-260,0-1-2

Seen in live traffic

Connections

7

First seen

2026-08-27 16:33 UTC

Last seen

2026-08-27 16:59 UTC

Transport

QUIC

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.