P.S.2 But as these methods of tracking are so sophisticated, one couldn't rely just on a 'mazochistic' uMatrix configuration and whatever a user says, a native 'solution' would be welcomed, where at least you know that these things and their shenanigans are being monitored and overlooked by Thanks for the informative articles, I did not know about this. about those tests, well they don't say anything to me in general, I find them too vague and thus unreliable, html5 fingerprinting is also another subject. You can read all details in the 1st link which links to brave's post and test, and I'm sure the real paper contains much more and far more juicy info, but I don't have the time to study it now.

So to overcome this with uMatrix one should block everything 1st-party, have the domain list always expanded, check the subdomains if they include a CNAME redirection with the drill command for example, then leave their scripts blocked. The difference between a newer version of uBlock for Firefox and an older one for it and the Chromium browsers, is that because of Firefox's API it can reveal the CNAME redirections and block them by default now, making it easier for the user, while in uMatrix if you don't block 1st-party scripts by default (which usually nobody does), a subdomain of it (for which you have also most probably accepted a cookie) can use a CNAME and redirect you to another url that tracks you, with its script or with the shared cookie. supported) less granular and less verbose (& abandoned) uMatrix now -it used to be the ad-block part of the 2 contained in HTTP-Switchboard as we know- so they are both content blockers, so imo what is said there applies to both, it's just that with uMatrix you have more power to overcome the hurdles, but you have to do it manually which can become a real pain. Tl dr: you can do it with uMatrix (I think and I believe I am right) but it can be a pain.

Most content blockers distinguish between first and third party resources, and CNAME tracking uses this to avoid detection. And Internet marketing companies may use CNAME cloaking to avoid detection by content blockers, regardless of whether they are integrated in the browser natively, provided by browser extensions, or through other means such as the HOSTS file or DNS.ĬNAME tracking, also called CNAME cloaking, works through redirects by using subdomains of the main domain which are then redirected automatically to a tracking domain.

Adguard theregister