HoneyLabs

UDP traffic / QUIC JA4 client fingerprint

q13i0213sb_62ed6f6ca7ad_03ad308c6343

QUIC JA4 client fingerprint. 3 datagrams in the last 30 days, last seen 2026-10-07 18:46 UTC.

A UDP source address can be forged, so each address listed here either sent the traffic or was impersonated by whoever did. UDP traffic is kept out of verdicts, feeds, watchlists and alerts.

3

Datagrams

3

Source addresses

3

Networks

1

Countries

1

Destination ports

Traffic by type

QUIC

3 datagrams from 3 sources

Initial packets of HTTP/3 connections, decoded on the sensor.

Latest QUIC datagram, to 443/udp

QUIC v1 Initial alpn=smb

Destination ports

QUIC clients (JA4)

QUIC transport parameters

QUIC versions

Networks

Countries

Source addresses (unverified)

AddressNetworkCcSendsDatagramsLast seen (UTC)
46.46.137.198AS29470 JSC RetnNetRUQUIC12026-10-07 18:46
62.105.128.170AS3216 PVimpelComRUQUIC12026-10-07 10:56
94.41.245.248AS24955 JSC UfanetRUQUIC12026-10-07 15:11

Latest datagrams

About this fingerprint

JA4 over QUIC fingerprints the TLS ClientHello carried inside a client's QUIC Initial packets, with a q prefix in place of t. Initial packets are encrypted with keys anyone can derive from the packet itself, which is how the sensor reads the ClientHello without answering. The same client library and version produce the same JA4.