How to Look Up Domain Registration Data With RDAP (Not WHOIS Scraping)

You need facts about a domain: who holds it, when it was created, when it expires, and whether the registry lists special statuses. WHOIS portals still exist, but RDAP is the modern, machine-readable path most registries expect tools to use.

This guide explains how to read RDAP without drowning in JSON, when WHOIS still matters, and how BenOpt turns registry answers into plain cards you can screenshot for a partner or paste into a spreadsheet.

---

Quick answer

RDAP (Registration Data Access Protocol) is JSON from the authoritative registry for a TLD. A 404-style response usually means the name is not registered. A 200 response means the registry has an object, even if DNS looks empty.

Use RDAP for registration facts. Use DNS for routing facts. Confirm price and cart eligibility at a registrar before you pay.

On BenOpt, open the RDAP registration lookup, paste a hostname like example.com, and read the summary cards.

---

Why RDAP replaced scraping WHOIS for most workflows

WHOIS was built for humans reading terminal output. RDAP was built for software that needs predictable fields: events, entities, status URIs, and nameserver objects.

That matters when you are:

• auditing an aftermarket listing
• checking whether a “parked” name is actually registered
• comparing expiry dates across a short list
• explaining to a cofounder why a name is not free

Scraping a registrar’s WHOIS HTML page breaks when layouts change. RDAP endpoints are documented in the IANA bootstrap file, which maps each TLD to one or more registry URLs.

BenOpt’s edge worker loads that bootstrap, picks the right server, and normalizes the response so you do not have to.

---

What you can usually see in a successful RDAP lookup

Not every registry returns the same depth. Privacy rules and ccTLD policy differ. Still, these fields show up often enough that they are worth knowing:

Registrar name

The company that sold or manages the registration on behalf of the registrant. Helpful when you are deciding who to contact for a transfer quote.

Registration and last-changed events

Timestamps tied to registration and last changed style event actions. These power age math and help you spot recent transfers.

Expiration event

The registry’s view of when the current registration period ends. Compare this with your registrar panel if they disagree.

Status codes

Often URNs like client transfer prohibited or redemption period. They explain why a name might not move even when DNS is quiet.

Nameservers

Authoritative DNS hosts listed in RDAP. If they point at a parking network, that explains a placeholder site.

The RDAP lookup tool surfaces these when the registry includes them. Missing lines usually mean redaction, not a bug in BenOpt.

---

Step-by-step: a lookup you can repeat

1. Copy the apex domain only (brandname.com, not a full URL with a path).
2. Strip https://, www., and tracking parameters mentally before you paste.
3. Run the lookup once and save a note: registrar, expiry, status list, nameservers.
4. If the outcome is unregistered, treat it as a strong signal, then confirm in a registrar cart.
5. If the outcome is registered but DNS is empty, read the why no website but RDAP says registered article next.

For ten or twenty names, batch through the bulk checker first, then RDAP only on the DNS-quiet candidates so you do not hammer registries.

---

When WHOIS portals still help

RDAP is not universal in spirit even when it is universal on paper.

Some ccTLDs publish thin RDAP data but richer local WHOIS rules. Some aftermarket brokers paste registrar screenshots that never appeared in RDAP because the listing is stale.

If RDAP returns unsupported for a TLD, fall back to the registry’s public site or a registrar search. Do not assume the name is free.

---

Common mistakes

Mistake: treating RDAP as legal clearance.

RDAP does not tell you about trademarks, prior spam, or UDRP history. It tells you registry metadata.

Mistake: ignoring status URIs.

A domain can be registered and effectively frozen. Status codes are where that story lives.

Mistake: comparing RDAP expiry to your credit card charge date.

Expiry is a registry event. Your registrar may show renewal windows, grace periods, and auto-renew flags that extend beyond the raw timestamp.

---

Worked example: reading a typical .com response

Imagine you lookup northstarlabs.com for a partnership pitch. RDAP returns registered status, a registrar you recognize, creation in 2019, expiry next spring, and two Cloudflare nameservers.

Your notes should capture:

• Object status: registered
• Registrar string exactly as shown
• Creation and expiry in UTC for your spreadsheet
• Whether transfer prohibited appears in the URI list

Then open DNS lookup. If MX records exist, the company still uses mail on the domain even when the marketing site is a holding page. That combination tells you negotiation is realistic, not a fresh registration play.

If the same lookup returned unregistered, your next step is cart pricing, not outreach to a fictional owner.

---

Building a repeatable research template

Create a spreadsheet with columns:

Column	Source
Apex	Your input
RDAP outcome	BenOpt bucket
Registrar	RDAP card
Created	RDAP event
Expires	RDAP event
Status URIs	Copy paste
NS list	RDAP or DNS tool
DNS summary	DNS lookup
Next action	Your call

One row per domain. Five minutes of discipline beats thirty minutes of re-querying because you forgot what you saw.

---

FAQ

Is RDAP the same as WHOIS?

They answer similar questions for humans, but RDAP is structured JSON aimed at tools. WHOIS is often a formatted view of overlapping data.

Why did BenOpt hide some fields?

We hide nothing on purpose. If a registry redacts registrant data, RDAP simply omits it.

Can I lookup www.brand.com?

You can paste it, but registries store the domain object for the registered name (brand.com). Focus on the apex unless you truly registered a subdomain zone, which is rare for founders.

Does RDAP prove availability?

It proves registry object presence. Premium tiers, reserved lists, and registry locks can still block purchase after a clean RDAP 404.

---

What to do next

Run your target name through RDAP lookup. If you are buying aged inventory, pair it with the domain age calculator. If you still need routing truth, use DNS record lookup.

BenOpt reads live registry and resolver data. Treat every result as a signal you confirm at checkout, not a guarantee.