x402AgentsToolsHub

RDAP / WHOIS Lookup

Full registration record for a domain via RDAP (the modern WHOIS): registrar, creation/expiration/last-updated dates with days-to-expiry, nameservers, EPP statuses and DNSSEC. Straight from the authoritative registry — the data agents should cite for domain diligence.

🔌 Server-side tool

This tool runs on the server (it fetches third-party URLs directly and cannot run in your browser). Use the paid JSON API below — the worked examples show real server-side results and refresh automatically.

Worked examples

A classic domain

GET /api/v1/security/whois-lookup?domain=example.com

Result: example.com — registered 1995-08-14, expires 2027-08-13 (300 days)

Google

GET /api/v1/security/whois-lookup?domain=google.com

Result: google.com — registered 1997-09-15, expires 2028-09-14 (698 days)

io domain

GET /api/v1/security/whois-lookup?domain=vercel.com

Result: vercel.com — registered 1999-10-04, expires 2029-10-04 (1084 days)

Machine API (x402)

$0.003 / call

This tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.

GET /api/v1/security/whois-lookup?domain=example.com HTTP/1.1
Host: agentstoolshub.com

→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)

{
  "tool": "security/whois-lookup",
  "input": {"domain":"example.com"},
  "result": { "value": 300, "answer": "example.com — registered 1995-08-14, expires 2027-08-13 (300 days)" }
}

Agent docs: /llms.txt · OpenAPI spec · integration guide

About this tool

Everything the registry knows about a domain, via RDAP — the structured JSON successor to port-43 WHOIS: registrar of record, creation and expiry dates, EPP lifecycle statuses, nameservers and DNSSEC signing. Answers 'how old is this business's domain' and 'is it about to lapse' from the authoritative source.

Frequently asked questions

Is this real WHOIS data?

Yes — RDAP is served by the same registries that ran WHOIS, with structured JSON and sane rate limits instead of a raw text blob. rdap.org resolves to the authoritative server for each TLD.

Why are some TLDs missing?

A few country-code TLDs still publish no RDAP service. In those cases the lookup returns a clear error rather than partial data — better than guessing from a cached scrape.

Related tools