Domainsdb Domains-Index API
✓ Official Vendor SpecData EnrichmentCompany Datanone14 EndpointsREST
For Agents
Search registered domain names, list per-TLD records, and pull added or deleted domain updates from the Domains-Index database via GET endpoints.
Use for: Search for domains containing a specific keyword, List all .com domains added yesterday, Find newly deleted domains across a TLD, Get statistics for a specific TLD zone
Not supported: Does not handle WHOIS contact records, DNS resolution, or domain registration - use for indexed domain search and TLD update feeds only.
The Domains-Index API offers a searchable index of registered domain names across many TLDs, with endpoints to search the database, list per-TLD records, download whole-zone datasets, and inspect added or deleted domain updates. Statistics endpoints under /info expose zone-level counts and TLD metadata. The published spec lists no security scheme, so calls are open or rely on a vendor-supplied key managed outside the spec. The service is suited to threat-intelligence enrichment, lead generation, brand monitoring, and registry analytics.
Install Jentic One Beta
Connect the Domains-Index API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Domains-Index API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdomainsdb.info%2Fdomainsdb" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdomainsdb.info%2Fdomainsdb" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Domains-Index API.
Search the domain database via GET /domains/search
List domains within a specific TLD with GET /domains/tld/{zone_id}
Download a complete TLD dataset via /domains/tld/{zone_id}/download
Retrieve added or deleted domains for a date via /domains/updates/added and /deleted
List historical update batches with GET /domains/updates/list
Pull TLD-level and zone-level statistics from /info/stat and /info/tld
Use Cases
Patterns agents use Domains-Index API for, with concrete tasks.
★ Brand and Trademark Monitoring
Run a daily watchlist by calling GET /domains/updates/added with a date and matching the returned domains against trademark patterns. The Domains-Index database covers many TLDs, so a single job can monitor newly registered look-alikes without subscribing to per-registrar feeds. Downloads can be paged or pulled as a whole dataset.
GET /domains/updates/added for today and filter results against a regex of brand variants, then alert on each match.
Threat Intelligence Enrichment
Enrich threat-intel pipelines with first-seen and removed-domain context by polling /domains/updates/added and /domains/updates/deleted. Combined with /info/stat, analysts can correlate suspicious domains to TLD-level baseline volumes to spot abuse-prone zones.
GET /domains/updates/added and /domains/updates/deleted for the last 24 hours and write each domain plus its zone to a SIEM enrichment table.
TLD Market Research
Pull GET /info/tld and /info/stat/{zone} to understand domain volumes per TLD, which supports market research, registry pricing decisions, and content pieces about TLD adoption. Combined with /domains/tld/{zone_id} this can power a domain-availability search experience.
GET /info/tld, then for each top-10 zone call /info/stat/{zone} and produce a CSV summary of domain counts.
AI Agent Domain Discovery via Jentic
An AI agent uses Jentic to find Domains-Index search and update endpoints, then runs GET requests to support brand-protection or research tasks. Any vendor key is stored in your Jentic One instance, and the agent works directly with structured operation schemas rather than parsing raw API docs.
Search Jentic for 'search registered domains', execute GET /domains/search with a brand keyword, and return the top results with their TLDs.
Key Endpoints
14 endpoints — the domains-index api offers a searchable index of registered domain names across many tlds, with endpoints to search the database, list per-tld records, download whole-zone datasets, and inspect added or deleted domain updates.
METHOD
PATH
DESCRIPTION
GET
/domains/search
Search the domain database
GET
/domains/tld/{zone_id}
Get TLD records
GET
/domains/updates/added
Get added domains for a date
GET
/domains/updates/deleted
Get deleted domains for a date
GET
/info/stat/{zone}
Get statistics for a specific zone
GET
/info/tld/
Get overall TLD info
GET
/domains/search
Search the domain database
GET
/domains/tld/{zone_id}
Get TLD records
GET
/domains/updates/added
Get added domains for a date
GET
/domains/updates/deleted
Get deleted domains for a date
GET
/info/stat/{zone}
Get statistics for a specific zone
GET
/info/tld/
Get overall TLD info
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Domains-Index API by hand means mapping its search, TLD, and update-feed routes and paging through large result sets yourself before you get a clean domain list. Through Jentic you install once, import the Domains-Index API from the API Directory, store any key once, and your agent calls it.
Permission scoping
Every Domains-Index operation here is read-only search and feed retrieval, so scope by operation: limit the agent to the reads it needs, such as searching domains or listing newly added domains, and it never reaches a write. You choose which of these read operations are in its set.
Credential isolation
Any Domains-Index key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search registered domains' or 'list newly added domains', and Jentic returns the matching Domains-Index operation with its parameter schema so the agent calls the right endpoint without consulting the spec by hand.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Domains-Index API through Jentic.
What authentication does the Domains-Index API use?
The published OpenAPI spec does not declare a security scheme. Domains-Index typically issues an API key separately for higher quotas; if you have one, store it in your Jentic One instance so it is injected at execution time rather than embedded in agent code.
Can I find newly registered domains with the Domains-Index API?
Yes. GET /domains/updates/added returns the latest batch of added domains, optionally filtered by date. Pair it with /domains/updates/list to enumerate the available historical batches.
What are the rate limits for the Domains-Index API?
Limits are not declared in the spec and depend on your Domains-Index plan. Apply exponential backoff on 429 responses, and prefer the /download endpoints when you need a full TLD snapshot rather than paging through /domains/tld/{zone_id}.
How do I search for a brand keyword across domains via Jentic?
Run pip install jentic and search for 'search registered domains'. Jentic returns GET /domains/search; execute it with your keyword and Jentic injects any stored credential and handles pagination so the agent only sees the results.
Can I download a full TLD dataset?
Yes. GET /domains/tld/{zone_id}/download returns the whole zone dataset. This is more efficient than paging /domains/tld/{zone_id} when you need a complete snapshot for offline analysis.
Does the Domains-Index API expose zone statistics?
Yes. GET /info/stat returns overall statistics and GET /info/stat/{zone} returns per-zone counts. Use these for baseline metrics when monitoring TLD growth or anomaly detection.
Can I limit what my agent is allowed to do with the Domains-Index API?
Yes. Because you self-host Jentic One, your own rules decide which Domains-Index operations the agent may call, and every operation here is read-only, so you scope by picking the exact reads it gets. You can allow just domain search on GET /domains/search, or add the added and deleted update feeds on GET /domains/updates/added and /domains/updates/deleted, or the zone statistics on GET /info/stat and /info/tld, and leave everything else out of its set. Any Domains-Index key is stored by your instance and injected only for the operations you permit, never exposed to the agent.
GET STARTED