Domainsdb Domains-Index API

Name: Domains-Index API
Brand: Domains-Index API
Availability: InStock

✓ 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.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Domains-Index API

Explore with Jentic

View OpenAPI Document

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.

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 the Jentic vault, 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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any Domains-Index key is stored encrypted in the Jentic vault and applied to the request at execution time. Agents only handle a scoped reference, so /domains/search and /domains/updates calls never expose the raw key.

Intent-based discovery

Agents search Jentic for intents like 'search registered domains' or 'list newly added domains' and receive the matching Domains-Index operation with its parameter schema, ready to call without consulting the spec by hand.

Time to first call

Direct integration: half a day to wire pagination and update polling. Through Jentic: under 30 minutes from search to first results.

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 the Jentic vault 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.