Consume 17,410+ AI-tool domains as machine-readable intelligence. Daily exports in CSV, JSON, EDL, PAC, hosts, and DNS RPZ formats plus a REST API — every domain tagged with a primary category and multi-label subcategories your SOC can map to its own risk tiers.
Traditional threat feeds track malware C2 servers, phishing domains, and botnets. They are blind to the thousands of legitimate AI SaaS apps employees use daily to generate text, write code, create images, and analyze data.
AI tools are legitimate SaaS apps — not malicious. But pasting source code, contracts, or PII into them sends data through channels your threat stack doesn't track.
Your TIP doesn't know a domain is an AI tool or what category it falls into — the context you need to judge what it means for your data-protection requirements.
We publish 17,410+ AI-tool domains as a structured, categorized domain list. Each record carries the classification context your SOC needs for triage.
The feed is a plain, structured domain list — refreshed daily and published in CSV, JSON, EDL, PAC, hosts, and DNS RPZ formats plus a REST API. Every major TIP, SIEM, and SOAR platform can ingest at least one of these formats natively.
The registrable domain of the AI tool, with aliases and subdomains resolved and dead domains pruned in the daily cycle.
A primary category (one of 18) plus a multi-label categories field in "Category > Subcategory | ..." format spanning 172 subcategories.
Fields describing the kind of AI service, its language, and whether the domain is currently active — useful filters when building block policies.
If your TIP expects STIX bundles, a flat categorized domain list converts cleanly: each domain becomes one Indicator object, and our category fields become labels. You stay in control of the mapping.
# STIX 2.1 indicator generated from our CSV/JSON export # by your own conversion script — you choose the labels and risk tier { "type": "bundle", "id": "bundle--a3e2c8f1-9d4b-4e7a-b6c5-1f8d3e2a7b9c", "objects": [ { "type": "indicator", "spec_version": "2.1", "id": "indicator--7c3a9f2e-1d5b-4e8c-a3f6-9b2d4e7c1a5f", "created": "2026-07-09T00:00:00.000Z", "modified": "2026-07-09T00:00:00.000Z", "name": "AI Text Generation Tool — example-ai-writer.com", "description": "Domain of an AI-powered text generation service. Primary category: text generation (from the AI Tools Blocklist).", "pattern": "[domain-name:value = 'example-ai-writer.com']", "pattern_type": "stix", "valid_from": "2026-07-09T00:00:00Z", "labels": ["ai-tool", "text-generation", "acme-tier-high"] } ] } # "ai-tool" and "text-generation" come straight from our category fields. # "acme-tier-high" is the risk tier YOUR policy assigns to this category.
Because the source data is a flat categorized list, the conversion is mechanical and easy to audit.
Each root domain from the export becomes a STIX Indicator with a domain-name pattern.
The primary category and subcategories map to STIX labels, so analysts see what kind of AI tool the domain is.
Attach your own tier labels or ATT&CK tags per category — the guidance sections below suggest sensible defaults.
Authenticated REST endpoint returning the current list as structured JSON — the same fields as the CSV export.
Cherry-pick categories relevant to your risk profile, or ingest all 18.
Because the feed ships as plain CSV, JSON, and flat domain-list formats, the most widely deployed TIPs can ingest it with their standard import mechanisms. Configure once, and AI-tool indicators flow on the daily cycle.
| Platform | Integration Method | Key Capability | Setup Time |
|---|---|---|---|
| MISP | CSV/freetext feed URL | Auto-correlation with existing network observables | < 15 min |
| OpenCTI | CSV feed / import connector | Indicators in the knowledge graph with category labels | < 15 min |
| ThreatConnect | CSV/JSON source import | Category-to-tag mapping for playbook triggering | < 15 min |
| Anomali ThreatStream | Flat-file feed import | Automated indicator enrichment | < 15 min |
| Recorded Future | REST API pull | Custom intelligence card configurations | < 15 min |
Many organizations run lean — a SIEM plus Python scripts that pull indicators and push them into lookup tables. Our REST API and daily JSON export are built for this workflow.
Fetches the current AI-tool domain list as JSON from the REST API, authenticated with your API key.
Extracts domain, category, and subcategories from each record, then attaches the risk tier your policy assigns to that category.
Pushes enriched fields via Splunk REST API. Available as a lookup table in SPL queries. A cron job runs daily.
#!/usr/bin/env python3 # ai_feed_ingest.py — Pull the daily AI-tool domain export and push to Splunk import os import csv import io import requests API_URL = "https://www.aitoolsblocklist.com/api/database/?action=download_database" API_KEY = os.environ["AITBL_API_KEY"] SPLUNK_URL = "https://splunk.corp.local:8089" SPLUNK_TOKEN = os.environ["SPLUNK_HEC_TOKEN"] # YOUR policy: map feed categories to your own risk tiers CATEGORY_TIER = { "AI Chatbots": "high", "AI Writing Tools": "high", "AI Code Assistants": "high", "AI Image Generators": "medium", "AI Audio Tools": "medium", } # Download the current database (CSV columns: domain,category,subcategory) resp = requests.get(API_URL, headers={"X-API-Key": API_KEY}, timeout=120) resp.raise_for_status() records = list(csv.DictReader(io.StringIO(resp.text))) # Push each record to the Splunk KV store lookup table for rec in records: category = rec.get("category", "unknown") entry = { "domain": rec["domain"], "category": category, "subcategory": rec.get("subcategory", ""), # risk tier comes from YOUR mapping, not from the feed "risk_tier": CATEGORY_TIER.get(category, "review"), } requests.post( f"{SPLUNK_URL}/servicesNS/nobody/search/storage/collections/data/ai_tool_iocs", headers={"Authorization": f"Bearer {SPLUNK_TOKEN}"}, json=entry, verify=False ) print(f"Ingested {len(records)} AI-tool domains")
The core fetch-and-parse logic stays identical. Only the downstream push changes.
Replace the Splunk KV push with an Elasticsearch bulk index operation targeting your threat-intel index.
Use the Microsoft Graph Security tiIndicators API to push into Sentinel's TI data connector.
Use the Chronicle Ingestion API's UDM event format with indicator entity types.
Every indicator in the feed is backed by a continuously running classification engine — the same data, whichever of the seven delivery formats you consume.
The feed itself is a categorized domain list — it does not ship ATT&CK mappings. But the 18 categories map naturally onto specific ATT&CK techniques, and many teams tag indicators at ingest using guidance like the table below.
Applying these category-level mappings lets your SOC operationalize AI-tool intelligence within existing ATT&CK-based detection frameworks, threat-hunting hypotheses, and risk-assessment methodologies.
| AI Category | Primary Technique | Risk Rationale |
|---|---|---|
| Text generation & language tools | T1567 | Employees paste sensitive text into web-based AI interfaces — data exfiltrated via legitimate HTTPS |
| Code assistants | T1059 + T1195.002 | Generate/execute code in production environments; AI-generated code may introduce vulnerabilities |
| Data analysis tools | T1530 | Integrate with cloud storage APIs (S3, GCS, Azure Blob) to process uploaded files containing regulated data |
| Voice & audio tools | T1123 | Process recorded audio that may contain sensitive conversations |
Primary exfiltration vector for all AI-tool categories. Sensitive data leaves through legitimate HTTPS connections not flagged by traditional DLP rules.
Mapped to AI code assistants. These generate executable code employees may run in production without review — risking vulnerabilities or insecure configurations.
Mapped to AI data-analysis tools connecting to cloud storage buckets (S3, GCS, Azure Blob). Risk: employees granting AI tools API access to regulated data.
Mapped to AI tools using WebSocket, gRPC, or custom protocols. These may bypass traditional proxy inspection and require protocol-aware detection rules.
Raw domain indicators are useful for blocking. Policy decisions require context. Every record ships with classification fields your team can map to its own risk tiers for automated triage.
We are not saying these domains are "malicious." Risk tiering is about potential for data exposure based on what a category of tools does with your data.
A starting point many customers adapt — map each of the 18 categories to a tier in your own policy.
| Category | Example Tier |
|---|---|
| Consumer chatbots | High — free-form paste of text and files |
| Code assistants | High for engineering orgs — source code exposure |
| Image/video generation | Medium — less likely to receive regulated data |
| Sanctioned enterprise assistants | Low — allow-list the approved domains |
Does the tool take text input, file uploads, API integrations, or screen capture?
Review the vendor's published policy, if one exists.
SOC 2, enterprise plans, compliance posture.
Consider data-residency implications for your regulatory scope.
Whether the tool explicitly states it trains on inputs.
Building a CASB, SWG, DLP, SIEM, or SOAR product? Our feed provides a turnkey AI-tool classification layer you can embed directly — no need to build your own scanning and classification engine.
OEM feeds published under your vendor identity. Producer fields, feed names, and record descriptions carry your branding. Our infrastructure is invisible to your customers.
HTTP POST when the daily export publishes, with the newly classified records in the payload — push alerts to customers without scheduling your own polling.
Ingesting indicators is step one. The real value comes from operationalizing them across the detection-response lifecycle.
Create SIEM correlation searches matching network traffic (proxy, DNS, firewall logs) against the AI-tool indicator lookup table.
The analyst receives a context-rich alert — not a raw domain requiring manual research. What was a ten-minute investigation becomes a thirty-second triage decision.
Based on alert context, the analyst can take graduated action:
Aggregate AI-tool alert data into weekly and monthly reports for CISO-level visibility. Our category taxonomy enables granular questions:
Download a free sample of the feed to test in your TIP today. Or tell us your platform and integration requirements — we will help you get ingestion running.
Tell us your TIP platform, preferred feed format (CSV, JSON, EDL, PAC, hosts, DNS RPZ, or REST API), and integration requirements — we will help you set up ingestion.