DomainKits turns domain data into answers. It does the search, retrieval, and correlation across registration pipelines (new / expired / deleted / aged), nameserver indexes, keyword registration trends, WHOIS/DNS, backlink and market datasets. Claude does the analysis.
Three jobs: finding domain opportunities, protecting your brand, and watching new registrations for threats.
- "What keywords are spiking in new registrations this week, and which spikes are real demand vs. bulk speculation?"
- "Find expired .com domains about fitness with a clean backlink profile" →
/domainkits:hunt - "Is brightpay.com worth the $3k ask? Full due diligence" →
/domainkits:analyze brightpay.com - "Which naming prefixes are trending, and where is the .com still open?"
- "Any new registrations containing 'acme' in the last 10 days?" →
/domainkits:watch acme - "The same prefix just appeared across 30+ TLDs. Is a registration pattern forming around our name?"
- "Where is 'acme' registered across TLDs, and which are still open to defend?"
- "Watch acme-related domains for WHOIS/DNS changes" (account feature)
- "New domains resembling 'ourbank' registered this week?" →
/domainkits:watch ourbank - "This lookalike is an active phishing site, what else is hosted on its nameservers?" (
ns_reversemaps the campaign) - "Any emerging keyword spikes with single-registrar, single-nameserver concentration?" (coordinated-operation signal)
- "Full WHOIS/DNS workup on this suspicious domain" →
/domainkits:analyze
In Claude Code, results compose with everything else Claude can do: write triage reports and shortlists to files, run bulk pipelines over your domain lists, schedule recurring sweeps, cross-check with web research.
| Command | For | What it does |
|---|---|---|
/domainkits:hunt [thesis] |
Investors | Opportunity discovery: expired, deleted, aged, trending, or unregistered names matching your thesis |
/domainkits:watch <brand/keyword> |
Brand & security | Sweep new registrations and TLDs for a term; triage into benign / brand conflict / suspicious; pivot suspects through their nameservers |
/domainkits:analyze <domain> |
Everyone | Full workup on one domain: registration, DNS, backlinks, value, market signals |
No command needed for ad-hoc questions. The bundled skills load automatically when a task involves domains.
- Discover: newly registered, expired, deleted, aged, and active domains; reverse-nameserver mapping; unregistered short domains
- Evaluate: backlink profiles, keyword volume/CPC, aftermarket prices
- Act: availability checks with registrar pricing, bulk checks, TLD-wide keyword availability
- Trends: keyword registration trends with quality metrics (.com share, sale-platform nameserver share, registrar/NS concentration), TLD ranking and historical trends
- Track: monitors (WHOIS/DNS/page changes) and saved strategies on your DomainKits account
The plugin ships eight open-source workflow skills that auto-activate on matching tasks:
| Skill | What it does |
|---|---|
| brand-protection | Scan typosquats and lookalike registrations around a brand, evaluate each domain individually on registration facts, offer monitoring |
| domain-analyze | Evidence-based picture of one domain: registration, DNS, backlinks, cross-TLD footprint, market context |
| domain-cma-valuation | Comparative Market Analysis against verified for-sale substitutes in the same keyword market |
| domain-generator | Creative brandable names from a keyword, concept, or taken domain, verified available at check time |
| domain-name-advisor | Naming consultation across registration, drop-catch, backorder, and aftermarket paths |
| keyword-intel | Evidence map for one keyword: search, advertiser, registration, supply, and transaction layers kept separate |
| keyword-trend-hunter | Discover registration keyword spikes and validate them against new-registration cohort signals |
| domain-market-beat | Time-bounded market briefing: sales, registration trends, and domain movements with source tiers |
Source repo (standalone install for other agents): DomainKits Skills.
domainkits plugin
├── .mcp.json → remote MCP server (https://api.domainkits.com/v1/mcp)
├── skills/domainkits/SKILL.md → core skill: tool usage guide (which tool for which task, combining and reporting results)
├── skills/<workflow>/SKILL.md → 8 bundled workflow skills (brand-protection, domain-analyze, ...)
└── commands/ → /domainkits:hunt · /domainkits:watch · /domainkits:analyze
No local code execution: the plugin is a remote endpoint, nine skill files, and three command prompts.
Claude Code (CLI, desktop, or VS Code):
/plugin marketplace add ABTdomain/domainkits-plugins
/plugin install domainkits@domainkits
claude.ai / Cowork (as a connector instead of a plugin):
- Settings → Connectors → Add custom connector
- Name:
DomainKits, URL:https://api.domainkits.com/v1/mcp - Start a new conversation
Works out of the box, no API key, no sign-up. Plans, limits, and account connection: domainkits.com/mcp. Ask Claude for your "DomainKits usage" anytime to see your tier and remaining quota.
Queries (domain names, keywords, search filters) are sent to api.domainkits.com to fetch results. The plugin reads no local files and ships no executable code.
Some workflow skills can also use tools you have connected yourself, such as a URL threat check (after asking you), and your client's web search and fetch. Those requests go to those tools, not to DomainKits.
Search and lookup tools are stateless: nothing you ask is retained. Three tools store data across sessions, and only after you enable memory:
| Tool | What it stores |
|---|---|
monitor |
The domains you watch and the results of each check |
preferences |
Your saved preferences and the memory switch |
strategy |
Strategy text you wrote, run timestamps and the most recent result |
Memory is off by default. When you turn it on, your monitors, preferences, and strategies are encrypted with AES-256-GCM and stored separately for each user, tied to your DomainKits account rather than to a single app. That is what lets you pick them up from any client connected to the same account: Claude Code, claude.ai, or another MCP client. You can delete all of it at any time by asking Claude to delete your DomainKits data (GDPR Article 17).
Responses contain no registrant personal data: WHOIS results carry registrar, dates, status codes and nameservers only.
Code: MIT (see LICENSE). Domain data is provided by DomainKits.com under its own terms; attribution required when republishing data.