{
"success": true,
"endpoint": "domain.rdap",
"billable": true,
"item": {
"domain": "apify.com",
"registered": true,
"ldhName": "apify.com",
"status": [
"client transfer prohibited"
],
"registrar": {
"name": "Amazon Registrar, Inc.",
"ianaId": "468",
"url": "http://registrar.amazon.com",
"abuseEmail": "[email protected]",
"abusePhone": "tel:+1.2024422253"
},
"createdAt": "2009-06-02T17:14:10Z",
"updatedAt": "2026-05-16T16:53:04Z",
"expiresAt": "2035-06-02T17:14:10Z",
"daysToExpiry": 3119,
"nameservers": [
"ns-1225.awsdns-25.org",
"ns-1928.awsdns-49.co.uk",
"ns-449.awsdns-56.com",
"ns-839.awsdns-40.net"
],
"dnssec": true
}
}
curl --location --request GET 'https://zylalabs.com/api/15008/rdap+domain+registration+and+availability+api/39569/domain+rdap+lookup?domain=apify.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the RDAP Domain Registration and Availability API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime.
WHOIS replacement: registration data from official RDAP registries. Registered or available, registrar, creation and expiry dates, days to expiry, status, nameservers and DNSSEC as clean JSON.
It uses RDAP, the ICANN-mandated successor to WHOIS, read directly from each registry. The output is structured JSON instead of free-form WHOIS text.
All gTLDs (.com, .net, .org, new gTLDs) and every ccTLD that publishes an RDAP server in the IANA bootstrap. Others (for example .de) return 422 unsupported_tld.
Yes. If the registry has no record the response is 200 with registered: false.
No. Registrant and other personal contact data are never returned. Only the registrar's public abuse contact is included.
Usually under one second; the registry bootstrap is cached.
The endpoint returns registration data for a domain, including whether it is registered or available, registrar details, creation and expiry dates, days to expiry, status, nameservers, and DNSSEC information, all in structured JSON format.
Key fields include "domain," "registered," "registrar" (with name, IANA ID, and abuse contact), "createdAt," "expiresAt," "daysToExpiry," "status," "nameservers," and "dnssec," providing comprehensive domain registration details.
The response is structured as a JSON object with a "success" flag, an "endpoint" identifier, and an "item" object containing all relevant domain data, making it easy to parse and utilize programmatically.
The endpoint provides information on domain registration status, registrar details, creation and expiration dates, days until expiration, domain status, nameservers, and DNSSEC, offering a complete view of domain registration.
Users can customize requests by providing a bare domain, a full URL, or a "www" prefixed domain. The API will determine the appropriate RDAP registry based on the TLD provided.
"registered" indicates if the domain is taken, "daysToExpiry" shows how many days remain until expiration, "status" lists current domain status (e.g., "client transfer prohibited"), and "dnssec" indicates if DNSSEC is enabled.
Typical use cases include domain availability checks, registrar information retrieval, monitoring domain expiration dates, and verifying DNSSEC status for security assessments.
Data is sourced directly from official RDAP registries, ensuring high accuracy. The API leverages the IANA bootstrap for reliable registry information, and regular updates from registries help maintain data integrity.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund