An RDAP lookup returns the same class of registration data buyers used to read in WHOIS, but as structured HTTP/JSON instead of a free-text port-43 dump — and privacy redaction still hides most registrant contact fields. If you searched “RDAP lookup,” you are not looking for a secret unredacted database. You are looking at the protocol ICANN now points the industry toward. Official overview: ICANN on RDAP. Official public search: lookup.icann.org.
This page compares protocols and what a buyer can rely on. It is not a tutorial on identifying a hidden owner. That job stays on how to find out who owns a domain. A live check on this site: WHOIS lookup.
GoatAcquisition is not a registrar and cannot retrieve fields a registry or registrar has redacted.
Port 43 WHOIS is being replaced, not prettied up
Classic WHOIS is a text protocol on port 43. Each registry and registrar formatted the response differently. Buyers learned to skim for “Registrar:”, “Creation Date”, “Name Server”, and status strings such as clientTransferProhibited. That skim still works on many leftover WHOIS pages, but it is not the direction of ICANN policy.
RDAP (Registration Data Access Protocol) is the replacement access method: query over HTTPS, response in a documented JSON shape, with links to related objects instead of one blob of prose. ICANN’s RDAP page describes that transition and why the old WHOIS model was inconsistent and hard to internationalize. You do not need to speak JSON. Buyer-facing tools, including lookup.icann.org and our WHOIS lookup, present the useful fields in a table.
Do not treat a WHOIS.com clone, a screenshot from 2019, or a registrar marketing page as the live record. Re-query the name the day you negotiate.
Field classes you can actually use
Across both protocols, a careful buyer reads categories, not a memorized field list that a blog invented:
- Registrar — which company holds the account that must push or unlock the name
- Status / EPP codes — transfer locks and hold states that affect close timing
- Events — created, updated, expiry (labels differ; the dates are the point)
- Nameservers — parking, marketplace, or corporate DNS, which is a clue, not identity
- Entities — registrant, admin, tech, registrar abuse contacts, often with roles in RDAP
RDAP’s advantage for buyers is consistency and machine-readable roles. A WHOIS paragraph might bury the registrar abuse email. An RDAP object usually labels the entity. RDAP also handles non-ASCII names more cleanly than old WHOIS text.
What RDAP does not magically restore: a personal email and phone for every GDPR-era registrant. Redaction is a policy and legal overlay, not a WHOIS bug that RDAP “fixes.”
If you need the human behind a privacy brand, that is research and outreach, not a protocol switch: WHOIS privacy. Nameserver interpretation: nameserver clues.
Privacy redaction on both protocols
After data-protection rules tightened, most gTLD records show a privacy or proxy service, or explicit redaction, in registrant name, organization, street, email, and phone. RDAP responses often include a remark that contact data is withheld and, sometimes, a registrar contact or abuse form instead.
That is expected. It is not proof the name is abandoned. It is not proof the person emailing you is the owner. It is not a reason to skip escrow. Use the public bits — registrar, lock status, expiry, nameservers — and treat anything in an inbox as a claim to verify in the closing file.
ICANN’s lookup tool is useful because it is the official public entry point, not because it bypasses redaction. If lookup.icann.org and your registrar’s RDAP disagree on something operational (lock, expiry), believe the account at close, and re-check ICANN’s pages if you are arguing about policy.
How to run the official checks
- Query the hostname on lookup.icann.org.
- Run the same hostname on WHOIS lookup.
- Note registrar, statuses, and dates. Ignore decorative “whois history” ads.
- If you will make an offer, save the lookup date. Records change.
Read ICANN’s own RDAP explainer rather than a forum summary: https://www.icann.org/rdap. Transfer-lock windows are a different policy document; do not mix them into this comparison. Locks: ICANN transfer locks.
What neither WHOIS nor RDAP will do
Neither protocol sells you the name. Neither proves the person on LinkedIn can transfer it. Neither is an appraisal. Neither replaces Escrow.com when money moves.
If the lookup shows no registrant object and the name is available to register, you are not in an acquisition. If it shows a registrant (even redacted), you are buying from an owner. Parent workflow from that point: how to buy a taken domain.
When you want a broker to run research and outreach rather than another lookup tab, submit a request. We still cannot unredact a record the registry will not publish.
Related reading
- How to find out who owns a domain — identity question, not protocol
- WHOIS privacy: find the owner — research after redaction
- Nameserver clues when researching an owner — DNS as a signal

