RDAP Lookup: How the New WHOIS Works Today

If you need an rdap lookup, the short answer is this: use RDAP to check the current registration record for a domain, especially a gTLD, in a structured, machine-readable format. It is the modern replacement for traditional WHOIS queries for gTLD registration data, and it is now the authoritative place to check registrar details, dates, nameservers, status values, and whatever contact data is actually published.

For most people, an rdap lookup is not about seeing a private owner’s full identity. It is about understanding the domain’s registration state. You can use it to see which registrar sponsors the name, when it was registered or updated, when it is due to expire, which nameservers are in use, and whether the domain has status codes that affect transfer, update, or deletion. That makes RDAP useful for due diligence, acquisition research, operations, and dispute screening.

What is an RDAP lookup?

An RDAP lookup is a query for domain registration data using the Registration Data Access Protocol. In plain English, it is the newer way to ask, “What does the registration record for this domain say right now?”

For gTLDs, RDAP is the modern replacement for traditional WHOIS queries. Instead of returning a block of loosely formatted text, RDAP returns structured data. That matters because the result is easier to read, easier to compare across providers, and easier for software to process accurately.

A typical rdap lookup gives you the practical facts most people care about:

• the domain name itself
• the sponsoring registrar
• registration, update, and expiry dates
• nameservers
• status values
• available contact or abuse reporting details

The key point is that RDAP is about registration information, not website content. It does not tell you what a domain is “worth”, whether the site is reputable, or whether the registrant is willing to sell. It tells you how the name is registered and what its current record shows.

That makes an rdap lookup useful for buyers, operators, investigators, and advisers who need a reliable view of a domain’s current registration state without relying on outdated WHOIS formatting or incomplete summaries.

RDAP vs WHOIS: what changed and why it matters

The biggest practical change is this: for gTLD registration data, RDAP is now the definitive source. On 28 January 2025, WHOIS port 43 obligations for gTLD registries and registrars ended. In effect, the old expectation that you could query a gTLD’s registration data through classic port 43 WHOIS stopped being the required standard.

For users, that does not mean domain data disappeared. It means the access method changed. Instead of depending on legacy WHOIS text output, you now rely on RDAP responses for current gTLD registration records.

This matters for several reasons:

• RDAP data is structured, so fields are clearer and more consistent
• responses are easier to parse than free-form WHOIS text
• modern access controls and disclosure models fit better with current privacy rules
• the result is generally more predictable across different providers

Privacy is the other major part of the story. On 25 May 2018, GDPR took effect. After that, most personal registrant data in WHOIS became redacted. That reshaped user expectations. Many people still search for “owner details”, but the reality is that public registration data often no longer shows the individual or organisation behind a domain in full.

So the shift from WHOIS to RDAP is not just technical. It reflects a newer model: structured access to registration data, with privacy limits built into what users can see.

How to do an RDAP lookup step by step

Doing an rdap lookup is straightforward once you know what to look for. Whether you use a registry service, a registrar tool, or a third-party RDAP client, the process is broadly the same.

Start with the exact domain name. Enter the full domain, then load the record. If the domain exists and the service supports it, you should get a structured result rather than a plain text WHOIS block.

Then work through the record in order:

• confirm the domain name returned matches what you searched
• note the sponsoring registrar
• check the registration date
• check the expiry date
• review the last updated date
• inspect the nameservers
• read the status values carefully

Status values are particularly important. They can indicate whether the domain is locked against transfer, under registry restrictions, or moving through lifecycle stages. If you are assessing whether a name might be acquirable soon, those values can be more informative than the headline dates alone.

Keep transfer timing in mind as well. A domain usually cannot be transferred to another registrar for 60 days after registration or a registrar transfer.

Finally, compare what you see across more than one RDAP source if needed. The core record should align, but a second check can help confirm that you have read the result correctly and not relied on a stale summary or cached page.

How to read RDAP lookup results

