Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cname-cloaking-blocklist
A list of domains used by tracking companies as CNAME destination when disguising third-party trackers as first-party trackers.
The default list is pretty good, but I definitely recommend adding the ticked ones from [firebog](https///firebog.net), I would also recommend applying the regex blacklists here, and finally, yeah, I’d recommend adding the cname one I put in the thread.
We've been discussing this new list source on another forum. As stated by some other users, a lot of the entries are already included in other lists, even that isn't very efficient. A long time ago, NextDNS published something similar on GitHub, after looking into that, I created and published a script that turned these entries into regex blacklist entries, which provide adequate protection against CNAME cloaking. Now the Adguard Team has published their version, however, using a similar technique to create regex blacklist entries also provides adequate protection, without adding thousands of new (some duplicate) entries to gravity. The file of interest in the entire repository is the json file, it contains the domains that would require regexes to efficiently block everything in the lists. When adding the regex entries, using a script, it turned out most of them are already covered by the NextDNS entries, only 9 additional regexes are added. For those who are interested in using the regex blacklist method, as opposed to adding big lists, you can find the entire explanation (and how to) in my pihole manual, section 15 (Deep CNAME inspection). the domain users.telenet.be may require whitelisting!