| Adblocker detection | |
|---|---|
| Adblock detected: | false |
| Adblocker: | No name detected |
| Adguard UUID leak: | None detected |
| Content blocking detection | |
|---|---|
| First-party blocking: | No |
| First-party blocking (no-JS): | Nodetected |
| Third-party blocking: | No |
| HTML element hiding: | No |
| Anti Adblock defuser detection | |
|---|---|
| Redirects | |
| Script redirect: | None detected |
| Image redirect: | None detected |
| Frame redirect (Firefox): | None detected |
| XHR redirect: | None detected |
| XHR fetch defuser test | |
| XHR blocked without response: | false |
| response.url does not match: | false |
| response length is too short: | false |
What does the site do? It detect content blocker behavior (Adguard and uBlock Origin) on Chrome and Firefox which can be used for tracking and Adblock detection. Also the site can be used for testing defuser scriptlets.
What is the Adguard UUID leak? Every Browser extension has a unique identifier which getting generated with the install of a extension, the UUID. It can be used for browser Fingerprinting.
Chrome: The identifier for a specific addon is the same for every user but a site can detect Adguard as a addon.
Firefox: When a user installs a Addon a unique UUID getting generated for every user so its a very strong tracking parameter. The only way to change the UUID is a addon reinstall.
The UUID is hidden but with a small script the UUID can be leaked from the Adguard extension. With the UUID a site or tracking company can track the user around the web. The bug got reported to Adguard https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2278
Direct link to the script: https://adblock-testing.glitch.me/script.js