RDAP API

Official7 tools

by rdapapi

Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.

MCP Server: io.rdapapi/rdap

This MCP server provides normalized JSON for any domain across 1,200+ TLDs. It reads WHOIS data when no RDAP server exists, and outputs results in a consistent JSON format suitable for downstream developer tooling.

🛠️ Key Features

Normalized JSON output for domain data
Coverage across 1,200+ TLDs
Uses WHOIS when RDAP server access is unavailable
Exposes 7 tools

🚀 Use Cases

Fetching domain registration information for domains spanning many TLDs
Integrating RDAP-like data workflows even when RDAP endpoints are missing

⚡ Developer Benefits

Consistent normalized JSON structure for varied TLD inputs
Fallback behavior to WHOIS when RDAP servers do not exist

⚠️ Limitations

Behavior depends on RDAP availability; WHOIS is used specifically when no RDAP server exists

Captured live from the server via tools/list.

domain-lookup

Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.

Parameters3

domain	string	required	The domain name to look up, e.g. "example.com". Unicode (IDN) names are accepted.
follow	boolean	optional	Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.
whois	boolean	optional	Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "description": "The domain name to look up, e.g. \"example.com\". Unicode (IDN) names are accepted.",
      "type": "string"
    },
    "follow": {
      "description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
      "default": false,
      "type": "boolean"
    },
    "whois": {
      "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.",
      "default": true,
      "type": "boolean"
    }
  },
  "required": [
    "domain"
  ]
}

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.

Parameters3

domains	array	required	The domain names to look up, e.g. ["example.com", "example.net"]. Between 1 and 10 per call. Unicode (IDN) names are accepted.
follow	boolean	optional	Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.
whois	boolean	optional	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.

Raw schema

{
  "type": "object",
  "properties": {
    "domains": {
      "description": "The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted.",
      "minItems": 1,
      "maxItems": 10,
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "follow": {
      "description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
      "default": false,
      "type": "boolean"
    },
    "whois": {
      "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.",
      "default": true,
      "type": "boolean"
    }
  },
  "required": [
    "domains"
  ]
}

ip-lookup

Look up normalized RDAP allocation data (network range, holder, country, status) for an IP address or CIDR block.

Parameters2

ip	string	required	IPv4 or IPv6 address, e.g. "8.8.8.8" or "2001:4860:4860::8888".
prefix	integer	optional	Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6.

Raw schema

{
  "type": "object",
  "properties": {
    "ip": {
      "description": "IPv4 or IPv6 address, e.g. \"8.8.8.8\" or \"2001:4860:4860::8888\".",
      "type": "string"
    },
    "prefix": {
      "description": "Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6.",
      "type": "integer"
    }
  },
  "required": [
    "ip"
  ]
}

asn-lookup

Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.

Parameters1

asn

string

required

Autonomous system number, e.g. "15169" or "AS15169".

Raw schema

{
  "type": "object",
  "properties": {
    "asn": {
      "description": "Autonomous system number, e.g. \"15169\" or \"AS15169\".",
      "type": "string"
    }
  },
  "required": [
    "asn"
  ]
}

nameserver-lookup

Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.

Parameters1

host

string

required

Nameserver hostname, e.g. "ns1.example.com".

Raw schema

{
  "type": "object",
  "properties": {
    "host": {
      "description": "Nameserver hostname, e.g. \"ns1.example.com\".",
      "type": "string"
    }
  },
  "required": [
    "host"
  ]
}

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.

Parameters1

handle

string

required

RIR entity handle, e.g. "GOGL" (ARIN) or "ORG-RIEN1-RIPE" (RIPE).

Raw schema

{
  "type": "object",
  "properties": {
    "handle": {
      "description": "RIR entity handle, e.g. \"GOGL\" (ARIN) or \"ORG-RIEN1-RIPE\" (RIPE).",
      "type": "string"
    }
  },
  "required": [
    "handle"
  ]
}

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.

Parameters3

tld	string	optional	A single TLD to describe, e.g. "com" or ".io". Omit to list every supported TLD by name.
server	string	optional	List only the TLDs served by this host, RDAP or WHOIS, e.g. "rdap.verisign.com". Ignored when "tld" is given.
since	string	optional	List only the TLDs added after this ISO 8601 date, e.g. "2026-01-01". Ignored when "tld" is given.

Raw schema

{
  "type": "object",
  "properties": {
    "tld": {
      "description": "A single TLD to describe, e.g. \"com\" or \".io\". Omit to list every supported TLD by name.",
      "type": "string"
    },
    "server": {
      "description": "List only the TLDs served by this host, RDAP or WHOIS, e.g. \"rdap.verisign.com\". Ignored when \"tld\" is given.",
      "type": "string"
    },
    "since": {
      "description": "List only the TLDs added after this ISO 8601 date, e.g. \"2026-01-01\". Ignored when \"tld\" is given.",
      "type": "string"
    }
  }
}

Install

Tools (7)

domain-lookupbulk-domain-lookupip-lookupasn-lookupnameserver-lookupentity-lookuptlds

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://rdapapi.io/mcp/rdap

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "rdap": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://rdapapi.io/mcp/rdap"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

MCP Server: io.rdapapi/rdap

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

domain-lookup

bulk-domain-lookup

ip-lookup

asn-lookup

nameserver-lookup

entity-lookup

tlds

Install

Remote endpoint

Related servers