io.rdapapi/rdap · v1.3.0 · sales-and-crm
RDAP API is healthy: it completed an MCP handshake in 1456 ms and exposes 7 tools.
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Endpoint: https://rdapapi.io/mcp/rdap (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 7 |
| Latency | 1456 ms |
| Last checked (UTC) | 2026-10-15T11:45:18.340Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T11:45:18.340Z | Healthy | 1456 |
domain-lookup | Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name. |
bulk-domain-lookup | Look up normalized RDAP registration data for several domain names in one pooled call. Requires a Pro or Business plan; every domain in the batch counts against the quota. |
ip-lookup | Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block. |
asn-lookup | Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number. |
nameserver-lookup | Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname. |
entity-lookup | Look up normalized RDAP data for an RIR entity handle — an organization or contact identifier such as "GOGL" or "ORG-RIEN1-RIPE". Only ARIN, RIPE, APNIC, LACNIC and AFRINIC handles resolve; a domain's registrar or registrant comes from domain-lookup instead. |
tlds | List the TLDs this API can query, or describe one: which RDAP server answers for it, since when it has been supported, and how often that server fills each field. Metadata, so it never counts against the monthly quota. |