Spoofing and lie detection (signals)
Checks whether language, resolution, OS or browser values were faked and whether an ad blocker is on.
In one line
Can check whether your browser settings were faked or an ad blocker is on
Checks whether language, resolution, OS or browser values were faked and whether an ad blocker is on.
Compares claimed values with probed ones to spot people using privacy tools or anti-detect browsers. The result becomes a fingerprint signal in itself.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Compare your claimed language, screen size and system with what the browser actually shows
- Tell if an ad blocker is running
- Spot privacy tools and anti detect browsers
- Add the result to a profile it builds about your device
It cannot
- Ask your permission first
- Change your settings or turn your ad blocker off
- See your name or account by itself
- Be stopped by a browser pop up, since none exists
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | Fingerprint2.js style checks: liedLanguages, liedResolution, liedOS, liedBrowser, adBlockInstalled |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| 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
- Compare navigator.languages with language
- Compare screen sizes with available sizes
- Compare UA OS with platform and touch
- Compare UA browser with feature probes
- Probe for ad blocker bait elements
Data you get
What comes back: Five flags
Shape: object
How often: per page
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
adBlockInstalled | boolean | None | Not listed | Not listed |
liedLanguages | boolean | None | Not listed | Not listed |
liedResolution | boolean | None | Not listed | Not listed |
liedOS | boolean | None | Not listed | Not listed |
liedBrowser | boolean | None | Not listed | Not listed |
Technical limits
- Cannot tell which tool caused the mismatch
The story
What it is
A script checks whether your browser's reported language, screen or system were faked, and whether an ad blocker is on.
For you
You never see it. The site quietly checks that the story your browser tells is consistent. If it looks faked, you may get an extra check, a CAPTCHA, or a blocked checkout with no clear reason.
For makers
Fraud and bot teams use it to catch people who hide behind fake settings. Ad networks use it to spot ad blockers and bots. It also lets trackers notice who is trying to avoid them.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A fraud tool sees a browser claiming to be an iPhone but acting like a Linux server, and flags it as a bot. | FingerprintJS, Akamai Bot Manager |
| payments | Fraud checks compare your reported time zone, language and device. A mismatch can send an order for manual review. | Stripe Radar |
| ads | An ad network tests for fake traffic. If the browser lies about its screen size, the click is not billed to the advertiser. | None named |
| games | A free to play browser game bans players who fake their device to farm rewards many times. | None named |
| news | A news site detects an ad blocker and shows a polite wall asking you to turn it off or subscribe. | None named |
| shopping | A ticket site spots scalper bots that fake many different devices to grab seats, and lets real fans through. | Ticketmaster |
| analytics | Analytics tools filter out visits where values were spoofed, so charts are not full of fake visitors. | None named |
Risks
- Privacy tools can look suspicious
- False alarms block real people
- Can single out people who hide
Good uses and abuse
Legitimate uses
- Bot detection
Known abuse
- Singles out privacy tool users
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 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 |
A real example: LinkedIn
signals key in the collector returns adBlockInstalled and the four lied flags (verified in the snapshot).
Related capabilities
Related
- APFC / DNA device fingerprint (abuse prevention features). Can collect about 48 device traits and send them in secret with later requests
- Ad blocker detection. Can guess whether you use an ad blocker, by checking if its bait ads vanish
Sources
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
- BrowserGate: how it works (48 feature table)
How well checked: Checked against real behavior.