Every major AI chatbot has web interfaces, API endpoints, mobile apps, and browser extensions your users can reach. Block them all with our daily-updated domain lists covering 17,410+ AI-tool domains.
AI chatbots are the single largest vector for unauthorized data exfiltration in the modern enterprise. Unlike traditional SaaS tools, they require no procurement review — any employee can access them in seconds.
Employees paste proprietary code into ChatGPT to debug it. That code leaves your network and enters a third-party system.
Users upload financial spreadsheets to Claude or feed draft merger agreements to Gemini for summarization.
Terms of service may permit the provider to use submitted content for model training. Your data could influence future model outputs.
Pasting regulated data into a chatbot constitutes a compliance violation under each of these frameworks.
| Regulation | Sector | Penalty | Key Risk |
|---|---|---|---|
| HIPAA | Healthcare | Up to $1.5M per violation category | No major chatbot offers BAAs for consumer chat interfaces |
| SOX / GLBA / SEC | Financial Services | Regulatory action + fiduciary breach | Fiduciary obligation to control customer financial data flows |
| GDPR | Any (EU data subjects) | Up to 4% of global revenue | No valid legal basis or DPA for chatbot processing of personal data |
Blocking a chatbot by its primary domain alone is insufficient. Each service operates across multiple domains — web interfaces, API endpoints, CDN assets, authentication services, and ancillary properties.
openai.com
chat.openai.com
chatgpt.com
api.openai.com
cdn.oaistatic.com
auth0.openai.com
platform.openai.com
claude.ai
anthropic.com
api.anthropic.com
console.anthropic.com
docs.anthropic.com
gemini.google.com
bard.google.com
generativelanguage.googleapis.com
aistudio.google.com
deepmind.google
deepseek.com
chat.deepseek.com
api.deepseek.com
coder.deepseek.com
platform.deepseek.com
perplexity.ai
api.perplexity.ai
copilot.microsoft.com
copilot.cloud.microsoft
sydney.bing.com
character.ai
beta.character.ai
pi.ai
heypi.com
inflection.ai
meta.ai
llama.meta.com
chat.mistral.ai
mistral.ai
api.mistral.ai
Deploy this hosts-format blocklist directly to workstations or import it into DNS sinkhole solutions. Each domain resolves to 0.0.0.0 for immediate connection failure instead of timeout.
# AI Chatbot Blocklist — Hosts File Format # Source: aitoolsblocklist.com | Updated daily # ChatGPT (OpenAI) 0.0.0.0 openai.com 0.0.0.0 chat.openai.com 0.0.0.0 chatgpt.com 0.0.0.0 api.openai.com 0.0.0.0 cdn.oaistatic.com 0.0.0.0 auth0.openai.com 0.0.0.0 platform.openai.com # Claude (Anthropic) 0.0.0.0 claude.ai 0.0.0.0 anthropic.com 0.0.0.0 api.anthropic.com 0.0.0.0 console.anthropic.com # Gemini (Google) 0.0.0.0 gemini.google.com 0.0.0.0 bard.google.com 0.0.0.0 generativelanguage.googleapis.com 0.0.0.0 aistudio.google.com # DeepSeek 0.0.0.0 deepseek.com 0.0.0.0 chat.deepseek.com 0.0.0.0 api.deepseek.com # Perplexity 0.0.0.0 perplexity.ai 0.0.0.0 api.perplexity.ai # Microsoft Copilot 0.0.0.0 copilot.microsoft.com 0.0.0.0 copilot.cloud.microsoft # Character.ai / Pi / Meta AI / Mistral 0.0.0.0 character.ai 0.0.0.0 beta.character.ai 0.0.0.0 pi.ai 0.0.0.0 heypi.com 0.0.0.0 inflection.ai 0.0.0.0 meta.ai 0.0.0.0 llama.meta.com 0.0.0.0 chat.mistral.ai 0.0.0.0 mistral.ai 0.0.0.0 api.mistral.ai
For BIND, Unbound, or commercial DNS resolvers with RPZ support, use this zone file format. RPZ supports wildcard entries that catch subdomains automatically — critical for vendors that frequently add new subdomains without announcement.
; AI Chatbot RPZ Zone File ; Add to your RPZ zone and reload BIND/Unbound ; ChatGPT — wildcard catches all subdomains openai.com CNAME . *.openai.com CNAME . chatgpt.com CNAME . *.chatgpt.com CNAME . cdn.oaistatic.com CNAME . ; Claude claude.ai CNAME . *.claude.ai CNAME . anthropic.com CNAME . *.anthropic.com CNAME . ; Gemini gemini.google.com CNAME . bard.google.com CNAME . generativelanguage.googleapis.com CNAME . aistudio.google.com CNAME . ; DeepSeek deepseek.com CNAME . *.deepseek.com CNAME . ; Perplexity / Copilot / Character.ai / Pi / Meta / Mistral perplexity.ai CNAME . *.perplexity.ai CNAME . copilot.microsoft.com CNAME . character.ai CNAME . *.character.ai CNAME . pi.ai CNAME . heypi.com CNAME . meta.ai CNAME . chat.mistral.ai CNAME . *.mistral.ai CNAME .
Most administrators start by blocking web interfaces — the URLs users type in their browsers. This handles visible usage but leaves API endpoints wide open.
Blocks browser-based access to chat.openai.com, claude.ai, and similar URLs. Handles the most common access method for non-technical users.
An employee who finds the web UI blocked can install a Python package, set an API key, and access the same model through api.openai.com — a completely different domain.
| Chatbot | Web Interface | API Endpoint | CDN / Auth |
|---|---|---|---|
| ChatGPT | chat.openai.com, chatgpt.com | api.openai.com | cdn.oaistatic.com, auth0.openai.com |
| Claude | claude.ai | api.anthropic.com | console.anthropic.com |
| Gemini | gemini.google.com | generativelanguage.googleapis.com | aistudio.google.com |
| DeepSeek | chat.deepseek.com | api.deepseek.com | platform.deepseek.com |
Gemini's API lives on generativelanguage.googleapis.com — a subdomain of the shared Google infrastructure domain. Blocking all of googleapis.com would break legitimate Google services, so you must target the specific AI subdomain.
Block these first — the most common access method. Covers chatgpt.com, claude.ai, gemini.google.com, and similar browser-based chat UIs.
Developers and power users access models via api.openai.com and api.anthropic.com. These must be blocked independently from web UIs.
Supporting infrastructure for assets, authentication, and streaming. ChatGPT loads JavaScript from cdn.oaistatic.com; login flows use auth0.openai.com. A complete block covers primary, API, CDN, and auth domains — otherwise partial functionality or confusing errors remain.
Every major AI chatbot now ships a mobile app. Mobile apps bypass web-based blocking because they connect directly to API endpoints, not through a browser.
Combine DNS-level blocking with MDM policies that prevent installation of specific apps on managed devices.
Use Jamf, Intune, or Mosyle to create an app restriction profile. Block App Store identifiers: ChatGPT (id6448311069), Claude (id6473753684), and Gemini.
Use managed Google Play configuration to exclude specific app package names from the allowed list. Prevents installation regardless of network configuration.
The ChatGPT browser extension and dozens of third-party AI assistants on the Chrome Web Store provide chatbot access from within the browser — without navigating to a blocked website.
The built-in Copilot sidebar is not a traditional extension. It must be disabled via a separate Group Policy setting (HubsSidebarEnabled), not the extension blocklist.
Even with chatgpt.com blocked at the network level, a browser extension can interact with the model through its sidebar interface using its own network calls to API endpoints.
# Windows Group Policy: Block AI chatbot browser extensions # Deploy via GPO or Intune configuration profile # Chrome — ExtensionInstallBlocklist (Registry) HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist "1" = "obdikmjfinmclgklelghjpigpheblkol" # ChatGPT extension "2" = "jgeljgmpcnhpfacijbdnillaoelpmank" # Claude extension "3" = "efbjaemollihicpgegoailnlhmpakfhb" # Perplexity extension # Edge — same registry path, different key HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallBlocklist "1" = "obdikmjfinmclgklelghjpigpheblkol" # Edge — Disable built-in Copilot sidebar HKLM\SOFTWARE\Policies\Microsoft\Edge "HubsSidebarEnabled" = dword:00000000 "CopilotPageContext" = dword:00000000 "CopilotCDPPageContext" = dword:00000000
ExtensionInstallAllowlist to permit only approved extensions and deny everything else. This is more secure than blocklisting individual extensions but requires more administrative effort to maintain.Hosts files, RPZ zones, firewall EDLs, MDM profiles, and extension policies all stay current from one daily-updated source.
DNS-level blocking is the most effective single layer of defense against AI chatbot access. Every device on the network is affected regardless of the application used.
Supports custom blocklists in hosts-file and DNSBL formats. Host our hosts-format export (from your account downloads page) on an internal web server, add it as a blocklist source, and Pi-hole fetches the updated list on its configured schedule.
Supports the same formats as Pi-hole and additionally supports DNS-over-HTTPS and DNS-over-TLS upstream configurations that coexist with local blocklists.
# Pi-hole / dnsmasq: Block AI chatbot domains # Add to /etc/dnsmasq.d/ai-chatbots.conf # ChatGPT address=/openai.com/0.0.0.0 address=/chatgpt.com/0.0.0.0 address=/oaistatic.com/0.0.0.0 # Claude address=/claude.ai/0.0.0.0 address=/anthropic.com/0.0.0.0 # Gemini address=/gemini.google.com/0.0.0.0 address=/bard.google.com/0.0.0.0 address=/generativelanguage.googleapis.com/0.0.0.0 # DeepSeek / Perplexity / Copilot / Others address=/deepseek.com/0.0.0.0 address=/perplexity.ai/0.0.0.0 address=/copilot.microsoft.com/0.0.0.0 address=/character.ai/0.0.0.0 address=/pi.ai/0.0.0.0 address=/heypi.com/0.0.0.0 address=/meta.ai/0.0.0.0 address=/mistral.ai/0.0.0.0 # Restart dnsmasq to apply # sudo systemctl restart dnsmasq # Pi-hole: alternatively, use our hosts-format export from your account # downloads page, or build one from the API CSV filtered to chatbot categories: # curl -s -H "X-API-Key: YOUR_API_KEY" \ # "https://www.aitoolsblocklist.com/api/database/?action=download_database" \ # | awk -F',' '$2 == "Text & Language" {print "0.0.0.0 " $1}' > ai-chatbots-hosts.txt # Host the file on an internal web server, then Settings → Blocklists → Add URL
*.openai.com catches every current and future subdomain.Only blocks traffic that traverses the firewall. Users on VPN split-tunnel configurations who route DNS queries through a different resolver are unaffected.
Only blocks traffic that flows through the proxy. Many AI desktop clients and CLI tools ignore system proxy settings entirely.
When all devices must use your internal resolvers, DNS blocking provides a universal layer that is difficult to circumvent without deliberate effort.
Determined users will try to circumvent chatbot blocking. The most common techniques are DNS-over-HTTPS (DoH), VPN/proxy services, alternative DNS resolvers, and AI chatbot aggregator sites.
Block outbound access to known DoH resolver IPs (1.1.1.1, 8.8.8.8, 9.9.9.9, 208.67.222.222) on TCP port 443.
Set the DnsOverHttpsMode policy to off to prevent encrypted DNS queries that bypass your internal resolvers.
Set network.trr.mode to 5 (disabled) via the Enterprise Policy engine to force standard DNS resolution.
Disable DoH in browsers via Group Policy. Block outbound connections to known DoH resolver IPs at the firewall. Force all DNS queries through your internal resolvers where the chatbot blocklist is enforced.
Block known VPN provider IP ranges and commercial proxy services at the firewall. Use EDR to detect VPN client software on managed endpoints. Monitor for sustained TLS connections to unclassified IP addresses that may indicate tunnel traffic.
Hundreds of third-party websites proxy AI chatbot APIs behind their own domains — offering "free ChatGPT" or "unblocked AI chat." Our blocklist includes these aggregator and proxy domains in addition to the primary chatbot domains, covering a bypass vector that manual lists always miss.
Configure your DNS sinkhole and firewall to log all blocked AI chatbot queries. Forward these logs to your SIEM and set alerts for users with high block counts — they may be actively searching for bypass methods. Correlate with EDR telemetry for a complete picture.
The static blocklist you build today will be incomplete within a week. New AI chatbots launch constantly, and existing ones add domains without announcement.
Our pipeline scans 300,000+ newly registered and updated domains every day against a classifier trained on a 102-million-domain corpus.
When a new chatbot launches or an existing one adds a domain, the classifier detects, verifies, and adds it to the feed — typically within 24 hours.
Every supported format — hosts file, RPZ zone, JSON export, CSV (API download and export), firewall EDL — updates simultaneously. Your blocking infrastructure stays current regardless of integration method.
Download the free sample to test in your environment today. Or tell us your blocking requirements and we will provide a comprehensive chatbot domain feed within 24 hours.
Tell us about your environment and blocking requirements. We will provide a comprehensive chatbot domain list within 24 hours.