Skip to Content
Platform.Ontology

HTTP/3 and QUIC fingerprint

QUIC's first packet carries a readable ClientHello, giving the same fingerprints as TLS plus transport parameters.

Used to track youNetwork and connectionHTTPWeb browsersWhen the page loads

In one line

Can tell which browser or tool you use from the first packet of a fast connection

QUIC's first packet carries a readable ClientHello, giving the same fingerprints as TLS plus transport parameters.

The QUIC Initial packet is encrypted with a public key, so middleboxes can read the TLS ClientHello and QUIC transport parameters. JA4 has a QUIC variant (prefix q). Connection ID length and version also differ per stack.

What it can and can't do

What the user does: Nothing. It happens when your browser opens a new HTTP/3 connection

It can

  • Compare the opening packet and its settings with known browsers
  • Use the same kind of fingerprint as normal secure connections
  • Spot scripts and bots with unusual connection details

It cannot

  • Know your name or account from it
  • Tell two people on the same browser apart
  • Apply to sites that do not use HTTP/3

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIQUIC Initial packet decrypt at edge; JA4 q variant
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Capture Initial packet
  2. Derive Initial keys
  3. Parse ClientHello and transport params

Data you get

What comes back: JA4 style string
Shape: string

FieldTypeUnitRangePrecision
quic_ja4stringNoneq13d...exact

Technical limits

  • Less deployed than TCP fingerprints
  • ECH will hide inner ClientHello fields

The story

What it is

The first packet of the newest connection type shows readable clues about your browser.

For you

You never see it. When your browser starts a fast new type of connection, the first message has readable details that match your browser and system. A server can tell real browsers from fake ones.

For makers

Bot defense and fraud teams extend their older checks to the newest connection type. It gives them the same browser signature plus extra transport details. It also adds to a long term fingerprint.

Where you see it

TypeExampleApps
securityA bot defense reads the first packet and blocks tools that fake a browser name.Cloudflare, Akamai
gamesA game portal blocks cheat sellers that script account creation.None named
shoppingA retailer protects limited drops from bots.Ticketmaster
mediaA video site blocks scrapers that rip its streams.YouTube
adsAn ad network filters click farms by connection pattern.None named
analyticsA researcher measures which browsers use the new connection type.None named

Risks

  • Hard to hide
  • Part of a fingerprint

Good uses and abuse

Legitimate uses

  • Bot detection on HTTP/3 edges

Known abuse

  • Same as JA4

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

History

  • 2021-05, rfc: RFC 9000 and 9001 define QUIC and its TLS binding
  • 2022-06, rfc: RFC 9114 HTTP/3 published

Sources

How well checked: Based on official documentation.

On this page