Developers & AI agents
Agent files, OpenAPI, and live tables /whois?query= and /dns?q=. JSON API uses an operator key; there is no public signup.
Agent discovery files
- llms.txt — language version index
- llms-ru.txt — full Russian description
- llms-en.txt — full English description
- ai.txt — short index for AI crawlers
- ai-ru.txt / ai-en.txt — short language-specific versions
- openapi.json — OpenAPI 3.1 (operator key required for live calls)
- agent.json — agent card
- mcp.json — no live MCP server
- sitemap.xml — sitemap
Live WHOIS and DNS tables
Live results are the query-parameter forms. /lookup/ hubs are noindex and are not the live table.
/whois?query=example.com— live WHOIS table/dns?q=example.com— live DNS table/lookup/whois/example.com— WHOIS hub (noindex), not the live table/lookup/dns/example.com— DNS hub (noindex), not the live table/check/example.com— full-check hub (noindex)/zones/ru— search in zone
Agent API
Base URL: https://domaintools.site/api/v1/
The API is on. Send X-API-Key or Authorization: Bearer. Keys are operator-issued; you cannot mint a key on this site. Missing key → 403. There is no live MCP server.
FAQ
Yes, for the JSON Agent API. The operator issues keys; there is no self-signup. Missing key → GET /api/v1/ is 403. OpenAPI and llms.txt are public.
JSON: /api/v1/dns and /api/v1/whois with a key. Or live tables /whois?query=example.com and /dns?q=example.com. Do not treat /lookup/whois/ as live WHOIS.
See llms.txt: typically 20–30 req/min per IP. On 429, wait and retry.
