RDAP registration lookups (domains and IP addresses)
RDAP (Registration Data Access Protocol) is the replacement for WHOIS. datapulse_live_rdap answers one domain or IP address synchronously; datapulse_live_rdap_bulk submits up to 150 and returns a receipt. Name canonicalization, hashes and bulk-receipt accounting common to every tool: datapulse_help(topic="conventions"). Registration history over time is datapulse_help(topic="history").
datapulse_live_rdap
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | One of query / domain_hash | Domain name or IP address (e.g. example.com, xn--n3h.com, 8.8.8.8, 2606:4700:4700::1111). Give this or domain_hash |
domain_hash | string | One of query / domain_hash | The stored row of a bulk submission, read instead of a new lookup: submitted[].domain_hash from a datapulse_live_rdap_bulk receipt. The envelope comes back with domain_hash beside it (no sent or type); a hash with no row answers found: false. force does not apply |
force | boolean | No | Skip the caches and look the domain up live (default false) |
What is looked up. A domain is reduced to its registrable name under the full Public Suffix List, private suffixes included: www.Example.COM. is looked up as example.com, _dmarc.example.com as example.com, and a name under a private suffix keeps that suffix (www.shop.example.github.io as example.github.io); submitted_domain then echoes what you sent. A name under a private suffix is registered, if at all, with the suffix’s operator. Where the operator publishes RDAP (CentralNic’s service covers 27 suffixes, among them jp.net, uk.com, us.com, co.com and radio.am), the lookup goes to that service: microsoft.jp.net answers. A name under any other private suffix is looked up at the TLD’s registry, which can answer 404, object does not exist; that 404 is not proof the name is unregistered. RDAP is the only tool family that removes hostname labels, because registries only know registered names. IDN, punycode, and emoji or symbol names as registries sold them are accepted. Refused before any request, with the reason: a single label, a registrable name with an underscore (exa_mple.com), a CIDR range (a lookup of one address inside it returns the whole allocation from the RIR), and reserved addresses (loopback, private, link-local, carrier-grade NAT, documentation, benchmarking and other IETF-reserved ranges), for which no RIR answers.
Where the answer comes from
For a domain, the Scrape API answers from the first source that has it, and the envelope’s source names it:
cache: the Scrape API’s own stored result, within its 90-day window.datapulse: the DataPulse crawl database;researchdateis that crawl’s date and can be weeks old.live: a worker queried the registry for this request.
force: true skips cache and datapulse. A forced lookup does not add an observation to datapulse_dns_rdap_history, which follows the collector’s own crawl schedule. Diagnosing why a domain is missing from listings needs current registry status, which force: true returns: datapulse_help(topic="why_missing").
For an IP address, the Scrape API answers from its cache when it holds a result (which can be several weeks old) and otherwise queries the RIR; force: true refreshes.
Response
The API’s envelope {query, source, datetime, results} as sent, plus this tool’s sent (what was asked for), type ("domain" or "ip") and submitted_domain. query is the API’s request path (/rdap/example.com). results holds every observation the API returned, in its order. Names, nameservers, EPP status codes and country codes are case-folded; nothing else changes.
Captured 2026-10-20 (example.com is registered to IANA, registrar ID 376; its record carries no abuse contact, so abuse_email and abuse_phone are absent):
{
"datetime": "2026-10-20T01:14:09.875111596Z",
"query": "/rdap/example.com",
"results": [
{
"dns": ["elliott.ns.cloudflare.com", "hera.ns.cloudflare.com"],
"expiration_date": "2027-08-13T04:00:00Z",
"ianaid": 376,
"last_changed": "2026-08-14T08:01:43Z",
"name": "example.com",
"registrationdate": "1995-08-14T04:00:00Z",
"researchdate": "2026-10-20T00:58:25.737Z",
"status": ["client delete prohibited", "client transfer prohibited", "client update prohibited"]
}
],
"sent": "example.com",
"source": "cache",
"type": "domain"
}
Domain observations:
| Field | Description |
|---|---|
name | Domain name |
researchdate | When this RDAP data was collected |
ianaid | IANA registrar ID, resolved by datapulse_dns_registrar(iana_id=...); absent when the registry assigns no IANA registrar IDs (Nominet .uk among others); registry numbering: “Registrar identifiers” in datapulse_help(topic="infrastructure") |
registrationdate | Registration date |
expiration_date | Expiration date; absent when not published |
last_changed | Last RDAP-visible change; absent where the registry or registrar publishes no such event |
status | EPP status codes (below) |
dns | Delegated nameservers |
abuse_email, abuse_phone | The registrar’s abuse desk, not the domain owner |
The expiry is expiration_date here, in datapulse_domain_overview and in datapulse_dns_rdap_history, beside registrationdate and ianaid (the DataPulse API’s own field names).
IP observations always carry network_name, start_address, end_address and researchdate; handle, type, cidr, country, organization, registration_date, last_changed, status, abuse_email, abuse_phone and port43 appear when the RIR publishes them, and the RIRs differ (an IP observation can also carry name: ""; abuse_phone values are as the RIR wrote them, tel: URIs or plain numbers such as ARIN’s +1-650-253-0000):
- ARIN omits
country. Country codes are lower case whatever the RIR published. organizationis whatever the RIR published as the registrant entity, which for some RIPE objects is a maintainer handle (MNT-…).- LACNIC puts the prefix in
handleand omitscidr. - AFRINIC and APNIC sometimes publish no abuse contact.
- Timestamps are as the RIR published them (ARIN uses a
-05:00offset, othersZ, with varying precision), so they compare correctly only after parsing.
Lookup errors
A lookup the registry or RIR could not answer is not a tool error: the envelope comes back normally, and the observation in results[] carries an error field with the RDAP server’s own text instead of registration data:
{"query": "/rdap/datapulse-nonexistent-7f3a9c.com", "source": "live", "datetime": "2026-10-06T21:01:08Z",
"results": [{"name": "datapulse-nonexistent-7f3a9c.com", "researchdate": "2026-10-06T21:01:08Z",
"error": "# Error: RDAP server returned 404, object does not exist."}],
"sent": "datapulse-nonexistent-7f3a9c.com", "type": "domain"}
Common causes: the domain is not registered, the TLD runs no RDAP server (example.de answers "# Error: No RDAP servers found for 'example.de'"), the address is not allocated, or the registry or RIR rate-limited or timed out. A tool error means the request itself was refused or failed: invalid input (a CIDR, a reserved address, a single label), authentication, or the service being unavailable.
TLDs without RDAP. Some TLDs run no RDAP server; the best-known are .de (DENIC, web WHOIS only) and .edu (every US college and university), which IANA’s RDAP bootstrap file does not list. That is a limit of the protocol, not of DataPulse coverage: label search, DNS history, infrastructure similarity and DNS clustering (datapulse_dns_neighborhood) cover those TLDs. Registration clusters (datapulse_dns_regclusters) and RDAP history are built from RDAP and hold nothing for them (datapulse_help(topic="methodology")).
datapulse_live_rdap_bulk
Up to 150 domains or IP addresses per request, mixed freely, each {"query": ..., "force"?}; any other item field, domain included, is refused, naming the item, before anything is sent. The tool returns a receipt, not registration data. Each result is read back with datapulse_live_rdap(domain_hash=...) using the item’s submitted[].domain_hash, which reads the stored row without a new lookup.
Every item is validated first, exactly as the single tool validates (the same reductions and refusals). Bulk consults only the Scrape API’s own 90-day cache, not the DataPulse database, so cached is usually nonzero and anything not cached is queued; force: true on an item bypasses the cache. A domain whose TLD runs no RDAP server (.de, .edu) passes validation, and its job then fails with “No RDAP servers found”; the single tool reports that immediately.
The receipt for six inputs:
{
"accepted": 1, "rejected": 0, "cached": 2,
"submitted": [
{"index": 0, "query": "example.com", "domain_hash": "a379a6f6...", "job_id": "550e8400-..."},
{"index": 2, "query": "8.8.8.8", "domain_hash": "838c4c25...", "cached": true},
{"index": 5, "query": "xn--bcher-kva.com", "domain_hash": "9c1d...", "cached": true}
],
"rejected_items": [],
"rejected_local": [
{"index": 1, "query": "127.0.0.1", "error": "invalid query \"127.0.0.1\": 127.0.0.1 is a loopback address and has no RIR registration"},
{"index": 4, "query": "not a domain!!", "error": "invalid query \"not a domain!!\": ..."}
],
"duplicates": [{"index": 3, "query": "WWW.Example.COM.", "first_index": 0}],
"errors": []
}
submittedlists every item sent, in its normalized form.domain_hashis the hex SHA-256 of that query and the key to read it back; for an address it is the hash of the address text.job_idandcachedcome from the API’s per-item report and are absent when it sends none: an accepted item hasjob_idand nocached, a cached onecached: true. An item the API refuses stays listed, without ajob_id, and also appears inrejected_items.rejected_items(index,query,error) is what the API refused;errorsholds the API’s codes only and is[]unless the API refused something that passed validation.rejected_localis what was refused before the request, with the reason. These are not counted inrejected.accepted + cached + rejected + len(rejected_local) + len(duplicates)equals the number of items passed (1 + 2 + 0 + 2 + 1 = 6 above).- When no item can be sent, nothing is sent: the call is an error whose text is this receipt, with every item in
rejected_local, the counts 0, the other lists[], and anote.
Interpreting registration data
Domain status codes
| Status | Meaning |
|---|---|
ok | No restrictions set; the domain can be transferred, updated or deleted on request |
client transfer prohibited | The registrar blocks transfers to another registrar; the default on nearly every retail registration |
client update prohibited | The registrar blocks changes to the registration |
client delete prohibited | The registrar blocks deletion |
server transfer prohibited, server update prohibited, server delete prohibited | The same locks set at the registry (registry lock), typical of corporate portfolios |
client hold | The registrar removed the domain from the DNS (unpaid, abuse, dispute); it does not resolve |
server hold | The registry removed the domain from the DNS; it does not resolve |
inactive | No nameservers are delegated, so the domain does not resolve |
pending create | The registration is not yet finalized and the domain is not yet in the DNS |
redemption period | Deleted after expiry; the registrant can restore it for about 30 days |
pending delete | After redemption, the domain is released within about 5 days |
Lock depth. Corporate portfolios typically carry the three client … prohibited codes plus the three server … prohibited codes; a lone client transfer prohibited is a retail registrar’s default. How lock depth is weighed as evidence of ownership: datapulse_help(topic="lookalike_domains"), “What resolves control”.
Nameservers. The dns array should match the zone’s NS records from datapulse_live_dns. A mismatch points at a recent migration, a misconfiguration, or a hijack; datapulse_live_domain_health traces the delegation.
Registrant data and reverse WHOIS
Two facts govern every “who owns this domain?” and “what domains does this person own?” question:
- Public registration data carries no registrant contact data. Since GDPR took effect (May 2018), registries and registrars redact the registrant’s name, organization, email and phone. The RDAP tools return registrar-level data:
ianaid, the registrar’s abuse contacts, dates, status and nameservers. - There is no reverse WHOIS. No DataPulse tool, and no public RDAP service, can search registrations by registrant email, name or organization.
| Registrar | Registrant | |
|---|---|---|
| Who | The company that sells and manages the registration (GoDaddy, Namecheap, MarkMonitor) | The domain’s owner |
| In DataPulse RDAP | ianaid, abuse_email, abuse_phone | Not published, apart from a country code (below) |
abuse_email and abuse_phone are the registrar’s abuse desk: the contact for reporting abuse of any domain that registrar sponsors. They do not identify the registrant. One case looks like an exception and is not: some registries let an organisation act as its own registrar (Nominet “tags” under .uk, so bbc.co.uk shows nominet.admins@bbc.co.uk); the field is still the sponsoring registrar’s published contact.
The one registrant-side value available is registrant_cc, the registrant’s country code, which datapulse_dns_rdap_history observations carry when the registry publishes one.
Questions this server cannot answer: “all domains whose WHOIS contains <email>”, “all domains registered by datapulse_dns_searchlabels matches domain-name labels, so an email address run through it matches nothing meaningful, and datapulse_dns_registrar searches registrar company names, not owners.
What is available instead:
- A candidate domain:
datapulse_live_rdap(query=...)for registrar, dates, status and nameservers, and its lock depth (above). - A brand or name:
datapulse_dns_searchlabelson the label (neurogum, not an email address), then each hit individually. - What the site claims:
datapulse_domain_overviewreturnsentity_name,entity_typeandcountryextracted from the site’s web content: a claim made by the website, not a registration record. - Related registrations:
datapulse_dns_dptechsimfinds domains with similar DNS infrastructure,datapulse_dns_regclustersfinds registrations at the same registrar on the same day, anddatapulse_dns_rdap_historyshows registrar and nameserver timelines. These are leads to corroborate, not proof of a common owner:datapulse_help(topic="infrastructure").
Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026. Your AI assistant reads this page by calling datapulse_help(topic="rdap").