Skip to Content
Platform.Ontology

HTTP/2 connection fingerprint (Akamai)

HTTP/2 settings, window updates and header order differ by browser and are readable by the server.

Used to track youNetwork and connectionHTTPWeb browsersWhen the page loads

In one line

Can tell which browser or tool you use from how your connection starts up

HTTP/2 settings, window updates and header order differ by browser and are readable by the server.

Akamai's fingerprint (Black Hat EU 2017) joins SETTINGS values, WINDOW_UPDATE, PRIORITY frames and pseudo-header order. Chrome sends m,a,s,p, Firefox m,p,a,s and Safari m,s,p,a; Go and Python clients differ visibly.

What it can and can't do

What the user does: Nothing. It happens as your browser connects to the site

It can

  • Compare connection settings and header order with known browsers
  • Tell Chrome, Firefox and Safari apart from each other
  • Spot scripts and bots whose settings look different

It cannot

  • Know your name or account from it
  • Tell two people on the same browser apart
  • Apply to old HTTP/1.1 connections

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

APIHTTP/2 frame capture at the edge
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 first HTTP/2 frames
  2. Format SETTINGS|WINDOW_UPDATE|PRIORITY|order
  3. Compare to known list

Data you get

What comes back: Pipe separated string
Shape: string

FieldTypeUnitRangePrecision
akamai_h2stringNoneSETTINGS|WINDOW|PRIORITY|ORDERexact

Technical limits

  • Spoofable by custom HTTP stacks
  • Same fingerprint across browser versions sharing an engine

The story

What it is

The way your browser opens a modern web connection leaves a signature the site can read.

For you

You never see it. When you connect, your browser sends settings in a pattern that is almost the same for every copy of Chrome, Safari or Firefox. A site can tell the real thing from a lookalike script.

For makers

Security vendors like Akamai and Cloudflare use it to tell real browsers from bots that fake a browser name. It catches many scrapers and card testing tools. It also adds to a fingerprint that is hard to change.

Where you see it

TypeExampleApps
securityA bot defense compares the connection pattern with the claimed browser and challenges mismatches.Akamai, Cloudflare
shoppingA retailer stops price scrapers that pretend to be Chrome.None named
gamesA game launcher site blocks automated tools that buy limited items.None named
adsAn ad platform removes fake traffic from automation tools.None named
bankingA bank adds the connection pattern to its fraud score at login.None named
analyticsA traffic analyst uses it to name the real browser share.None named

Risks

  • Hard to change
  • Can flag privacy tools

Good uses and abuse

Legitimate uses

  • Bot detection at CDNs

Known abuse

  • Cross-session client identification

Scores

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

Sources

How well checked: Based on official documentation.

On this page