The Domain Data API

Pick Your Surface, Keep One Key

The same key authenticates every surface. Start with whichever fits your stack; switching later costs nothing because they all speak to the same API.

curl "https://premium-api.domainkits.com/api/v1/search/expired?keyword=clinic&tld=com" \
  -H "Authorization: Bearer dk_xxx"

npm install @domainkits/sdk

const dk = new DomainKits('dk_xxx');
await dk.expired.list({ keyword: 'clinic', tld: 'com' });

Settings > Community Nodes > Install
n8n-nodes-domainkits

One credential covers every resource.

A Domain Data API Built Around Research

The core of the API is research: query six domain inventories by keyword, or browse an entire gTLD, then stack filters for length, age, composition and sale status until millions of names narrow down to a decision-ready shortlist.

From there the endpoints chain together. A typical flow: search a keyword across newly registered domains, check WHOIS and safety on the interesting ones, confirm how the keyword is trending, then see whether matching names are listed for sale.

• Search: newly registered, aged, active, expired, deleted and for-sale domains.
• Lookups: WHOIS, DNS, reverse nameserver, Google Safe Browsing, IP geolocation, registrar and EPP status checks, answered at request time.
• Trends: daily registration volumes per gTLD with moving averages, and hot, emerging and prefix keyword rankings.
• Downloads: daily newly registered domain files by TLD.
• Account: per-endpoint usage counters, so quota checks can be automated.

What Can You Build with a Domain Intelligence API?

Brand protection teams watch each day's new registrations for names that contain their brand, and check WHOIS, DNS and safety status on anything suspicious. Domain investors filter expiring inventory by age, length and drop date to feed acquisition pipelines, and track marketplace supply by TLD or keyword to read the market before bidding.

Product builders use the same endpoints for registrar-style search experiences, portfolio dashboards that track listing status for held names, or research tools built on registration trend data.

Coverage and Cadence

Coverage is gTLD-focused, spanning all the gTLDs we track. The data is compiled from public sources and does not include ccTLD zones, so totals can differ from registry-reported figures. Search indexes and trend series refresh daily; WHOIS, DNS and safety lookups run live at request time. Trend windows span 7 to 180 days.

Responses contain no personal data. WHOIS results are limited to registrar, dates, status codes and nameservers; registrant names, emails, addresses and phone numbers are not returned.

Access and Keys

API access is included with Premium and higher plans. Authentication is a single key sent in a request header, and the same key works across the REST API, the TypeScript SDK and the n8n node. API usage is metered separately from your web limits, so API calls do not consume the quotas you use elsewhere. Every response carries rate limit headers, and per-endpoint limits are listed in the API reference (sign in required).