JA4 q13d0316h3_55b375c5d22e_df815552bcbf

q13d0316h3_55b375c5d22e_df815552bcbf

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

3

Extensions offered

16

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_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

Extensions 16

• server_name
• ec_point_formats
• session_ticket
• renegotiation_info
• extended_master_secret
• signed_certificate_timestamp
• quic_transport_parameters
• status_request
• supported_groups
• signature_algorithms
• signature_algorithms_cert
• application_layer_protocol_negotiation
• supported_versions
• key_share
• psk_key_exchange_modes
• pre_shared_key

Named groups 4

• x25519
• secp256r1
• secp384r1
• secp521r1

Point formats 1

• uncompressed

771,4865-4866-4867,0-11-35-65281-23-18-57-5-10-13-50-16-43-51-45-41,29-23-24-25,0

Seen in live traffic

Connections

1

First seen

2026-08-26 05:41 UTC

Last seen

2026-08-26 05:41 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.