- cname-cloaking-blocklist VS pihole-regex
- cname-cloaking-blocklist VS cname-trackers
- cname-cloaking-blocklist VS Filterlist-for-AdGuard-or-PiHole
- cname-cloaking-blocklist VS 1Hosts
- cname-cloaking-blocklist VS smashblock
- cname-cloaking-blocklist VS trackerslist
- cname-cloaking-blocklist VS NextDNS-Config
Cname-cloaking-blocklist Alternatives
Similar projects and alternatives to cname-cloaking-blocklist
-
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.
-
Filterlist-for-AdGuard-or-PiHole
Discontinued A very aggressive filter-list that consolidates over 370 lists for use in AdGuard Home, Pi-Hole or similar.
-
smashblock
📡 🛡️A self-updating extensive blocklist filter for AdGaurd. Be sure to 🌟 this repository for updates!
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
cname-cloaking-blocklist reviews and mentions
-
Disguised trackers are blocked regardless of toggle (which is a good thing)
So nextdns’s third party disguised trackers is actually really tiny of a list, like 30 domains. (Im trying to add more so it has the same amount of cname’s blocked as adguard). Anyways, the reason why the list is so tiny is because it uses wildcard logic so all subdomains get blocked. It already uses some of the cname companies that adguards cname-tracker list uses but not all. Hopefully my pull request can get merge eventually because then the setting will be a little bit more effective
-
New Adguard CNAME Tracker List that works on Pi-hole!
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!
Stats
nextdns/cname-cloaking-blocklist is an open source project licensed under MIT License which is an OSI approved license.
Popular Comparisons
Sponsored