Software Alternatives & Startups

Officially verified details RDAP API

Domain registration data as clean JSON across 1,200+ TLDs, through RDAP, the official WHOIS replacement. 7-day free trial, from $9/month.

RDAP API

RDAP API Reviews and Details

This page is designed to help you find out whether RDAP API is good and if it is the right choice for you.

Screenshots and images

  • Landing page: a domain lookup returns one clean JSON response, across 1,200+ TLDs. //
    2026-11-14
  • Free web lookup for github.com: registrar, registration and expiry dates, nameservers and EPP status. //
    2026-11-14
  • API reference with endpoints for domains, IPs, ASNs, nameservers and entities, and curl, Node.js and Python examples. //
    2026-11-14
  • Three plans from $9/month, each with a 7-day free trial, plus bulk lookups, WHOIS fallback and an MCP server for AI agents. //
    2026-11-14

Badges

Promote RDAP API. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Questions & Answers

As answered by people managing RDAP API.
  1. Which are the primary technologies used for building RDAP API?

    PHP and Laravel, MariaDB, Redis, Vue.js with Inertia, and Stripe for billing.

  2. What makes RDAP API unique?

    It reads registration data from the registries themselves over RDAP, the protocol that ICANN made the replacement for WHOIS, and returns it in one JSON format for more than 1,200 TLDs. Where a TLD has no RDAP server, it reads the registry's WHOIS server and returns the same format, with the source stated in the response. For .com and .net, an optional follow mode also fetches the contacts held by the registrar. A public /tlds endpoint shows, for each TLD, which fields the registry actually fills.

  3. Why should a person choose RDAP API over its competitors?

    Most WHOIS APIs sell records from their own database and price them for security teams: WhoisXML API costs $2.40 per 1,000 queries at one million per month. RDAP API answers from the registry, with at most 48 hours of caching, and costs between $0.20 and $0.30 per 1,000 requests. The response format is identical for every TLD, so there is no WHOIS text to parse and no per-registry exception to handle.

  4. How would you describe the primary audience of RDAP API?

    Developers who need domain registration data inside their own product: domain investors and availability checkers, brand protection and security tools, registrars, and companies that enrich lead or vendor data with domain information. Most usage is unattended automation.

  5. What's the story behind RDAP API?

    ICANN ended the WHOIS obligation for gTLD registries in January 2025, and RDAP became the official source. RDAP is a better protocol, but every registry implements it slightly differently, and some TLDs still have no RDAP server at all. RDAP API was launched in March 2026 to absorb those differences, so that developers get one reliable format instead of maintaining their own parsers.

Videos

We don't have any videos for RDAP API yet.

Do you know an article comparing RDAP API to other products?
Suggest a link to a post with product alternatives.

Suggest an article

RDAP API discussion

Log in or Post with

Is RDAP API good? This is an informative page that will help you find out. Moreover, you can review and discuss RDAP API here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.