Pi-hole Optimized Blocklists
Pre-optimized, deduplicated blocklists for Pi-hole
Looking for more features? Check out Zach's Lists — a full-featured blocklist platform with custom source selection, smart whitelisting, and multiple output formats.
Available Lists
| List | Description | Domains |
|---|---|---|
| all_domains.txt | Everything combined (except NSFW) | 2,411,965 |
| advertising.txt | Ad networks & services | 98,381 |
| tracking.txt | Analytics & telemetry | 8,640 |
| malicious.txt | Malware, phishing, scams | 1,960,831 |
| suspicious.txt | Potentially unwanted | 63,104 |
| comprehensive.txt | Curated multi-category | 454,814 |
| nsfw.txt | Adult content (separate) | 0 |
Note:
nsfw.txtis not included inall_domains.txtbecause it blocks legitimate adult sites. Add it separately if you want NSFW blocking.
Last updated: June 09, 2026
Quick Start
- Go to Pi-hole admin → Settings → Adlists
- Add the raw URL for your chosen list(s)
- Run
pihole -gto update
Report a Domain
Found a domain that should be blocked or a false positive? Open an issue using one of the templates:
- Block Domain — request a malicious, ad, tracking, or suspicious domain to be blocked
- False Positive — report a legitimate domain that's being incorrectly blocked
- Bug Report — report a problem with the lists or automation
The maintainer reviews each report, verifies it, and opens a PR. Once merged, the change takes effect on the next weekly update.
FAQ
What's the difference between this and Zach's Lists?
This repository provides static, pre-built blocklists updated weekly. Zach's Lists offers additional features:
- Custom source selection — pick which blocklists to include
- Smart whitelisting — regex, wildcards, subdomain patterns
- Multiple formats — hosts, plain, and Adblock syntax
- Real-time build progress
Both use the same underlying sources and are maintained by the same person.
How often are these lists updated?
Every Sunday at midnight UTC via GitHub Actions. Community-reported domains are included once their PR is merged before the next run.
Which list should I use?
- comprehensive.txt — Good balance for most users
- all_domains.txt — Maximum blocking (may cause false positives)
- Individual category lists — If you want granular control
How do community-reported domains work?
Domains reported via issues are added to custom/<category>.txt files in the repo. These are referenced as sources in blocklists.conf via raw GitHub URLs, so the optimizer picks them up on the next weekly run just like any other upstream source.
Contributing
See CONTRIBUTING.md for details on how to report domains, submit PRs, and use the automated workflows.
Sponsors
Thanks to everyone who supports this project.
One-Time
Star History
License
MIT License — see LICENCE for details.