New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

node-red-contrib-domainkits

Package Overview
Dependencies
Maintainers
1
Versions
7
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

node-red-contrib-domainkits

Node-RED nodes for the DomainKits domain data API. Search newly registered, expired, aged and for-sale domains, plus WHOIS, DNS, CT logs and trends. One credential covers every endpoint.

latest
Source
npmnpm
Version
0.3.7
Version published
Weekly downloads
15
-28.57%
Maintainers
1
Weekly downloads
 
Created
Source

node-red-contrib-domainkits

Query the DomainKits domain data API from Node-RED.

This is the official Node-RED node for the DomainKits API, published and maintained by the DomainKits team. DomainKits is built and operated by Lyalpha GmbH, with domain data and infrastructure provided by ABTdomain, our domain intelligence and data aggregation platform. This repository is hosted under the ABTdomain GitHub organisation. Learn more about the relationship at domainkits.com/about.

The lead use case is newly registered domain search: every domain registered in the last 60 days across the indexed gTLDs, refreshed daily, filterable by keyword, registration date, length, composition and more. The same two nodes also cover expired, aged, active, deleted and for-sale domain search, plus WHOIS, DNS, safety, Certificate Transparency and trend lookups.

DomainKits is one API with a shared key across every endpoint. One credential in Node-RED covers all of it.

Install

From the Node-RED editor: Menu, Manage palette, Install, search for node-red-contrib-domainkits.

Or from the command line:

npm install node-red-contrib-domainkits

Credentials

You need a DomainKits API key. Sign up at domainkits.com; API access requires a Premium or higher plan, and Premium includes a trial period. Keys start with dk_.

Add the key once in the DomainKits API configuration node. Both nodes share it.

Nodes

Searches seven domain inventories. Pick the resource in the edit dialog; the filter fields adjust to match.

ResourceWhat it searches
Newly registered (default)Domains registered in the last 60 days, from the zone files
Newly registered, live feedDomains registered in the last 3 days, from Certificate Transparency
ExpiredDomains in the deletion cycle: expired, redemption, pending delete
AgedDomains with 5 to 20+ years of registration history
ActiveCurrently registered domains
DeletedDropped domains
For saleDomains listed on marketplaces

Typical newly registered query: keyword shop, TLD com, registered on 2026-07-10, letters only.

Configure filters in the edit dialog, or override any of them per message via msg.query:

{ "query": "shop", "tld": "com", "create_date_start": "2026-07-10", "create_date_end": "2026-07-10", "all_alpha": "true", "limit": 50 }

Numeric ranges are _min/_max pairs (length_min/length_max, age_min/age_max), date ranges are _start/_end pairs (create_date_start/create_date_end); either side may be omitted, equal bounds select an exact value. Composition booleans accept only true/false. Unknown parameter names and values return 400 with the supported values in the message. Full reference: the OpenAPI spec.

The two registration feeds read from different places, so they answer different questions. Newly registered reads the zone files and holds 60 days; it is the complete view for the generic TLDs. The live feed reads Certificate Transparency and holds 3 days: a name reaches it once a certificate is issued, which can be before the zone files carry it, so it surfaces names the zone feed cannot show yet. A live row carries tld in place of tld_count, and the endpoint runs on a smaller per-minute quota. Switch to it per message with { "resource": "nrds-live" } in msg.query.

Output: msg.payload is an array of domains; msg.total is the size of the full result set. A single request returns at most 500 rows; page with offset.

domain lookup

Single lookups and reports: WHOIS, DNS records, safety check, IP geolocation, registrar lookup, EPP status guide, TLD availability, typosquat scan, reverse nameserver, domain change monitoring, CT subdomains, CT certificates, CT search, TLD and keyword trends, and account usage.

Set the operation and target in the edit dialog, or per message via msg.operation and msg.target. Extra REST parameters go in msg.query.

Example flows

New registration watch: Inject (daily) sets msg.query to {"query":"yourbrand"}, domain search (newly registered) returns the day's matches, a switch node routes non-empty results to a notification.

Drop watch: Inject (daily), domain search (expired, stage pending delete, age 20+), function filters against your list, notification.

WHOIS enrichment: any flow that produces a domain feeds domain lookup (WHOIS) and gets registrar, dates and nameservers back on msg.payload.

Coverage

gTLDs only for the zone based search resources and trends. The index covers generic TLDs: .com, .net, .org, .info, .biz, .xyz, .online, .site, .top, .club, .live, .app, .dev and others. Country-code TLDs are not indexed: a query for .de, .co or .us returns an empty result set, not an error. The live feed is the exception and also carries .ai and .io.

WHOIS, DNS, safety, IP lookup and Certificate Transparency work on any domain, ccTLDs included.

No PII. 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.

Rate limits

Quotas follow your account and vary by plan. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Daily quotas reset at 00:00 UTC. Current limits: domainkits.com/dev/api-docs.

Resources

License

MIT

Keywords

node-red

FAQs

Package last updated on 21 Aug 2026

Related posts