Confirm the registrar and published domain lifecycle dates
Review structured registration, update, and expiry events without treating a published expiry date as a guaranteed deletion date.
Whois / RDAP Lookup
Free, no signup. Registry data, without old WHOIS parsing: registrar, dates, nameservers, domain locks, and clear privacy-redaction context.
Checks run from our server; we fetch the URL you enter and don't keep the results. This queries IANA's RDAP bootstrap and the relevant registry. Results may be cached for up to 24 hours; registry privacy policies can redact contacts. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report
Illustrative example — documentation-domain fixture
example.com
- Created: 1995-08-14
- Registrar: published by registry response
- Registrant: redacted by registry privacy policy
- Nameservers: observed RDAP values
- Status: clientTransferProhibited — transfer is locked at the registrar
Dates and parties in a real report are displayed only when the registry publishes them; missing values remain “Not published.”
How to use it
- Enter a root domain and choose Look up domain.
- Review registry dates and registrar separately from registrant contact data.
- Read each EPP status explanation and confirm actionable locks in the registrar account.
- Use the DNS handoff when nameserver publication needs a resolver-level check.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Registration
Parties
Nameservers
Domain status
Rate this tool
How to read the result
Registration dates are normalized registry events. Parties are registry-published roles and may be redacted. Nameservers are RDAP registration data, not a live DNS resolution test. Statuses are EPP codes with plain explanations, not independent diagnoses.
Data sources & freshness
The endpoint normalizes the domain, follows IANA’s RDAP bootstrap to the responsible registry service, and returns structured events, entities, nameservers, and statuses. The browser formats dates, calculates days to published expiry, and explains supported EPP status codes. Responses may be cached for 24 hours.
Features
- Structured registrar, date, nameserver, and status fields.
- Privacy-redaction context instead of blank-owner assumptions.
- Plain-language EPP status explanations.
- Prefilled handoff to DNS Checker.
Limitations
Some ccTLDs lack complete RDAP service, registries redact data, and published dates or parties can be absent. The tool does not bypass privacy, guarantee deletion timing, manage renewals, or replace the registrar account. Cached dataCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency. may lag a recent change.
Frequently asked questions
Why is registrant information missing?
Many registries redact registrant data under privacy policy or GDPR. Missing data is not proof the domain has no registrant.
Is this WHOIS?
It provides the same practical lookup information via RDAP, the structured successor to traditional WHOIS. Some ccTLD registries do not yet publish RDAP data.
What do clientTransferProhibited and other domain statuses mean?
They are EPP status codes published by the registry. The report explains common locks and holds, but your registrar is the authority for why a status is set and how to change it.
Is the expiry date a guarantee that the domain will be deleted then?
No. Expiry, grace, redemption, auction, and deletion policies vary by registrar and registry. Treat the published date as an operational reminder and confirm renewal in the registrar account.
Feature requests for Whois Lookup
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Understand missing or privacy-redacted registrant data
Distinguish a registry privacy redaction from a genuinely unpublished role instead of assuming a blank owner field means no registrant exists.
Review domain locks and holds in plain language
Translate common EPP status codes into useful context, then confirm the reason and any change in the registrar account.
Check which nameservers the registry publishes
Use RDAP nameserver values as registration evidence while keeping them separate from a live recursive DNS lookup.
Hand the domain into a resolver-level DNS check
Open DNS Checker with the domain prefilled when published nameservers or recent DNS changes need a separate live resolver comparison.
Watch the full workflow
Whois / RDAP Lookup walkthrough
Read the transcript
Whois / RDAP Lookup
This beginner walkthrough uses a repeatable fictional domain record to explain R-D-A-P, the structured registry-data successor used for practical Whois lookups. We will review published lifecycle dates, registrar and privacy context, nameservers, domain-lock statuses, result limitations, and the prefilled handoff into DNS Checker.
Step 1
R-D-A-P is a structured way to retrieve domain-registration data from the responsible registry service. This page focuses on the practical Whois-style facts shown in its heading: registrar, dates, nameservers, locks, and privacy-redaction context. It does not sign in to a registrar or expose private account data.
Step 2
Use the lookup to confirm published lifecycle dates, understand missing or redacted registrant data, interpret domain locks and holds, review registry-published nameservers, or hand the same domain into a resolver-level D-N-S check. Each use case keeps registry evidence separate from registrar-account actions and live D-N-S observations.
Step 3
Enter a root domain, without a page path, then choose Look up domain. The privacy note explains that the endpoint follows I-A-N-A’s R-D-A-P bootstrap to the relevant registry and may cache the response for up to twenty-four hours. Registry policy can redact contact fields, so missing contact text is not proof that nobody registered the domain.
Step 4
The sample report previews the result structure with the documentation domain example dot com. It separates the created date, registrar, redacted registrant, observed nameservers, and a transfer-lock status. Its final note is important: dates and parties appear only when the registry publishes them; otherwise the result says Not published.
Step 5
For the full workflow, enter trail dot example dot test. Dot-test is reserved for fictional examples, so this cannot expose a customer record. The capture fulfills the bounded R-D-A-P request locally with fixed registry fields and blocks every external response.
Step 6
Choose Look up domain. The button changes while the bounded request is pending, then the report opens for the normalized domain. The top card shows a countdown to the published expiry event and a separate Check D-N-S records handoff. A successful report means the registry fixture returned structured data; it does not prove control of the domain.
Step 7
The top card identifies trail dot example dot test and calculates days to its published expiry date using the fixed capture date. Treat that as an operational reminder, not a deletion promise. Grace periods, redemption, auctions, and deletion rules vary, so renewal status must be confirmed in the registrar account.
Step 8
Registration lists three normalized registry events: created on April twelfth, twenty twenty-one; updated on June thirtieth, twenty twenty-six; and expiring on February fifteenth, twenty twenty-seven. These are dates published in the R-D-A-P record. They are not billing receipts, renewal settings, or proof of a future deletion time.
Step 9
Parties keeps two roles separate. Example Registrar is the fictional published registrar. The registrant value says Redacted by registry privacy policy because no public name was returned and the response carries redaction context. That wording avoids the false conclusion that the domain has no registrant.
Step 10
Nameservers lists N-S-one and N-S-two dot example dot test because those are the values in the registry fixture. They show what R-D-A-P publishes for the registration. They do not confirm what Cloudflare, Google, Quad Nine, or another recursive resolver returns right now.
Step 11
Domain status explains two E-P-P codes. Client transfer prohibited means the registrar has locked transfers by request or policy. Server delete prohibited means the registry is preventing deletion. These explanations describe the published codes. The registrar or registry remains the authority on why a status is present and how it can change.
Step 12
Read the report as four bounded evidence groups: registry events, published parties, nameservers, and status codes. A missing value stays Not published. Redaction remains explicit. Plain-language explanations help with triage, but none of these sections independently diagnoses a registrar-account problem or live D-N-S failure.
Step 13
Choose Check D-N-S records. The local handoff opens DNS Checker and prefills trail dot example dot test. It does not run a resolver query automatically or carry registry contacts. This is the correct next surface when the question changes from what the registry publishes to what recursive resolvers currently observe.
Step 14
The result-reading section states the boundaries directly. Dates are normalized registry events. Parties may be redacted. Nameservers are registration data, not a live D-N-S test. Statuses are E-P-P codes with explanations, not independent diagnoses. Those distinctions keep each field useful without overclaiming what it proves.
Step 15
The data-source section explains the lookup path: normalize the domain, use I-A-N-A’s bootstrap to select the responsible registry service, and return structured events, entities, nameservers, and statuses. The browser formats dates and explains supported status codes. Cached responses may lag a recent registry change by up to twenty-four hours.
Step 16
The main features are structured registrar, date, nameserver, and status fields; privacy-redaction context instead of blank-owner assumptions; plain-language E-P-P status explanations; and a prefilled handoff to DNS Checker. All four features stay tied to registry-published data and an explicit next step.
Step 17
Some country-code registries lack complete R-D-A-P service, and registries can omit dates or parties. The tool cannot bypass privacy, guarantee deletion timing, manage renewals, or replace the registrar account. Cached data may lag. Confirm renewal and lock changes with the registrar, and use the D-N-S handoff only when you need separate resolver evidence.
Treat the RDAP record as published context—not account access.
Save the exact domain, observed registrar, published dates, nameservers, status codes, and lookup date with your notes. Confirm renewal, lock reasons, and any requested changes inside the registrar account. If the question is what recursive resolvers currently return, continue with the prefilled DNS Checker instead of treating R-D-A-P nameserver data as a live DNS test.
Common issues & how to fix them
- Error Domain has serverHold status Fix: Contact the registrar or registry to resolve the serverHold cause before expecting DNS publication to resume.
- Error Domain has clientHold status Fix: Resolve the registrar’s clientHold condition, then confirm the status clears and authoritative DNS answers return.
- Error Domain is in redemption period Fix: Request domain restoration through the registrar and pay any redemption fee before the redemption period ends.
- Error Domain is pending deletion Fix: Confirm whether restoration is still possible; otherwise monitor the registry drop because ordinary renewal is no longer available.
- Warning Domain registration expires soon Fix: Renew the domain now, enable auto-renew with valid payment details, and verify the updated RDAP expiration date.
- Information Registration identity is redacted Fix: Use authenticated registrar records for ownership verification because public RDAP redaction is normal and cannot be repaired on the website.
- Information DNSSEC is not indicated Fix: Enable DNSSEC at the DNS provider, publish the DS record through the registrar, and verify the chain of trust.