anti-AD: ten generated blocklist formats, and the traps between them
Aims to be the ad-filtering list with the highest hit rate in the Chinese-language region, providing precise ad blocking and privacy protection. anti-AD now supports AdGuardHome, dnsmasq, Surge, Pi-hole, Clash, mihomo, smartdns, sing-box and other network components, and is fully compatible with the list formats used by common ad-filtering tools.
At a glance
- What is it?
- anti-AD merges upstream hosts and adblock lists, deduplicates them, and publishes ten output formats for DNS resolvers and proxy clients. Two of those files live in another repository, one format breaks tools that match URL paths, and the generator is not on the default branch.
- Who is it for?
- anti-AD is worth wiring up if your traffic already passes through AdGuard Home, dnsmasq, Pi-Hole, smartdns, Surge, Clash, mihomo, or sing-box, and pointless if it does not, because the project is a list and not a resolver. Before trusting it, read discretion/README.md for the contested domains and check changelog.md rather than the Releases page, which still points at v4.3 from 2020.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- privacy-protection-tools/anti-AD10,969 ★ · +198
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| privacy-protection-tools/anti-AD | 10.8k | 11k |
198 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Blocking happens during name resolution, not while the page loads
anti-AD is a list, not a client. It works at the DNS resolution layer, which means something has to consume it that resolves names: AdGuard Home, dnsmasq and its derivatives, Surge, Pi-Hole, Clash, mihomo, smartdns, or sing-box. Dropping the file onto a machine with no such resolver achieves nothing, and installing it does not stop in-app advertising on a device whose traffic never reaches your resolver. The stated scope covers ad domains, TV box advertising, in-app ads, and a set of logging and big-data statistics sites that touch personal privacy. The output is built by merging and deduplicating well-known hosts lists, ad filter lists, and adblock lists, then putting the result through abstraction steps: proactively dropping dead domains, easylist optimization of fuzzy matching, and an enhanced black and white list mechanism. The stated goal is the highest hit rate among Chinese-language ad-filtering lists.
One file in the table will break your setup if you pick it wrong
The quick use table maps ten output files to the components they target, and two rows carry warnings that matter more than the rest. anti-ad-easylist.txt holds regular expression rules and is meant for AdGuard Home; it must not be used in AdGuard, uBlock Origin, or any tool that matches URL paths, because a specific URL can be wrongly blocked. The second row is anti-ad-surge2.txt, offered for Surge and similar tools in DOMAIN-SET format because that format performs better than anti-ad-surge.txt. The rest split along the same fault line: adblock-for-dnsmasq.conf and anti-ad-smartdns.conf are resolver configs, anti-ad-domains.txt is the plain domain list for Pi-Hole and similar tools, anti-ad-adguard.txt matches the domain part of a whole URL, and anti-ad-clash.yaml targets Clash Premium style tools.
The sing-box and mihomo files live in a different repository
Ten files are listed, but the last two are not in this repository. The raw links for anti-ad-sing-box.srs and mihomo.mrs point at privacy-protection-tools/anti-ad.github.io rather than at the anti-AD master branch, and the top-level tree confirms it: it holds adblock-for-dnsmasq.conf, anti-ad-adguard.txt, anti-ad-clash.yaml, anti-ad-domains.txt, anti-ad-easylist.txt, anti-ad-quanx.txt, anti-ad-smartdns.conf, anti-ad-surge.txt, and anti-ad-surge2.txt, with no .srs or .mrs file among them. Both are binary rule sets, so you cannot read or edit them as text, and both carry hard version floors: sing-box needs 1.10.0 or above and mihomo needs 1.18.7 or above. Check your client version against those floors before loading either file.
The generator is not on the default branch and it needs PHP 8
You cannot rebuild the lists from a clone of master. Version v4.5.1 moved the build scripts onto a separate branch so that the default branch would look cleaner, which means a checkout of master contains generated output and no tooling. The rules are not hand-maintained either, since they come from upstream lists and from issues filed by users. The generator also moved under the maintainers' feet: v4.5.2 switched the project code to PHP 8 and states plainly that older PHP versions are not fully compatible. Before that, v4.5.0 refactored the easylist-extend.php script for a threefold execution speedup and started supporting the newer AdGuard Home modifiers syntax, which the release note marks as still in testing because AdGuard Home's own parser has bugs. The consequence is that reproducing one specific published list needs the right branch, the right PHP, and tolerance for syntax the target tool may still mis-parse.
Disputed domains are collected for you to decide
Some domains look like advertising or tracking but serve other purposes as well, and blocking them causes extra problems. anti-AD does not settle that for you. The discretion directory holds a written collection of such contested domains with short explanations, and the project's position is that you add your own rules to allow or block them according to how you actually use them. That is a reasonable choice with a real cost: a false positive in this category shows up as a broken login, a dead embed, or a payment page that never loads, and nothing in the list tells you which one you hit. False kills are treated as reportable, an issue template is provided, and a QQ group numbered 716981535 is offered for faster discussion. Until you have read discretion/README.md, treat breakage on an unusual site as unresolved rather than as a resolver bug.
Aggregating upstream lists imports their maintenance status too
The credit list names the sources feeding the merge, and two entries carry their own status notes. vokins/yhosts is annotated as a source that has stopped being maintained, and notracking/hosts-blocklists-scripts is credited for supplying lists of invalid domains and invalid hosts. The rest span Adblock Plus, AdguardTeam/AdguardFilters, fanboy-annoyance, easylist.to, neoFelhz/neohosts, cjx82630/cjxlist, AWAvenue-Ads-Rule, ACL4SSR, v2fly/domain-list-community, malware-filter/urlhaus-filter, adblock-nocoin-list, CoinBlockerLists, and WindowsSpyBlocker. The project asks for review of its code and for issues covering false kills and bugs, and describes itself as a non-mainstream project that keeps every line open.
The Releases page is years behind the default branch
The repository is not archived and its last push is dated 2026-11-01, but the newest GitHub release is v4.3, tagged 2020-02-04, with v4.2.2 and v4.2.1 before it. The version history inside the README tells a later and different story, running through v4.5.2 on 2022.12.15, v4.5.1 on 2021.05.31, and v4.5.0 on 2021.05.02, with the full progression in changelog.md. The two views disagree because the release tags stopped tracking the documented versions. The consequence for an operator is that freshness cannot be judged from the Releases page; point your resolver at a raw file or at the anti-ad.net URLs instead, and read changelog.md when you want to know what changed. The tree also ships .md5 companions for anti-ad-adguard.txt and anti-ad-easylist.txt only, so integrity checking is available for those two formats and not for the dnsmasq, surge, smartdns, or clash outputs.
Editorial conclusion
anti-AD is worth wiring up if your traffic already passes through AdGuard Home, dnsmasq, Pi-Hole, smartdns, Surge, Clash, mihomo, or sing-box, and pointless if it does not, because the project is a list and not a resolver. Before trusting it, read discretion/README.md for the contested domains and check changelog.md rather than the Releases page, which still points at v4.3 from 2020.
Frequently asked questions
What is anti-AD?
It is a merged and deduplicated ad filtering list that blocks at the DNS resolution layer rather than in the browser. It targets the Chinese web and ships in ten formats covering AdGuard Home, dnsmasq, Surge, Pi-Hole, Clash, mihomo, smartdns, and sing-box.
Can anti-AD block ads permanently?
Its rules come from upstream lists and user-submitted issues. Contested domains are handled separately in the discretion directory precisely because some ad-looking domains also serve other purposes, and the README accepts false-kill reports as issues.
Does anti-AD cost anything?
The project is released under the MIT license and the files are plain text or binary rule sets you point a resolver at. The list does nothing on its own: it only takes effect once AdGuard Home, dnsmasq, Pi-Hole, smartdns, Surge, Clash, mihomo, or sing-box is configured to load it.
How does anti-AD compare to other ad blockers?
anti-AD publishes no ranking of ad blockers. It names the upstream sources it merges, including Adblock Plus, AdguardTeam/AdguardFilters, fanboy-annoyance, easylist.to, neoFelhz/neohosts, AWAvenue-Ads-Rule, and v2fly/domain-list-community, and notes that one credited source has stopped being maintained.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/privacy-protection-tools-anti-ad)Star history chart for your README
[](https://hysenlabs.com/projects/privacy-protection-tools-anti-ad)Was this useful?