QUIC transport fingerprint
JavaScript required
Algorithm: myleaks-quic-v1
HTTP/3 and QUIC fingerprint test
Observe QUIC and HTTP/3 connection characteristics
Inspect two distinct MyLeaks-defined summaries from the same direct HTTP/3 connection. They describe the connection that reached MyLeaks, not a browser, device, or person.
Live result
Current direct QUIC and HTTP/3 observation
JavaScript is required to attempt the direct browser QUIC/HTTP3 measurement.
HTTP/3 fingerprint
JavaScript required
Algorithm: myleaks-h3-v1
Direct connection summary
- QUIC public IP
- JavaScript required
- QUIC version
- JavaScript required
- Transport parameters
- JavaScript required
- HTTP/3 SETTINGS
- JavaScript required
Technical details
- Availability reason
- JavaScript required
- QUIC canonical
- JavaScript required
- HTTP/3 canonical
- JavaScript required
- Transport parameters
- JavaScript required
- QUIC GREASE exposure
- JavaScript required
- Initial DCID / SCID length
- JavaScript required
- 0-RTT attempted / accepted
- JavaScript required
- HTTP/3 SETTINGS
- JavaScript required
- HTTP/3 SETTINGS GREASE
- JavaScript required
- Request header-name order
- JavaScript required
JavaScript is required to run the live QUIC/HTTP3 test.
What this test measures
MyLeaks observes direct QUIC transport characteristics and separate HTTP/3 SETTINGS and request characteristics. It produces myleaks-quic-v1 for the transport layer and myleaks-h3-v1 for the HTTP/3 layer. Both are MyLeaks-defined results.
How it works
The browser attempts an HTTP/3 connection over QUIC. MyLeaks records the available transport and HTTP/3 characteristics and keeps the two results separate. See Methodology for calculation details.
What the results mean
The two results summarize characteristics of this connection. Many clients can share the same values, and network software may alter them.
QUIC versus HTTP/3
QUIC is the transport layer. HTTP/3 runs over QUIC and exposes a different set of SETTINGS and request characteristics. MyLeaks therefore keeps the two project-defined canonicals and SHA-256 hashes separate even though they come from the same direct H3 connection.
Limitations
- Browsers, proxies, firewalls, gateways, or network policy may block QUIC or use a different network path.
- Some protocol fields or wire ordering are unavailable and are shown as Not exposed.
- Transport-parameter GREASE is omitted when it cannot be observed. Dynamic reserved HTTP/3 GREASE identifiers and values are not hashed.
- Many clients can share the same result.