← All posts
RDAP: The Domain Registry Protocol You Need to Know
Guide

RDAP: The Domain Registry Protocol You Need to Know

2026-07-01 3 min read

RDAP is the modern standard for querying domain registration data

If you've ever looked up domain ownership information, you've used WHOIS. But WHOIS is old—we're talking 1982 old. It's a text-based protocol that works, but it's clunky, inconsistent across registries, and increasingly restricted due to privacy regulations like GDPR.

Enter RDAP: the Registration Data Access Protocol. It's the standardized, machine-readable replacement that ICANN has been rolling out since 2015. Think of it as WHOIS's competent younger sibling—same goal, better execution.

How RDAP works

RDAP queries return structured data in JSON format instead of unformatted text. When you ask an RDAP server for domain information, you get back clean, organized responses that are easy for software to parse and analyze.

Here's what you typically get:

  • Domain registration details: creation date, expiration date, last update
  • Registrar information: which company registered it
  • Name server data: where the domain points
  • Registrant contact info: name, organization (when publicly available)
  • Status codes: whether it's active, expired, on hold, or locked

Each RDAP query goes to the authoritative registry for that TLD. If you want data on a .com domain, you query VeriSign's RDAP server. For .io domains, you query the registry that manages that TLD.

Why this matters for domain intelligence

When you're scoring expired domains for SEO authority at Parlor, RDAP is your backstage pass to reliable metadata. The structured format means:

Faster automation: You can programmatically request domain data and reliably parse responses. No more regex nightmares trying to extract information from inconsistent WHOIS output.

Better accuracy: Since RDAP is standardized, you get consistent field names and formats across all registries. An expiration date is always an expiration date, not buried in a wall of text with unpredictable formatting.

Privacy compliance: RDAP respects GDPR and similar regulations better than WHOIS. When registrant data is redacted, you get a clear response indicating that—not a cryptic placeholder.

Richer historical context: Some RDAP implementations provide event history (when was it registered, last updated, etc.), giving you better signals for authority assessment.

RDAP vs. WHOIS: the practical differences

WHOIS still works. You can still query it. But here's why RDAP is better:

| Aspect | WHOIS | RDAP | |--------|-------|------| | Data format | Unstructured text | Structured JSON | | Consistency | Varies by registry | Standardized | | Machine parsing | Difficult, error-prone | Easy, reliable | | Privacy handling | Inconsistent | GDPR-aware | | Authentication | Limited | Built-in support | | Rate limiting | Unclear | Well-defined |

WHOIS also has a reputation problem: it's frequently throttled, sometimes blocked, and many registries are phasing it out in favor of RDAP.

Getting started with RDAP queries

If you want to query RDAP directly, you need the right endpoint. ICANN maintains a bootstrap service that points you to the correct registry RDAP server for any domain.

Basic RDAP query structure:

https://rdap.[registry].net/domain/example.com

Most modern domain research tools—including intelligent domain scorers—already integrate RDAP under the hood. If you're building domain evaluation pipelines, using a tool that leverages RDAP gives you cleaner, more reliable data.

The transition from WHOIS to RDAP

WHOIS isn't disappearing overnight, but the writing is on the wall. ICANN has been pushing registries to support RDAP since 2015, and compliance is increasing. Some registries now recommend RDAP over WHOIS for new integrations.

For domain investors and SEO professionals, understanding RDAP matters because:

  • Tools you rely on are increasingly using it
  • Data quality improves when you're working with standardized responses
  • Privacy regulations mean WHOIS data access is becoming more limited
  • Automation and scripting become much more reliable

Bottom line

RDAP is the future of domain registration data access. It's not a radical change—it solves the same problem WHOIS does, just better. If you're serious about domain intelligence and authority scoring, knowing that RDAP exists and understanding what it provides gives you a clearer picture of the tools and data sources you're relying on.

When evaluating expired domains or building domain scoring systems, you want accurate, consistently formatted data. RDAP delivers that. That's not exciting—but it's exactly what you need.