Despite the name, it's backed by RDAP (RFC 7484/9082/9083), the structured JSON successor to the legacy WHOIS protocol — no port-43 text parsing, no external binary. It resolves the authoritative RDAP server per TLD from IANA's bootstrap registry (https://data.iana.org/rdap/dns.json, cached for 24h) and queries it directly over HTTPS.

Install

Into a dsh profile:

dsh plugin --profile <name> add dsh-whois-plugin                # from npm
dsh plugin --profile <name> add github:rjn32s/dsh-whois-plugin  # straight from GitHub

Verify the layer, then boot:

dsh --profile <name> --dump-config   # look for "# == dsh-whois-plugin"
dsh --profile <name>

Usage

Once installed, just ask the agent, e.g.:

Look up the WHOIS/RDAP info for example.com

The model calls whois({ domain: "example.com" }) and gets back the raw RDAP JSON (registrar, status, events like registration/expiration, nameservers, and registrant entities where the registry publishes them).

Notes / limitations

A small number of ccTLDs have no RDAP entry yet in IANA's bootstrap file; the tool throws a clear error in that case rather than silently falling back to legacy WHOIS.
No API key or network egress config required beyond outbound HTTPS.