An rdap lookup is easiest to use when you focus on the fields that answer real questions. Most users care less about protocol details and more about what the record says about the domain’s current registration position.

The most useful fields usually include the registrar, the registration date, the expiry date, the last update date, the nameservers, and the domain status values. Together, these tell you who sponsors the name, how long it has been registered, when it is due for renewal, whether anything changed recently, where the domain is routed, and whether restrictions apply.

A practical way to read the result is this:

• Registrar: who manages the registration for the registrant
• Registration date: when the domain entered its current registration life
• Expiry date: when the current term is due to end
• Last update: when the record was last changed
• Nameservers: where DNS for the domain points
• Status codes: whether transfer, update, deletion, or other actions are restricted

Contact data needs careful interpretation. In many cases, personal registrant details are limited or redacted. That does not mean the record is useless. It means you should treat the registrar, status values, and technical fields as the primary evidence.

One of RDAP’s advantages is structure. Because the data is organised into defined fields, it is usually easier to parse correctly than legacy WHOIS output, which often varied widely in layout and wording.

What an RDAP domain lookup can tell you about ownership

A common question is whether an rdap lookup reveals the owner of a domain. Sometimes it helps, but often not in the direct way people expect.

Since GDPR took effect on 25 May 2018, most personal registrant data in WHOIS became redacted, and that reality carries through to modern registration data access. So if by “owner” you mean the named individual or organisation behind a domain, public RDAP results may provide limited information or none at all.

That said, an rdap lookup can still tell you a great deal about effective control and registration context. It may show the sponsoring registrar, available abuse or contact channels, technical routing clues from nameservers, and status information that helps you understand how the domain is being managed.

This is especially useful for ownership research in the broader sense:

• identifying which registrar to contact
• spotting whether the domain is actively maintained
• seeing whether DNS points to a known hosting pattern
• checking whether the record was updated recently
• assessing whether transfer or deletion restrictions are in place

If the domain has expired, lifecycle timing also matters. After expiry, many gTLD names pass through an auto-renew grace period of up to 45 days, then a 30-day redemption period, then 5 days of pending delete.

So RDAP may not hand you a private owner’s identity, but it often gives you the operational clues needed to understand who controls the registration and what may happen next.

Can RDAP show when a domain can be transferred or dropped?

An RDAP lookup can often help you judge where a domain sits in its lifecycle, but it does not give a promise that a transfer or drop will happen on a certain day.

For transfers, the key practical point is the usual 60-day lock. A domain usually cannot be transferred to another registrar for 60 days after initial registration or after a registrar transfer. In RDAP, you may see creation and update dates, the sponsoring registrar, and status values that help you infer whether that lock may still be in effect. Some registrars also expose transfer-related status information more clearly than others.

For expiry and deletion, many gTLDs follow a broad path after expiry:

• an auto-renew grace period of up to 45 days
• then a 30-day redemption period
• then 5 days of pending delete

An RDAP lookup is useful because it can show status changes and important dates as the name moves along that path. If a domain is in redemption or pending delete, that is often a strong signal about what comes next.

Still, RDAP is a monitoring tool, not a guarantee. Registrar policies, renewals by the registrant, registry rules, and timing differences between data sources can all change the outcome. Use RDAP to track the position of the name, not to assume a transfer window or deletion date is fixed.

Why an RDAP lookup may show redacted or limited data

Many users run an RDAP lookup expecting the old style of WHOIS visibility, then assume something is broken when contact details are missing. Usually, it is not an error at all. It is the result of policy and privacy rules.

A major turning point came when GDPR took effect on 25 May 2018. After that, most registrant personal data in WHOIS became redacted. RDAP developed into the structured replacement for WHOIS, but it did not reverse those privacy limits. In many cases, it simply presents the same limited disclosure in a cleaner and more standardised format.

