JA4 q13d0414h3_9caa18292e23_f974b4cb0673

q13d0414h3_9caa18292e23_f974b4cb0673

Presented a User-Agent we cannot attribute to a known client.

What this fingerprint encodes

Transport

QUIC

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

4

Extensions offered

14

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_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_CCM_SHA256

Extensions 14

• quic_transport_parameters
• 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
• compress_certificate
• padding

Named groups 4

• x25519
• secp256r1
• secp384r1
• secp521r1

Point formats 3

• uncompressed
• ansiX962_compressed_prime
• ansiX962_compressed_char2

771,4865-4866-4867-4868,57-0-11-10-35-16-22-23-13-43-45-51-27-21,29-23-24-25,0-1-2

Seen in live traffic

Connections

1

First seen

2026-09-26 01:17 UTC

Last seen

2026-09-26 01:17 UTC

Transport

QUIC

User-Agents seen on this fingerprint

• h2load nghttp2/1.68.0 5×

A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.

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.