HTTP header order and casing
The set and order of request headers is different for each browser and HTTP library.
In one line
Can tell which browser or tool you use from the order of request headers
The set and order of request headers is different for each browser and HTTP library.
Chrome, Firefox and Safari send Accept, Accept-Language, Accept-Encoding and Sec-* headers in distinct orders; scripted clients (requests, Go, Node fetch) differ. Mismatches versus the User-Agent flag bots.
What it can and can't do
What the user does: Nothing. It happens with every page request
It can
- Compare the order and casing of header lines with known browsers
- Spot scripts and bots that use plain code libraries
- Flag a browser name that does not match the headers
It cannot
- Know your name or account from it
- See your files or other tabs
- Tell two people on the same browser version apart
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 1 | 2004-11-09 | None |
| Safari | Supported | 1 | 2003-06-23 | None |
| Safari on iPhone | Supported | 1 | 2007-06-29 | None |
| Chrome on Android | Supported | 1 | Not listed | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | Server request header parsing |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Read headers in received order
- Hash names, order and values
- Compare with User-Agent
Data you get
What comes back: Ordered list
Shape: string
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
header order | list | None | 10 to 20 names | exact |
Technical limits
- Proxies and CDNs can reorder headers
- HTTP/2 lowercases names
The story
What it is
The order of the info your browser sends to a site reveals which browser it is.
For you
You never see it. Each browser sends the same pieces in a slightly different order, like a signature. A site can tell Chrome from Firefox from a script even if the browser claims otherwise.
For makers
Bot defense vendors use header order as a quick way to catch scripts pretending to be browsers. It is also a fingerprint input, since software versions and add-ons leave marks.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bot defense checks if the header order matches the browser claim, and blocks scripts that fake Chrome. | Cloudflare, DataDome |
| games | A game login page blocks credential stuffing tools that send headers in an odd order. | Roblox |
| shopping | A sneaker or ticket site spots scalper bots by header order before the sale begins. | Ticketmaster |
| ads | An ad platform filters click fraud from scripts with the wrong header signature. | None named |
| analytics | A traffic report separates real browsers from crawlers. | None named |
| media | A streaming site stops account sharing and scraping tools by headers. | None named |
Risks
- Hard to hide
- Can flag privacy tools
Good uses and abuse
Legitimate uses
- Bot detection
Known abuse
- Client identification
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 3 | Rough identifying entropy, when known |
Related capabilities
Related
- HTTP/2 connection fingerprint (Akamai). Can tell which browser or tool you use from how your connection starts up
- Client Hints (Accept-CH, Critical-CH). Can ask your browser for extra device details such as model, OS version and screen
Sources
How well checked: Based on official documentation.