That means an RDAP response may show technical facts about the domain while withholding personal contact data. You might still see the registrar, registration dates, nameservers, and domain statuses, while registrant name, email, phone, or address fields are masked, omitted, or replaced with redaction notices.

The exact output can vary for sensible reasons:

• different TLDs may apply different publication rules
• different registries and registrars may expose different fields
• some providers reformat or summarise the authoritative response

So, if an RDAP lookup appears sparse, do not assume the service failed. The more likely explanation is that the underlying data is intentionally limited. RDAP is designed to improve access to registration data, not to guarantee full public disclosure of personal details.

RDAP lookup errors, mismatches and missing records

RDAP is more structured than legacy WHOIS, but users still run into practical issues. A lookup may return no result, appear outdated, or show slightly different information depending on where you query it.

A missing record can have several explanations. You may be querying the wrong service, using a provider with incomplete coverage, or looking up a name that is no longer in the zone. In some cases, the domain exists but the path to the authoritative RDAP service is not obvious from the tool you are using.

Stale results are another common frustration. One provider may cache responses or refresh less often than another. A registrar response may also differ in timing or detail from the registry response. That matters when you are tracking expiry, transfer events, or deletion status.

Status values can be confusing too. Terms such as client and server statuses often look similar but come from different layers of control. The practical answer is to focus on authoritative sources and compare them carefully where possible.

A sensible approach is to check:

• the registry RDAP response for the TLD
• the sponsoring registrar response, where available
• whether dates, nameservers, and status values align

If records do not match, do not rely on the first result you found. RDAP is only as useful as the source behind the lookup tool, and source authority matters more than convenience.

RDAP lookup for buyers, investors and brand teams

For commercial researchers, an RDAP lookup is less about curiosity and more about reducing uncertainty. It helps buyers, investors, and brand teams assess a domain’s factual position before they spend time, budget, or legal effort.

Before an acquisition approach, RDAP can confirm the registrar of record, show the creation date, and reveal status values that may affect timing. If a name appears inactive on the web, RDAP can help you test whether it is simply unused, parked, expired, or moving through a deletion path.

This is especially useful in a few recurring situations:

• due diligence before contacting an owner or broker
• checking whether expiry timing is approaching
• confirming whether a domain is locked or subject to transfer constraints
• tracking nameserver or status changes over time
• assessing whether a domain remains active or is heading towards deletion

RDAP also became more central operationally when ICANN's RDAP became the definitive source for gTLD registration data on 28 January 2025, when WHOIS (port 43) obligations for gTLD registries and registrars ended. For gTLD research, that makes RDAP the default factual starting point.

What RDAP does not do is tell you motive, beneficial ownership, or commercial intent. It is strongest as a status and infrastructure check. For buyers and brand teams, that makes it valuable precisely because it is grounded in operational facts rather than assumptions.

Best practices when using RDAP lookup data

The best way to use RDAP is to treat it as a factual status source, not a complete answer to ownership, rights, or recoverability. It tells you important things about registration state, but it does not prove beneficial ownership, trade mark priority, or entitlement to a transfer.

In practice, a single lookup is rarely enough. Domain situations change, and the useful clues often come from comparison over time. Recording key fields can make a real difference when you are trying to understand whether a name is stable, neglected, or moving towards expiry or deletion.

A practical working method is to log:

• lookup date
• sponsoring registrar
• creation, update, and expiry dates where shown
• domain status values
• nameservers
• any redaction or remark fields that explain limited data

Then compare that record with what you can observe elsewhere. Website behaviour, DNS resolution, mail configuration, and archived versions of the site can all add context that RDAP alone cannot provide. If the website is down but DNS remains active, that suggests something different from a name in pending delete.

Most importantly, avoid over-claiming from sparse records. An RDAP lookup is excellent for timing, status, and infrastructure facts, but weaker as evidence of control or legal position. For higher-value names or disputed situations, a confidential Westmore review can help turn those signals into a clearer picture.