AI Blocklist for Pi-hole and AdGuard Home
Most "AI blocklists" you find hide AI images from search results. They do nothing about the AI browsers and agents now acting with your users' logins.
Load a list built for agents into the DNS server you already run, and keep it current every day.
# AdGuard Home: adblock-style rules ||manus.im^ ||browser-use.com^ ||glama.ai^ # Pi-hole: hosts format 0.0.0.0 manus.im 0.0.0.0 browser-use.com 0.0.0.0 glama.ai
AI Agent Blocklist for Pi-hole and AdGuard Home
2,600+ AI agent and AI browser domains in hosts, plain domain and adblock-style formats, each with a risk grade, updated every day.
Three different things called an "AI blocklist"
Search for an AI blocklist for uBlock Origin, uBlacklist, AdGuard or Pi-hole and you get lists with very different goals. Pick the one that matches your problem.
Hide AI content in search
Community lists, some with "huge" in the name, that hide AI-generated images and content farms from search results in uBlock Origin or uBlacklist.
Good for: people who want cleaner search pages.Block AI chat sites
Short lists of well-known chatbot domains. They stop a browser tab from opening a chat page, and little else.
Good for: a quick block on a few big names.Block AI agents and browsers
Domains that AI browsers, agent extensions, desktop agents, MCP hubs and agent platforms need to act. This is what the AI Agent Blocklist covers.
Good for: stopping software that clicks, reads and sends for the user.The problem: agents act, ad blockers only filter pages
An AI agent is not an ad. It is a program with the user's sessions. It reads your mail, opens admin pages and submits forms, guided by its maker's service. A content filter inside one browser never sees most of that.
Live logins
AI browsers act inside the user's signed-in email, CRM and cloud storage.
Hidden prompts
Researchers showed in 2025 that hidden page text could steer an AI browser to read a one-time code from email and post it out.
Tool sprawl
MCP servers and agent plugins arrive from public hubs with no review. One fake package in 2025 copied every email sent through it.
Outside the browser
Desktop agents and coding CLIs run as their own processes. A browser extension cannot touch them.
uBlock Origin, uBlacklist or a DNS server?
Browser extensions are personal tools. Pi-hole and AdGuard Home sit on the network and answer for every device. For an office, a school or a home lab with many devices, that difference decides everything.
| uBlock Origin | uBlacklist | Pi-hole | AdGuard Home | |
|---|---|---|---|---|
| Where it runs | One browser profile | One browser, on search pages | Your DNS server | Your DNS server |
| Covers other browsers and apps | No | No | Yes, any device using it | Yes, any device using it |
| User can switch it off | Yes | Yes | Not without changing DNS | Not without changing DNS |
| Sees desktop agents and CLIs | No | No | Their lookups, yes | Their lookups, yes |
| Rule style for our list | Network filters | Site match patterns | Hosts or plain domains | Adblock-style rules |
| Per-device logs | No | No | Query log | Query log |
Since Chrome 138 in July 2025, Chrome runs only extensions built on the newer Manifest V3 format. In Chrome, uBlock Origin Lite is the version that runs; Firefox still runs the classic uBlock Origin.
Who runs into this first
Pi-hole and AdGuard Home are no longer only home tools. They run in small offices, school buildings, branch sites and labs, often looked after by one person.
Small offices
No secure web gateway, one DNS server, and staff who try every new AI browser they read about. DNS is the only control that covers every device.
Schools and libraries
Shared and guest devices where nobody can install policies. A network block is the one rule that reaches them all.
Branch and lab networks
Test benches and build machines where coding agents and MCP servers appear without a ticket.
IT teams of one
No time to track hundreds of new agents a month by hand. A daily list does that part.
Remote staff on a home lab
Work laptops on home networks that already filter through Pi-hole. The list keeps agents off those too.
MSPs
Many small sites, one list each. Our MSP plan gives separate files per client or site.
Signs your network needs an AI agent list
Open the query log before you change anything. These patterns mean agents are already in use.
- Steady lookups from one or two laptops to an AI browser's sync and agent services, all day long.
- Agent platform domains resolving overnight, when no one is at the keyboard.
- MCP hub and registry names from developer machines, such as smithery.ai or glama.ai.
- Names behind AI sidebar and agent extensions from browsers you thought were standard.
- Download hosts of new AI browsers right after launch news.
- Devices that stop querying your server at all, a hint they switched to encrypted DNS.
How we solve it: a list made for agents, in your server's format
The AI Agent Blocklist covers 2,600+ AI agent domains: AI browsers, browser agents, autonomous agents, personal assistants, agent platforms and multi-agent orchestration.
It also covers MCP servers, coding agents, deep-research, meeting, voice and sales agents and AI RPA. Every entry is checked before it enters the list, and new agents are added the day they appear, not when someone remembers to update a community file.
||manus.im^ ||skyvern.com^
For AdGuard Home. Each rule blocks the domain and all its subdomains.
0.0.0.0 manus.im 0.0.0.0 skyvern.com
For Pi-hole and any server that reads hosts files. Blocks the exact names listed.
manus.im skyvern.com
For Pi-hole subscribed lists and AdGuard Home domains-only lists. Exact names.
Risk-graded subsets
The CSV and JSON carry the tool name, category and risk grade, so you can build a "higher grades only" list for staff.
Updated every day
New AI browsers, agents and MCP servers are added as they appear. Your server picks them up on its next refresh.
Device files too
5,300+ extension, app and process identifiers for browser policies and MDM, for what DNS cannot reach.
Add the AI blocklist to Pi-hole and AdGuard Home
Use the address of the file from your download access, or host the file on an internal web server and use that address. Menu names change between versions, so check the current admin console of your install.
Pi-hole
- Open the web interface and go to the subscribed lists page (Lists in Pi-hole v6, Adlists in v5).
- Paste the address of the plain domain or hosts file, add a comment such as "AI agents", and add it as a blocklist.
- Assign the list to the groups that should get it, for example Staff and Guests, and leave approved devices out.
- Update gravity so the list loads: use the Update Gravity tool in the interface, or run pihole -g.
- Pi-hole refreshes lists weekly by default. Add a daily job that runs pihole -g so new agents arrive in a day, not a week.
- Test from a client: a listed name should get Pi-hole's block answer.
AdGuard Home
- Open Filters, then DNS blocklists, then Add blocklist and Add a custom list.
- Name it "AI agents", paste the address of the adblock-style file, and save.
- Go to Settings, then General settings, and set the filters update interval to 24 hours. In the config file this is filters_update_interval, in hours.
- Put exceptions for approved tools in Filters, then Custom filtering rules, as @@||approved-tool.example^.
- Limit a rule to some devices with the $client modifier, by IP, CIDR range or client name.
- Test from a client and check the query log shows the block.
Format matters in AdGuard Home: ||example.org^ blocks subdomains, while hosts lines and plain domain lines block only the exact name. Use the adblock-style file there.
Exceptions, groups and wildcards
A block that ignores the tools people are allowed to use creates tickets on day one. Plan exceptions before you switch the list on.
| Task | Pi-hole | AdGuard Home |
|---|---|---|
| Allow one approved AI tool | Add its domains to the allowlist. Allowlist entries win over subscribed blocklists. | Custom rule @@||tool.example^, which also covers its subdomains. |
| Different rules for staff and guests | Groups: assign the list and the clients to groups. | $client modifier on rules, or per-client settings in Settings, then Client settings. |
| Block every subdomain of one domain | A regex deny rule, for example (\.|^)manus\.im$ | Built in with ||manus.im^ |
| Make your own rule win | Exact allow and deny entries rank above subscribed lists. | $important raises a rule above others, even basic exceptions. |
| Apply changes | pihole -g for lists; pihole reloadlists after database edits. | Saved rules apply right away; lists on the next refresh. |
List added but nothing blocked? Check these first
Most "the AI blocklist does not work" reports come down to one of these. Work down the list in order.
- The list loaded with zero entries. Open the lists page and look at the domain count and status. An address that needs a login or returns an error page gives an empty list.
- Wrong format for the server. AdGuard Home needs the adblock-style file to cover subdomains. Pi-hole reads the plain domain or hosts file.
- Gravity or filters not refreshed. In Pi-hole run pihole -g; in AdGuard Home use the check for updates button on the blocklists page.
- The client is not using your server. Check the query log for the device's address. No entries means it resolves elsewhere.
- The browser uses DNS over HTTPS. Disable it by policy and test again.
- An allow rule wins. A broad allowlist entry or exception rule may cover the name you expect to be blocked.
- A cached answer. The device or browser may hold an earlier answer for a few minutes. Flush the local cache or wait, then retest.
Read the query log once a week
The blocklist also works as an inventory. Ten minutes a week in the query log tells you which agents people want and who needs a conversation.
| What to look at | What it tells you | What to do |
|---|---|---|
| Top blocked AI agent domains | Which agents people keep trying | Decide: approve one with controls, or explain the block |
| Clients with the most AI blocks | Devices with an agent installed and retrying | Remove the app with your device tools |
| New names in the list's hits | Agents that appeared since last week | Check your list of AI browsers and policies |
| MCP hub lookups | Developers adding tools to coding agents | Agree an approved set; see blocking MCP servers |
| Silence from a device | DNS sent somewhere else | Close the encrypted DNS gap |
Unapproved AI use is rarely malicious. It is people trying to save time. Our guide to shadow AI agents covers how to turn what you see in the log into a short approved list.
What to block, what to watch, what to allow
Use the category and risk grade in the CSV to make two or three lists instead of one big switch.
- AI browsers and browser agents
- General autonomous agents
- MCP hubs and registries nobody approved
- Higher risk grades in every category
- Coding agents on developer machines
- Meeting and voice agents
- Deep-research agents
- Agent-building platforms
- Your approved AI assistant
- Licensed coding tools
- Internal agents on your domains
- Time-limited exceptions
Close the gaps around your DNS server
Pi-hole and AdGuard Home only see what is sent to them. These four gaps make a good list look broken.
Browser DNS over HTTPS
Turn it off with browser policy, for example DnsOverHttpsMode in Chrome and Edge, and answer the Firefox canary domain with NXDOMAIN.
Other resolvers
On the router or firewall, allow outbound DNS only from your Pi-hole or AdGuard Home. Drop the rest.
Laptops away
Off the network, your server is not asked. Use a VPN that carries DNS, or device controls through Intune.
AI built into allowed sites
AI features inside search or office suites share domains you need. Turn them off with Chrome AI policies.
Installed apps
A blocked agent stays on disk. Remove AI browsers with your device tools; see removing AI browsers.
Extensions
Block agent extensions by ID in browser policy. See blocking AI browser extensions.
For resolvers other than these two, see our general guide to blocking AI agents with DNS.
Give your Pi-hole or AdGuard Home a list that knows agents
One subscription, every format your DNS server reads, refreshed daily. Download access is set up within one business day of an order.
- Adblock-style rules for AdGuard Home
- Hosts file and plain domain list for Pi-hole
- CSV and JSON with tool name, category and risk grade
- Firewall external list format and DNS filter import files
- Extension and app identifiers for browser policies and MDM
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Questions about AI blocklists for Pi-hole, AdGuard and uBlock Origin
Is there an AI blocklist for Pi-hole?
Yes. The AI Agent Blocklist ships 2,600+ AI agent and AI browser domains as a plain domain list and a hosts file, which Pi-hole reads as a subscribed list. It updates every day, so set Pi-hole to refresh daily.
Which format should I use in AdGuard Home?
The adblock-style rules. In AdGuard Home ||example.org^ blocks the domain and all its subdomains, while hosts and plain domain lines block only the exact name.
Can uBlock Origin block AI agents?
Not across an organisation. It filters requests in one browser profile the user controls. It does not see other browsers, desktop agents or coding CLIs, and an AI browser's built-in assistant is part of the browser itself.
Does uBlock Origin still work in Chrome?
Chrome 138, released in July 2025, no longer runs extensions built on the older Manifest V2 format. The classic uBlock Origin uses that format, so in Chrome people now use uBlock Origin Lite, the Manifest V3 version. Firefox still runs the classic version.
Can uBlock Origin stop the AI in Dia or other AI browsers?
No. A content blocker filters page requests. The assistant in an AI browser is built into the browser. To control Dia or similar browsers at work, block the app on devices and its services at DNS.
What is the difference between a uBlacklist AI list and an AI agent blocklist?
uBlacklist lists hide chosen sites from search results, often AI-generated content. An AI agent blocklist stops devices reaching the services AI browsers and agents need to act.
How do I allow one approved AI tool while blocking the rest?
In Pi-hole, add its domains to the allowlist, which wins over subscribed lists. In AdGuard Home, add @@||approved-tool.example^ in Custom filtering rules, optionally limited with $client.
Pi-hole, AdGuard and AdGuard Home are trademarks of their respective owners. uBlock Origin, uBlock Origin Lite and uBlacklist are the names of their respective open source projects. Dia is a trademark of its owner.
Google and Chrome are trademarks of Google LLC. Microsoft, Edge and Intune are trademarks of Microsoft Corporation. Firefox is a trademark of the Mozilla Foundation. Manus, Browser Use, Skyvern, Smithery and Glama are trademarks of their respective owners.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies or projects.