HostlistsRegistry
HostlistsRegistry copied to clipboard
anti-adblock blocker, I don't care about cookies
Two blocklists I'd love to see on Adguard Private DNS:
- "I don't care about cookies" blocker: https://www.i-dont-care-about-cookies.eu/abp/ and
- "Anti adblocker" blocker: https://raw.githubusercontent.com/reek/anti-adblock-killer/master/anti-adblock-killer-filters.txt
Thanks! Kris
Adguard Private DNS
- "I don't care about cookies" blocker: https://www.i-dont-care-about-cookies.eu/abp/
This list contains cosmetic filters (##.cookie-banner
) and non-hosts network filters (||example.com/files/cookie.js
); How can such list helps in a DNS blocker that only supports Hosts filters like example.com
?
2. "Anti adblocker" blocker: https://raw.githubusercontent.com/reek/anti-adblock-killer/master/anti-adblock-killer-filters.txt
Same reasons for the first list also applies to this one.
Besides that, this list has been unmaintained for 6 years, you shouldn't use such list. Did you even bother to check the last update of this list before proposing it? https://github.com/reek/anti-adblock-killer/commits/master/anti-adblock-killer-filters.txt
Doublechecking №1's syntax, only circa 113 of its ~23,000 entries would be accepted as-is by AdGuard's DNS-based tools (Listed in the dropdown button below; entries ending with .js
are excluded from the count), and it'd work on possibly only 10% of websites out there.
.cookiehub.eu
/aloofvest.com
/amp-user-notification-
/avisopcdidomi
/bosch-privacy-settings-
/bundle-consent-banner
/chickensstation.com
/childlikeform.com
/consent-banner-bootstrap
/consentcheck.de
/ConsentManager,Sticky
/cookie-banner-vue
/Cookie-GetCookieModal
/cookieconsent.klaro.
/cookiesdirective
/edgecastcdn.net
/epaas.consentdrawer.bundle
/ercookiebar.
/fearlessfaucet.com
/GDPRPanelComponent
/getCookieConsent
/handsomelyhealth.com
/hatefulrequest.com
/iwCookieBanner
/jqueryCookieGuard
/lovelydrum.com
/mdp.javascript.gdpr.min
/micado.web.dsgvo.cookie
/modal-acceptare-cookie
/ModalCookiesPrivacy.php
/new-cookie-policy.
/pleasantpump.com
/pubtech-cmp
/railwayreason.com
/superficialeyes.com
/taunton-user-consent-eu
/teenytinycellar.com
/whCookieManager
/widget-module-cookies
analytics-consent-manager.azureedge.net
api.cookielaw-script.it
api.cookielaw.eu
app.eprivacy-keeper.eu
browser-consent-front.coco.s-cloud.fi
bs-cookie.staging.springbok.agency
cc.controlcookies.com
ccm19.vucx.de
cdn.cookiecode.nl
cdn.realpeoplemedia.co.uk
cdn.truendo.com
cdn.userdatatrust.com
cdncmp.richaudience.com
choices.consentframework.com
cmp-loader.choice.faktor.io
cmp.cdntrf.com
cmp.cls.pm
cmp.dreamlab.pl
cmp.md-nx.com
cmp.mediavine.com
cmp.optad360.io
cmp.osano.com
cmp.pafo.fairbung.com
connect.danone.es
consent-manager.confirmic.com
consent-manager.metomic.io
consent-notice.magix.com
consent.23g.io
consent.scm-verlagsgruppe.de
consent.theneweuropean.co.uk
consentserve.mgr.consensu.org
cookie-bar.salessquad.co.uk
cookie.consent.is
cookieconsent.blob.core.windows.net
cookieconsent.syreta.com
cookielaw.emea.fcagroup.com
cookiemon.atcom.gr
cookiePolicyEUPopin*
cookies.ae-webdesign.com
cookies.algo.at
cookies.innershed.co.uk
dan.mgr.consensu.org
digitrust.mgr.consensu.org
etarget.mgr.consensu.org
eurocookie.galilcloud.wixapps.net
flipdish-cookie-consent*
fundingchoices.google.com
gdpr-banner.awsmpsa.com
gdpr.internetbrands.com
gemius.mgr.consensu.org
global.ketchcdn.com
inforpl.mgr.consensu.org
jquery-eu-cookie-law-popup*
js.cookietagmanager.net
jssdk.privacy.pre.schibsted.com
nexus.ensighten.com
notice.sp-prod.net
ogury.mgr.consensu.org
pdcc.gdpr.es
privacidade.api.milvus.com.br
privacy-policy.u-lab.nl
privacy.claytonhomes.com
procookie.by.nf
sddan.mgr.consensu.org
sharethis.mgr.consensu.org
shinystat.mgr.consensu.org
sibboventures.mgr.consensu.org
tag.goadopt.io
up-cookiemon.wavecdn.net
webads.mgr.consensu.org
webcache-eu.datareporter.eu
webcache.datareporter.eu
widgets.legalmonster.com
wpjslib-chunk-notification.js^
Regarding №2, the concept of anti-anti-adblock lists has pretty much been integrated into AdGuard Base Filter and uBlock Filters by now, especially in the past 2 or 3 years.
How AdGuard DNS block path like:
/amp-user-notification-
Also Google generated bad time when needed is accept pop-up to use tracking on page and AdSense (or both services can by banned for webpage/webmaster).
Believe it or not, but it does. At least it does after AdGuard Home's engine began considering an initial /
to be equivalent to ://
around a year and a half ago.
Believe it or not, but it does.
So it can block /amp-user-notification-
but not example.com/amp-user-notification-
?
On paper, yes. /amp-user-notification-
would be able to block longshot theorethical scenarios like amp-user-notification-text.com
So looks as secret wildcard syntax (but pointless if no exist these amp 3p domain with gdpr in soft implementation (don't break embedded video/posts e.g. YouTube or Twitter)).