MyLeaks HTTP/2 fingerprint
JavaScript required
Algorithm: myleaks-h2-v1
HTTP/2 fingerprint test
Observe HTTP/2 connection characteristics
Inspect the HTTP/2 client initialization observed for this connection.
Live result
Current direct HTTP/2 observation
JavaScript is required to connect from this browser and display a live HTTP/2 result.
Connection summary
- Protocol
- JavaScript required
- SETTINGS
- JavaScript required
- Connection WINDOW_UPDATE
- JavaScript required
- Initial frames
- JavaScript required
- Pseudo-header order
- JavaScript required
Technical details
- Availability reason
- JavaScript required
- Canonical
- JavaScript required
- SETTINGS wire order
- JavaScript required
- Unknown SETTINGS
- JavaScript required
- Stream WINDOW_UPDATE
- JavaScript required
- PRIORITY
- JavaScript required
- Unknown frame types
- JavaScript required
- Regular header-name order
- JavaScript required
- HEADERS END_STREAM
- JavaScript required
- HEADERS END_HEADERS
- JavaScript required
JavaScript is required to run the live HTTP/2 test.
What this test measures
MyLeaks observes HTTP/2 client initialization: SETTINGS identifiers and values in wire order, initial non-ACK frame behavior, connection flow-control updates, pseudo-header order, and regular header-name order. Existing stream-window, priority, and end-state facts remain available in Technical details.
How it works
The test opens an HTTP/2 connection and records its initial settings, frames, window updates, and header order. See Methodology for calculation details.
What the result means
The result describes the observed connection behavior. Many clients can share it, and proxies or intermediaries may alter it.
About myleaks-h2-v1
myleaks-h2-v1 is MyLeaks-defined. It is not JA4H, Akamai fingerprinting, or a universal standard. Its SHA-256 input preserves the established V1 SETTINGS, window-update, frame, pseudo-header, and regular header-name ordering semantics. Header values, IP addresses, ports, and timings are excluded.
Limitations
The direct HTTP/2 probe uses TCP/8443. Some networks, proxies, firewalls, and restrictive gateways allow HTTPS only on TCP/443.
- Some proxies, corporate networks, and firewalls can block the test connection.
- Many clients can share the same behavior and intermediaries can change it.
- MyLeaks has no browser mapping or uniqueness database for this result.