RDAP registration lookup

Follow the authoritative registry narrative without copying raw JSON. Built for audits, aftermarket checks, and calmer stakeholder updates.

Domain to look up

Paste a bare hostname. We strip `https://`, `www.`, and anything after `/` before querying the bootstrap RDAP endpoint for your TLD.

Why RDAP instead of scraping WHOIS

RDAP is structured JSON sourced from registry operators listed in the IANA bootstrap feed. WHOIS portals still exist, yet many teams reach for RDAP first because parsers can evolve without fragile screen scraping when a TLD operator ships machine-readable payloads.

Privacy laws and registrar policy mean some registrant-facing fields intentionally disappear behind redaction tiers. Missing values are signals of policy, not a bug in BenOpt.

How RDAP interacts with DNS

A domain may exist in RDAP yet show sleepy DNS elsewhere. Conversely, delegated records can flap while registry metadata stays untouched. RDAP informs lifecycle questions; DNS lookups answer routing questions.

Availability: Still confirm renewal quotes and premium tiers at checkout before handing over a card.
Transfers: Transfer locks and statuses may live only in registrar consoles even when RDAP already lists an expiry stamp.

Related tooling on BenOpt

Need quick math on timestamps? Jump to domain age calculator for elapsed time since registration. Still hunting availability? Pair this page with bulk domain checker or our DNS record lookup.

BenOpt summarizes public RDAP data. This is informational research, not legal advice about trademarks, escrow, or contract negotiations.