q13d0315h3_55b375c5d22e_e9b4b416271b
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
q13d0315h3
handshake shape, human-readable
JA4_b
55b375c5d22e
truncated hash of the cipher list
JA4_c
e9b4b416271b
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 15
- 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 3
-
TLS_AES_128_GCM_SHA256 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_256_GCM_SHA384
Extensions 15
-
ec_point_formats -
key_share -
psk_key_exchange_modes -
extended_master_secret -
signature_algorithms -
session_ticket -
status_request -
server_name -
supported_versions -
renegotiation_info -
supported_groups -
quic_transport_parameters -
signed_certificate_timestamp -
application_layer_protocol_negotiation -
pre_shared_key
Named groups 3
-
x25519 -
secp521r1 -
secp384r1
Point formats 1
-
uncompressed
Raw JA3 string
771,4865-4867-4866,11-51-45-23-13-35-5-0-43-65281-10-57-18-16-41,29-25-24,0Seen in live traffic
- Connections
- 1
- First seen
- 2026-08-31 09:20 UTC
- Last seen
- 2026-08-31 09:20 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.