Since a few days i get the following error when trying to visit mobile.de:
Access denied
Reference Error: 0.117a2617.1764711957.197945c0
Unfortunately, automated access to this page was denied.
If you are interested in accessing our data, please contact us
I tried different browsers (firefox, chrome, opera), deleting cookies/website data, no browser addons and using a VPN. → Did not solve my problem.
On my Laptop which is connected to the same fritzbox the website works without a problem. But if i use a Virtualbox Linux Mint instance on the laptop i once again get the same error message.
I contacted mobile.de and sent a few emails back and forth but they are just replying with generic, useless answers.
Now my desktop is a workstation with somewhat exotic hardware:
According to ChatGPT it is possible for websites to analyze my hardware and then
flag me as a “bot” because what i’m using looks more like a server than a desktop machine.
I never heard of or seen that though.
ChatGPT also suggested using LibreWolf because that would kinda “hide/fake” my hardware and sure enough that works.
When using LibreWolf i can visit mobile.de but not if i use regular firefox.
But using 2 browsers is impractical and according to ChatGPT websites can also detect how many cpu cores i have etc. and this is apparently information that LibreWolf can’t hide.
So its probably only a matter of time until this “fix” stops working.
So is this real and something new, up and coming for the year 2026?
Do i have to worry that more and more websites will adapt this kind of technology starting in 2026?
Or is something completely different going on?
But it sure looks like they really analyze visitors hardware.
With not really knowing all the details, I’m inclined to say no, your hardware processors do not make any difference here. It should not show up to the browser. Here is a comparison site (https://privacytests.org/) that lists quite a lot of things that websites try to do to get info and here is another (https://coveryourtracks.eff.org/) that should show what kind of fingerprint you leave. Problem being that there can be tactics that aren’t listed in those, of course. Also note that not all browsers are equal in covering user privacy.
For example, any Javascript that can execute multiple threads without restriction can probe how many CPUs you have (approximately). And that is just the tip of the iceberg.
Have you tried a VM on the desktop? i.e. where you can limit the available resources for the VM. However I acknowledge that a VM on the laptop was a step backwards.
Is the web site operator able to confirm that if you disable Javascript then the web site 100% will fail?
Why? I do that (more than 2 in fact) all the time, for improved resistance both to fingerprinting and compromise.
If i do the following in Firefox ESR then mobile.de works again:
1. about:config
2. privacy.resistFingerprinting -> Set to: true
3. Restart Firefox ESR
4. Navigate to "mobile.de" (or any website that blocks you based on fingerprint)
5. Delete Cookies/Website Data from mobile.de (or any website that blocks you based on fingerprint)
6. Reload Page (F5)
7. privacy.resistFingerprinting -> Set to: false
8. Restart Firefox ESR
Note that i do revert the privacy.resistFingerprinting at the end but mobile.de keeps working UNLESS i delete the cookies again.
Do you guys think they use WebGL Fingerprinting the first time someone visits their site and then set a cookie that determines if you are blocked or not?
Or do you think they go further than just looking at WebGL?
Because if it’s just WebGL i could probably fix it by using a Consumer GPU instead.
But then on the other hand for how long would this fix it until they come up with even deeper analytics…
I run Firefox permanently with privacy.resistFingerprinting set to true.
(It is most likely the case that if there is some web site that won’t work unless it is false, I would simply not use that web site. Firefox appears to offer privacy.resistFingerprinting.exemptedDomains if there were such a web site that I really really wanted to use.)
PS I also toss everything away on Firefox exit. Yes, that is a bit harsh on the internet connection, but not only is it usually better privacy and security to do that but also it can solve some weird web site problems.
1. google-chrome --disable-webgl or --disable-3d-apis
2. Navigate to "mobile.de" (or any website that blocks you based on fingerprint)
3. Delete Cookies/Website Data from mobile.de (or any website that blocks you based on fingerprint)
4. Reload Page (F5)
Disables WebGL but does not fix the problem. So they are obviously looking at more than just WebGL when creating their fingerprint.
Which brings me back to the original question if i have to fear being kicked out of many websites in the future because of my unusual hardware being flagged as a fraudster of bot.
Unfortunately it looks like the cookies from mobile.de only last for about 1 day. So i would have to do this over and over again or keep the settings “true” permanently which probably risks compatibility problems with other websites. Because of that i think i will just use LibreWolf for browsing mobile.de at this point.
But i’m still wondering if this site is an outlier or if this is one of the “cool” new things for 2026.
Is this (fingerprinting users with their hardware) actively being pushed / sold to developers?
The only viable solutions I have found to the browser and device fingerprinting issue is running dedicated VMs via QubesOS, or SimplifiedPrivacy’s HydraVeil product which takes a unique hybrid approach.
… well, as I said, I run permanently with true and don’t particularly have a problem with web sites in general. Conversely though, I therefore can’t tell you whether false with the failure in the OP will be the cool new thing for 2026 - but then I don’t have a bot-sized rig as my desktop and FWIW mobile.de works for me.
And, as said, it looks as if you can exempt a set of other web sites from “resist fingerprinting” if you had to - however I am not doing that (no web sites are in my list to exempt).
One avenue for troubleshooting your fingerprinting (or not…) issue, would be to examine what scripts are downloaded and executed (if not blocked by NoScript/UBO and such similar extensions) at page load under the different situations you described (alternate browser, about:config mods, cookies and site data)
Hitting the F12 key inside Firefox and derived browsers will display the dev console - choose the network tab and reload. You will see all the scripts that were downloaded for that page. First thing I would look for, is to confirm whether a fingerprinting script is actually being used - because all the commonly used fingerprinting scripts are well known and due to unimaginative developers, they all say what they do in their names: fp.js, fpjs, fpjs2, fingerp.js, fingerprinting.js, etc…
This way, you could at least confirm if a known fingerprinting script is being used, or if they have a particular more sophisticated method/script/CSS/XHR/fetch/websocket for achieving their devilish task.