RDAP API is an MCP server published by io.rdapapi, hosted at rdapapi.io. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 7 tools, including domain-lookup, bulk-domain-lookup, ip-lookup, asn-lookup, nameserver-lookup.
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.
| Parameter | Type | Description |
|---|---|---|
| whois | boolean | Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true. |
| domain * | string | The domain name to look up, e.g. "example.com". Unicode (IDN) names are accepted. Pass the registered domain, not a host such as "www.example.com". |
| follow | boolean | Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false. |
None yet. Changes appear after a server's second daily check.
{
"name": "domain-lookup",
"title": "Domain Lookup",
"description": "Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"whois": {
"type": "boolean",
"default": true,
"description": "Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true."
},
"domain": {
"type": "string",
"description": "The domain name to look up, e.g. \"example.com\". Unicode (IDN) names are accepted. Pass the registered domain, not a host such as \"www.example.com\"."
},
"follow": {
"type": "boolean",
"default": false,
"description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false."
}
}
},
"annotations": {
"title": "Domain Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| whois | boolean | Set false to refuse the WHOIS fallback for every domain in the batch, so a TLD with no RDAP server returns not_supported. Defaults to true. |
| follow | boolean | Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false. |
| domains * | array | The domain names to look up, e.g. ["example.com", "example.net"]. Between 1 and 10 per call. Unicode (IDN) names are accepted. Pass registered domains, not hosts such as "www.example.com". |
{
"name": "bulk-domain-lookup",
"title": "Bulk Domain Lookup",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"domains"
],
"properties": {
"whois": {
"type": "boolean",
"default": true,
"description": "Set false to refuse the WHOIS fallback for every domain in the batch, so a TLD with no RDAP server returns not_supported. Defaults to true."
},
"follow": {
"type": "boolean",
"default": false,
"description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false."
},
"domains": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 10,
"minItems": 1,
"description": "The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted. Pass registered domains, not hosts such as \"www.example.com\"."
}
}
},
"annotations": {
"title": "Bulk Domain Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.
| Parameter | Type | Description |
|---|---|---|
| ip * | string | IPv4 or IPv6 address, e.g. "8.8.8.8" or "2001:4860:4860::8888". |
| prefix | integer | Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6. |
{
"name": "ip-lookup",
"title": "IP Address Lookup",
"description": "Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.",
"inputSchema": {
"type": "object",
"required": [
"ip"
],
"properties": {
"ip": {
"type": "string",
"description": "IPv4 or IPv6 address, e.g. \"8.8.8.8\" or \"2001:4860:4860::8888\"."
},
"prefix": {
"type": "integer",
"description": "Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6."
}
}
},
"annotations": {
"title": "IP Address Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.
| Parameter | Type | Description |
|---|---|---|
| asn * | string | Autonomous system number, e.g. "15169" or "AS15169". |
{
"name": "asn-lookup",
"title": "ASN Lookup",
"description": "Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.",
"inputSchema": {
"type": "object",
"required": [
"asn"
],
"properties": {
"asn": {
"type": "string",
"description": "Autonomous system number, e.g. \"15169\" or \"AS15169\"."
}
}
},
"annotations": {
"title": "ASN Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.
| Parameter | Type | Description |
|---|---|---|
| host * | string | Nameserver hostname, e.g. "ns1.example.com". |
{
"name": "nameserver-lookup",
"title": "Nameserver Lookup",
"description": "Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.",
"inputSchema": {
"type": "object",
"required": [
"host"
],
"properties": {
"host": {
"type": "string",
"description": "Nameserver hostname, e.g. \"ns1.example.com\"."
}
}
},
"annotations": {
"title": "Nameserver Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| handle * | string | RIR entity handle, e.g. "GOGL" (ARIN) or "ORG-RIEN1-RIPE" (RIPE). |
{
"name": "entity-lookup",
"title": "Entity Lookup",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"description": "RIR entity handle, e.g. \"GOGL\" (ARIN) or \"ORG-RIEN1-RIPE\" (RIPE)."
}
}
},
"annotations": {
"title": "Entity Lookup",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}List the TLDs this API can query, or describe one: which RDAP or WHOIS 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.
| Parameter | Type | Description |
|---|---|---|
| tld | string | A single TLD to describe, e.g. "com" or ".io". Omit to list every supported TLD by name. |
| since | string | List only the TLDs added after this ISO 8601 date, e.g. "2026-01-01". Ignored when "tld" is given. |
| server | string | List only the TLDs served by this host, RDAP or WHOIS, e.g. "rdap.verisign.com". Ignored when "tld" is given. |
{
"name": "tlds",
"title": "Supported TLDs",
"description": "List the TLDs this API can query, or describe one: which RDAP or WHOIS 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.",
"inputSchema": {
"type": "object",
"properties": {
"tld": {
"type": "string",
"description": "A single TLD to describe, e.g. \"com\" or \".io\". Omit to list every supported TLD by name."
},
"since": {
"type": "string",
"description": "List only the TLDs added after this ISO 8601 date, e.g. \"2026-01-01\". Ignored when \"tld\" is given."
},
"server": {
"type": "string",
"description": "List only the TLDs served by this host, RDAP or WHOIS, e.g. \"rdap.verisign.com\". Ignored when \"tld\" is given."
}
}
},
"annotations": {
"title": "Supported TLDs",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Normalized RDAP (the official successor to WHOIS) domain registration lookups. - `domain-lookup` — registrar, status, key dates, nameservers and contact entities for a domain name. Set `follow` to true when you need registrar-level detail on thin registries such as .com and .net. For the TLDs IANA lists no RDAP server for, the answer is read from the registry's WHOIS server instead and returned in the same shape; `meta` carries `source` (`rdap` or `whois`) and `server`. A WHOIS registry may publish fewer fields — several give no dates, some no registrar — and anything it withholds is null rather than inferred. - `bulk-domain-lookup` — the same data for several domains in one pooled call, which is far faster than looping `domain-lookup`. Pro and Business plans only. - `ip-lookup` — network range, holder, country, status and geofeed URL for an IPv4 or IPv6 address, optionally with a CIDR prefix length. - `asn-lookup` — holder, country and registration dates for an autonomous system number. - `nameserver-lookup` — IP addresses, status and sponsoring registrar for a nameserver hostname. - `entity-lookup` — an organization or contact by RIR handle, e.g. "GOGL" (ARIN) or "ORG-RIEN1-RIPE" (RIPE). ARIN, RIPE, APNIC, LACNIC and AFRINIC only; a domain's registrar or registrant comes from `domain-lookup`. - `tlds` — which TLDs are supported, which server answers for one, and how reliably that server fills each field. Each entry carries `protocol`; field availability is measured from RDAP responses, so a `whois` entry has none. Metadata: no quota cost. Authentication uses your API key as a bearer token. Each successful lookup (and each "not found", which is still a real answer) counts against your monthly plan quota, exactly like the REST API — one unit per domain in a bulk batch. `tlds` is metadata and is never charged.
Names, descriptions and schemas were written by the server and are shown as data.