Chrome's hidden X-Browser-Validation header reverse engineered

5 dsekz 3 7/11/2025, 2:00:10 AM github.com ↗

Comments (3)

cebert · 1d ago
I have to imagine Google added these headers to make it easier for them to identify agentic requests vs human requests. What angers me is that this is yet another signal that can be used to uniquely fingerprint users.
dsekz · 1d ago
Dug into chrome.dll and figured out how the x-browser-validation header is generated. Full write up and PoC code here: https://github.com/dsekz/chrome-x-browser-validation-header

Why do you think Chrome bothers with this extra headers. Anti-spoofing, bot detection, integrity or something else?

twapi · 1d ago
Seems like they are using these headers only for google.com requests.