Your customers are demanding an AI-tools category — and you don't have the domain intelligence to deliver it. We provide 17,410+ classified AI-tool domains across 18 categories, updated daily, structured for direct resolver integration.
Every use case requires the same foundation: a comprehensive, accurate, continuously-updated list of AI-tool domains mapped to functional categories your policy engine can act on.
Your DNS filtering product blocks malware, adult content, and gambling. These categories have been refined over a decade and cover the established web.
AI tools are the fastest-growing class of web applications in history. The category didn't exist at meaningful scale until 2023, and most vendors lack the classification infrastructure to populate it.
Tens of thousands of domains across 18 categories and 172 subcategories — text generation, image synthesis, code assistants, voice cloning, autonomous agents, and more.
New tools launch daily. Existing tools rebrand, merge, or migrate to new domains. A pipeline accurate last month is already missing hundreds of entries.
Our classification database spans 102 million pre-categorized domains, with roughly 300,000 newly registered domains checked and classified every day. Integrate ours and ship the AI-tools category within weeks, not years.
Category granularity is what separates a checkbox feature from a competitive differentiator in your admin console.
The minimum viable product. Lets administrators block or allow all AI tools as a group — one toggle, no granularity.
The competitive differentiator. Block AI chatbots in classrooms while allowing educational tutoring. Block code generators for finance while allowing them for engineering.
categories field. Expose as much or as little granularity as your UX supportsChatbots, writing assistants, summarizers, translation tools, grammar checkers, and content generators.
Image generators, AI art platforms, photo editors, background removers, and visual design tools.
Code completion tools, AI pair programmers, automated testing platforms, and code review assistants.
AI music generators, voice synthesizers, audio editing tools, podcast tools, and sound effect generators.
AI video generators, deepfake tools, video editors, avatar creators, and animation platforms.
AI-powered search engines, research assistants, academic tools, and citation generators.
Meeting assistants, document automation, AI scheduling, CRM copilots, and workflow automation tools.
AI data analysis tools, visualization generators, predictive analytics, and business intelligence assistants.
Autonomous AI agents, browser automation, RPA with AI capabilities, and task orchestration platforms.
AI tutoring platforms, homework helpers, study tools, language learning, and educational chatbots.
AI copywriting tools, ad generators, email marketing assistants, SEO tools, and lead generation platforms.
Medical AI assistants, drug discovery tools, diagnostic aids, clinical note generators, and bioinformatics platforms.
Model hosting platforms, inference APIs, training infrastructure, MLOps tools, and AI development frameworks.
AI companion chatbots, virtual friends, AI dating assistants, social simulation, and character interaction platforms.
AI-assisted design tools, logo generators, UI/UX assistants, 3D modeling, and creative suite integrations.
AI-powered security scanners, compliance automation, threat detection, and vulnerability assessment tools.
AI translation services, localization platforms, real-time interpretation, and multilingual content tools.
Multi-modal AI platforms, general-purpose assistants, AI aggregators, and tools spanning multiple categories.
primary_category plus a multi-label categories field in Category > Subcategory format. Your integration maps the 18 categories and 172 subcategories to your internal category IDs once — the same labels appear in each daily export.Category > Subcategory pairs separated by |, so your policy engine can match on any of them.Domains enter the feed through two complementary pipelines built on our 102-million-domain pre-categorized corpus — the same database that powers websitecategorizationapi.com.
Roughly 300,000 newly registered domains from zone files, certificate transparency logs, and registration feeds are checked and classified every day. Many turn out to be empty or parked and are excluded, so they don't inflate the database. Any domain classified as an AI tool automatically enters the feed.
A dedicated discovery pipeline monitors app directories, product-launch platforms, developer communities, academic repositories, and the open web every day. Candidate domains are classified into the 18 categories with tool name and subcategory.
Dead domains are pruned, and aliases and subdomains are resolved to their root domain. Both pipelines merge into the same daily export cycle — CSV, JSON, EDL, PAC, hosts, and DNS RPZ formats, plus the REST API.
// Classified domain record (JSON) — fields as shipped in every export { "root_domain": "chatgpt.com", "primary_category": "Text & Language", "is_active": 1, "language": "en", "ai_type": "chatbot", "categories": "Text & Language > Chatbots | General & Multi-Purpose > AI Assistants" }
The categories field is multi-label: a tool spanning several functions carries every applicable Category > Subcategory pair, separated by |. Your policy engine can block a domain when any of its labels matches a blocked category.
primary_category gives a single best-fit label for products with per-category toggles, and the is_active flag marks domains that are no longer live.The full AI-tools category, ready for your policy engine, refreshed every 24 hours.
Response Policy Zones (RPZ) are the standard mechanism for injecting policy decisions into DNS resolution. If your product is built on a standard resolver, RPZ is the native integration path.
Standard RPZ zone file available for direct download. Conforms to the RPZ specification implemented by all major resolver software.
Load the daily RPZ export onto your own primary name server and let your resolver fleet pull it via standard AXFR/IXFR zone transfer — as shown in the configuration examples below.
; RPZ zone file — AI tools category (excerpt) ; BIND, Unbound, PowerDNS, and CoreDNS all support this format $ORIGIN ai-tools.rpz.aitoolsblocklist.com. $TTL 300 ; SOA and NS records (required for zone transfer) @ IN SOA ns1.aitoolsblocklist.com. hostmaster.aitoolsblocklist.com. ( 2026070901 ; serial (YYYYMMDDNN) 3600 ; refresh 600 ; retry 86400 ; expire 60 ; minimum TTL ) @ IN NS ns1.aitoolsblocklist.com. ; Block AI chatbot domains (return NXDOMAIN) chatgpt.com CNAME . *.chatgpt.com CNAME . claude.ai CNAME . *.claude.ai CNAME . gemini.google.com CNAME . perplexity.ai CNAME . *.perplexity.ai CNAME . ; Redirect AI image tools to block page midjourney.com A 10.0.0.1 *.midjourney.com A 10.0.0.1 leonardo.ai A 10.0.0.1 *.leonardo.ai A 10.0.0.1 ; ... 17,410+ domains across 18 categories
Configuration snippets for the four most common resolver platforms. Your product's configuration interface generates these for end customers.
# BIND 9 — named.conf RPZ configuration options { response-policy { zone "ai-tools.rpz.aitoolsblocklist.com" policy nxdomain min-update-interval 300; }; }; zone "ai-tools.rpz.aitoolsblocklist.com" { type secondary; primaries { 198.51.100.10; }; file "rpz/ai-tools.db"; }; # ───────────────────────────────────── # Unbound — unbound.conf RPZ module rpz: name: "ai-tools.rpz.aitoolsblocklist.com" primary: 198.51.100.10 zonefile: "/etc/unbound/rpz/ai-tools.zone" rpz-action-override: nxdomain rpz-log: yes rpz-log-name: "ai-tools-rpz" # ───────────────────────────────────── # PowerDNS Recursor — recursor.conf lua-config-file=/etc/pdns-recursor/rpz.lua # rpz.lua: rpzPrimary("ai-tools.rpz.aitoolsblocklist.com", "198.51.100.10", { policyName="ai-tools", refresh=300 }) # ───────────────────────────────────── # CoreDNS — Corefile RPZ plugin . { rpz ai-tools.rpz.aitoolsblocklist.com { action nxdomain log } forward . 8.8.8.8 8.8.4.4 }
Every domain carries a primary category and a multi-label categories field drawn from the 18-category, 172-subcategory taxonomy. Categories are the policy knob your customers use to decide what gets blocked.
A single best-fit category per domain — ideal for products that expose a simple per-category toggle in the admin console.
The full set of Category > Subcategory pairs a domain belongs to, separated by | — for products offering granular, subcategory-level policies.
Your backend should ingest the entire feed — all domains with all of their category labels — into your category database.
When your resolver evaluates a DNS query, it checks the domain's stored category labels against the administrator's blocked-category list. No re-download needed when policies change.
Different category selections per policy — e.g., block chatbots and AI companions on the student network while allowing education and tutoring tools on the teacher network.
The AI-tool landscape is not static. New tools launch daily — some on new domains, others as AI features added to existing platforms.
Approximately 300,000 newly registered domains — sourced from zone files, certificate transparency logs, and registration feeds — are checked every 24 hours.
Each daily batch is classified the same day. Many new registrations turn out to be empty or parked and are excluded, so they don't inflate the database.
Any domain classified as an AI tool automatically enters the feed and ships in the next daily export across all delivery formats.
is_active field, so removals are explicit in the dataOur OEM license lets you embed AI-tools category data into your own product and redistribute it to all your end customers.
Whether you serve 100 small businesses or 10,000 enterprise accounts, the license cost is the same. Your growth incentive is fully aligned with ours.
We succeed when your product succeeds. No surcharges that penalize your growth.
Full API credentials, complete data dump, integration documentation, and access to our integration engineering team.
Most vendors complete integration in 2–3 weeks via RPZ or 3–4 weeks via REST API.
Choose the licensing tier that matches your needs, with daily updates delivered across all seven formats, including the REST API.
Start with a free 30-day technical evaluation. Full API access, complete dataset, and a dedicated integration engineer — no commitment required.
Tell us about your DNS filtering product and target market. We will provide API credentials, sample data, and integration documentation within 24 hours.