
A merged, deduplicated, Pi-hole-compatible domain blocklist built from 29 public sources — updated daily, mirrored, and versioned. Here’s what it is, how to use it, and how it’s built.
If you run Pi-hole (or AdGuard Home, Blocky, or any DNS-level blocker), you’ve probably done the same thing everyone does at the start: you find a list, add it, then find another list, add it, then another — and after a week you have twelve adlists, half of them overlapping by 80%, two of them abandoned, and one of them quietly returning a broken redirect page that’s silently blocking nothing.
I got tired of that. So I built a small pipeline that does it properly: one merged list, deduplicated, format-normalized, published on a stable URL, updated daily, with dated backups for rollback.
This post explains what the list is, why it’s built the way it is, how to use it, and what’s actually running behind it.
What it is
A single plain-text list of domains at:
https://www.wael.name/waelfilters.txt
Every line is a bare domain — ads.example.com, tracker.example.net — with no IP prefix, no Adblock syntax, no wildcards, no comments except a short header. That’s the format every DNS-level blocker understands natively, and the format that performs best because it requires no per-query parsing on the resolver side.
The list is regenerated once a day from 29 public blocklists, merged, deduplicated, and validated. The header tells you exactly when it was built and how many domains it contains.
Why not just subscribe to the raw lists?
Three reasons.
1. Overlap. Lists like HaGeZi, StevenBlack, OISD, and AdAway share a large amount of ground. Running all of them raw means Pi-hole downloads, stores, and re-checks thousands of duplicate domains every time gravity runs. Merging collapses that to one entry per domain.
2. Format incompatibility. Many list maintainers publish the same blocklist in five formats — hosts, Adblock, DNSMasq, wildcard, RPZ. Pi-hole only understands the first two reliably (and Adblock only on v6+, and only the basic ||domain^ syntax). If you subscribe to the wrong format, you either get nothing or you get silent over-blocking. Normalizing everything to plain domains eliminates the whole class of problem.
3. Reliability. A list that returns an HTML error page instead of its content is worse than no list at all, because you don’t notice. A merged list gives you one place to check, one build timestamp, and one number to sanity-check.
What’s in it
The 29 sources fall into three rough categories:
Ads and trackers — KADhosts, AdAway, AdGuard DNS filter, Easylist, EasyPrivacy, pgl.yoyo, anudeepND’s adservers, the firebog Admiral and Prigent-Ads lists, FadeMind’s Spam / UncheckyAds / 2o7Net, hostsVN, frogeye’s first-party trackers, HaGeZi Pro, StevenBlack’s unified hosts, OISD Big, and GoodbyeAds.
Malware, phishing, and stalkerware — DandelionSprout’s AntiMalware list, Prigent-Crypto, FadeMind’s add.Risk, Phishing Army, Quidsup’s NoTrack malware list, Spam404, the AssoEchap stalkerware indicators, cyberhost.uk’s malware list, and the Blocklist Project’s Dutch phishing list.
Telemetry and spyware — WindowsSpyBlocker’s spy hosts, which blocks Microsoft telemetry endpoints that Windows and Office call home to.
The mix is deliberately weighted toward ads and trackers (that’s what most people want blocked), with enough security coverage that the list is useful on a network that also has untrained users on it.
How to use it in Pi-hole
v6:
- Open the admin panel and go to Settings → Lists.
- Click Add list.
- Address:
https://www.wael.name/waelfilters.txt - Comment:
waelfilters(or anything you’ll recognize) - Save, then click Update gravity or run
pihole -g.
v5:
- Group Management → Adlists, add the URL in the Address field.
- Tools → Update Gravity, or run
pihole -g.
Pi-hole will pull the list on its next gravity update and re-pull it whenever gravity runs again. If you want it refreshed on a tighter schedule than your Pi-hole’s default (weekly on most installs), either change Pi-hole’s own gravity cron or add an extra entry that runs pihole -g daily.
Also works with
Because the file is plain domains, it’s not Pi-hole-specific:
- AdGuard Home — add the URL under Filters → DNS blocklists → Add blocklist → Add a custom list.
- Blocky — reference the URL in your
config.ymlunderblocking.blackLists. - Diversion (Asuswrt-Merlin) — add the URL to the custom list sources.
- dnscrypt-proxy — list it under
blocked_names.blocked_names_fileafter downloading.
Anything that reads a hosts-format or plain-domain list will take it.
Caveats worth knowing
- It’s a blocklist, not a cure. DNS filtering stops a lot of ads and trackers, but nothing that’s served from the same domain as the content you’re loading. Pi-hole is one layer; browser extensions, uBlock Origin, and DNS-over-HTTPS for outbound traffic are complementary layers.
- False positives happen. Every list in the merged set occasionally blocks something legitimate. If a site or app breaks, check the Pi-hole query log for the blocked domain, then add it to Pi-hole’s allowlist. The override is instant and doesn’t require touching the list itself.
- Not tuned for aggressive blocking. The mix leans toward “normal use, few complaints” rather than “block everything that looks suspicious.” If you want a harsher list, swap the base for a more aggressive set or add HaGeZi’s Ultimate variant alongside it.
- Refresh cadence. The list updates once a day. If you want it fresher, point Pi-hole at it more often, or pull it more often on the server side — nothing in the pipeline assumes a daily interval.
The short version
If you’re running Pi-hole or any other DNS-level blocker and you don’t want to maintain a stack of overlapping adlists, the list is at:
https://www.wael.name/waelfilters.txt
Add it as an adlist, run gravity, done. The build date and domain count are in the first few lines of the file, so you always know exactly what you’re running.
If you find it useful, or if it breaks something on your network that it shouldn’t, the contact details on wael.name are the right place to report it.
Leave a Reply