When an HTTP/2 connection opens, the client sends SETTINGS and a window update, then its first request. Browser engines differ in the values they choose, the order of frames and the arrangement of the four pseudo-headers :method, :authority, :scheme and :path. Together these form an HTTP/2 fingerprint which, like a TLS fingerprint, sites use to tell real browsers from scripts and proxies. This page connects straight to our probe and shows what the connection actually sent.
シェア
This connection
Protocol
SETTINGS entries
Connection window increment
Pseudo-header order
Testing
The probe records SETTINGS, WINDOW_UPDATE, PRIORITY and the first request’s headers as the connection opens. When the browser reuses a connection, this is still that connection’s original setup. Behind a proxy that speaks only HTTP/1.1 there is no HTTP/2 data.
Testing
Anti-abuse systems compare this order with the User-Agent. A client that claims to be Chrome but uses another order is typical of scripts with an edited User-Agent, nghttp2-based clients or a proxy that re-originates HTTP/2.
Testing
RFC 9113 deprecates HTTP/2’s own stream priorities. Older Firefox sent a set of PRIORITY frames, Chrome carries priority inside HEADERS, and newer versions use the priority request header (RFC 9218).
The fingerprint has four parts: the SETTINGS entries, the connection-level WINDOW_UPDATE increment, PRIORITY frames and pseudo-header order. It describes the HTTP client implementation; browsers of one version usually share it, and it is not a unique device identifier.
SETTINGS
ID
Name
Value
Frames at connection setup
#
Frame
Stream
Length
1
2
3
Request header order
Names only, never values
Reference: pseudo-header order by engine
Engine
Order
Chrome / Edge
m,a,s,p
Firefox
m,p,a,s
Safari and every browser on iOS
m,s,a,p
m, a, s and p stand for :method, :authority, :scheme and :path. Each engine’s network stack fixes this order and has not changed it in years; curl and other nghttp2 clients use the same order as Safari.
How to use this tool
使い方
See the Akamai fingerprint of your browser’s HTTP/2 connection: SETTINGS, WINDOW_UPDATE, PRIORITY and pseudo-header order, with the frame sequence and header order at setup, compared against the engine in the User-Agent.
Steps
The test runs when the page opens. Keep the proxy or VPN state you want to inspect.
Start with “This connection”: whether HTTP/2 was used and whether pseudo-header order matches the User-Agent.
Copy the Akamai fingerprint or its hash to compare; use SETTINGS and the frame sequence when investigating a difference.
What the result tells you
The fingerprint describes the HTTP client implementation. Browsers of one version usually share it; it is not a unique device identifier.
Behind a proxy or security product that re-originates HTTP/2, the connection recorded is theirs.
Only header names and their order are recorded, never any header value.
よくある質問4
Q1What are the four parts of the Akamai fingerprint?
The SETTINGS entries as id:value, the connection-level WINDOW_UPDATE increment, PRIORITY frames, and the first letters of the four pseudo-headers in order, separated by vertical bars. Absent parts are written 00 or 0.
Q2What if pseudo-header order does not match the User-Agent?
Chrome, Firefox and Safari each use a different order and have for years. A client that claims to be Chrome but uses another is one of the most direct signs of a script or disguised client, and can trigger challenges or blocks.
Q3Why does it say HTTP/2 was not used?
A proxy or security product may speak only HTTP/1.1 and downgrade the connection. There is then no HTTP/2 setup to observe; it does not mean the browser lacks support.
Q4Why is the result identical after testing again?
Browsers reuse an open connection, so the probe reports that connection’s original setup. A browser’s HTTP/2 fingerprint does not vary between connections anyway.