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