RDAPclient is a blazing-fast domain lookup service powered by Next.js and RDAP. It features a responsive web UI and a clean JSON-based API for retrieving domain registration data in real-time.
- 🌍 Web Interface: Perform WHOIS lookups directly from a clean and modern browser interface.
- ⚡ Fast API: Programmatic access to RDAP data using a REST-style endpoint.
- 📄 Rich JSON Output: Includes registrar, expiration/registration dates, DNSSEC, EPP status (with official links), nameservers, and RDAP server.
- 🔐 CORS Enabled: Easily consumable by frontend apps.
- 📘 ICANN EPP Labels: Domain status codes are linked to ICANN’s official registry.
- 🌐 Standards-Based: Built on top of the RDAP protocol defined by the IETF.
| Feature | WHOIS | RDAP |
|---|---|---|
| Standardized Format | ❌ Inconsistent across registries | ✅ JSON format, standardized |
| Secure Access (HTTPS) | ❌ Typically plain text over port 43 | ✅ Always delivered over HTTPS |
| Internationalization Support | ❌ No Unicode support | ✅ Full support for internationalized data |
| Access Control | ❌ No user-based access differentiation | ✅ Can provide tiered access (public vs. privileged data) |
| Searchability | ❌ Limited or unavailable | ✅ Supports entity/domain queries |
| Extensibility | ❌ Very limited | ✅ Easily extensible with new fields and capabilities |
| Service Discovery | ❌ Manual or unclear | ✅ Built-in mechanisms for registry discovery |
| Machine Readable | ❌ Hard to parse | ✅ Easy to integrate into apps & services |
📝 ICANN Announcement “As of 28 January 2025, the Registration Data Access Protocol (RDAP) will be the definitive source for delivering generic top-level domain name (gTLD) registration information in place of sunsetted WHOIS services. RDAP offers several advantages over WHOIS including support for internationalization, secure access to data, authoritative service discovery, and the ability to provide differentiated access to registration data. RDAP was developed by the Internet Engineering Task Force.”
➡️ Source – ICANN Announcement (27 Jan 2025)
Query domain WHOIS/RDAP records programmatically.
GET https://rdap.sayed.app/api/[domain]
Replace
[domain]with a valid domain likeexample.com.
GET https://rdap.sayed.app/api/lookup/abusayed.dev
{
"domainName": "abusayed.dev",
"registrar": "CloudFlare, Inc.",
"dnssec": "Signed",
"registeredOn": "Sun, 19 Sep 2021 15:18:19 GMT",
"expiresOn": "Sat, 19 Sep 2026 15:18:19 GMT",
"lastUpdated": "Wed, 11 Jun 2025 10:02:34 GMT",
"statuses": [
{
"label": "Client transfer prohibited",
"url": "https://icann.org/epp#clienttransferprohibited"
},
{
"label": "Renew period",
"url": "https://icann.org/epp#renewperiod"
}
],
"nameservers": ["lara.ns.cloudflare.com", "tony.ns.cloudflare.com"],
"rdapServer": "https://pubapi.registry.google/rdap/"
}| Field | Type | Description |
|---|---|---|
domainName |
string |
The fully qualified domain name. |
registrar |
string |
The domain registrar organization. |
dnssec |
string |
DNSSEC status (e.g., "Signed", "Unsigned"). |
registeredOn |
string (GMT) |
Domain registration date. |
expiresOn |
string (GMT) |
Domain expiration date. |
lastUpdated |
string (GMT) |
Timestamp of the last known WHOIS update. |
statuses |
object[] |
Array of EPP status objects (label + url). |
nameservers |
string[] |
Array of authoritative nameservers. |
rdapServer |
string |
The RDAP server used to retrieve this information. |
- 📜 ICANN – What is RDAP?
- 📄 ICANN RDAP Replacement Announcement (Jan 2025)
- 🧾 EPP Status Code Definitions (ICANN)
- 📚 IETF RDAP Specs (RFC 7480–7484)
- 🌐 Client.RDAP.org (Official UI)
- 📦 RDAP Client GitHub Repo
- 🧪 ICANN RDAP Deployment Statistics
- 🛠️ ICANN RDAP Server Implementation (Reference)
Check it out: https://rdap.sayed.app
This project is open-source and available under the MIT License