WHOIS / RDAP Lookup
Check domain registration data online with RDAP-first lookup and WHOIS fallback to review registrar, status, nameservers, and renewal timing before transfers.Domain WHOIS Summary
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
|
No lifecycle fields available
The selected lookup source did not return registration dates or status fields for this domain.
|
||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
|
No public contact fields returned
Registry privacy or RDAP redaction can hide registrant, admin, technical, and billing contact values.
|
||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
|
No nameserver fields returned
The WHOIS or RDAP source did not publish nameserver fields in this response.
|
||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
|
No registrar profile fields returned
Try the WHOIS-first fallback if the RDAP source omits registrar contact fields.
|
||
Introduction
Domain registration data tells you who sponsors a domain name, which statuses control it, when key events were recorded, and which nameservers are meant to answer for it. That information often matters before a transfer, during a renewal review, after an unexpected outage, or when you need to check whether a domain is still under the registrar and delegation setup you expect.
Enter a fully qualified domain name and the page returns a current registration record with a compact summary first. You can quickly see the source used, registrar, status, creation date, update date, expiry date, age in days, and days to expiry, then move into separate views for the registrant overview, contacts, DNS, registrar details, and the raw JSON payload.
The summary is usually enough for a first decision. If the source is RDAP and the status looks normal, you may only need to confirm the expiry date and nameservers. If the domain is locked, on hold, close to expiry, or missing fields you expected, the deeper sections help you decide whether the next step belongs with the registrar, the registry, your DNS host, or your own internal records.
Public registration data is often incomplete on purpose. A blank contact block does not automatically mean bad data or a hidden owner. Many records are redacted, shortened, or disclosed only to authorized requesters. In those cases, registrar, status, dates, and nameservers become the most reliable clues the public record can still give you.
Technical Details
Registration data and live DNS answers are related, but they are not the same thing. Registration data describes the administrative state of the domain: who sponsors it, which status codes apply, what dates were recorded, and which nameservers were delegated. Live DNS tells you what records are being served right now. A domain can have a valid registration record and still fail to resolve because the nameservers are wrong, the zone is broken, or a hold status is preventing publication.
RDAP is the structured successor to WHOIS. It returns machine-readable JSON instead of unstructured text and can expose nameservers, events, entities, roles, public identifiers, and a server-reported WHOIS endpoint in a more consistent format. That matters because the same domain question can produce very different output quality across registries and registrars. Structured RDAP data is usually easier to compare, filter, and export without losing context.
The lookup path starts with the domain itself. The name is normalized to lowercase, any scheme or path is removed, and leading or trailing dots are stripped away. The result must still be a dot-separated host name made from letters, digits, and hyphens. If the name contains non-ASCII characters, it has to be converted to its A-label form before the lookup can proceed.
| Output field | Derived from | Why it matters |
|---|---|---|
Source |
RDAP first, WHOIS fallback if needed | Tells you how structured and authoritative the returned record is likely to be. |
Status |
RDAP status array or WHOIS status text | Shows whether transfer, update, delete, hold, or pending operations are affecting the domain. |
Created, Updated, Expires |
Server-reported event dates | These dates anchor age, renewal timing, audit trails, and registrar follow-up. |
Age (days) |
Computed from the creation timestamp | Useful for fast triage, but it is still a convenience count rather than a legal registration age record. |
Days to Expiry |
Computed from the expiry timestamp | Helps you spot immediate renewal risk without manually counting calendar days. |
Nameservers |
Delegation data published in the registration record | Lets you compare the delegated DNS host against the provider you intended to use. |
Registrar IANA ID |
Registrar public ID when present | Useful when brand names vary, mergers have happened, or you need a stable registrar identifier. |
Dates in the summary are not copied from a single universal field set. RDAP commonly reports event objects such as registration, last changed, and expiration. WHOIS-style providers may flatten those values into simpler date properties. The page maps those different shapes into the same summary so the output stays readable across sources.
Those two counts are convenient, but they are not exact contractual deadlines. Age (days) rounds down. Days to Expiry rounds up and never goes below zero. A domain that expires later today can still show 1, while a domain that has already crossed the timestamp can show 0. If a deadline is sensitive, trust the exact Expires value and the registrar's own billing or renewal window.
| Input case | What happens | Practical meaning |
|---|---|---|
Example.COM |
Lowercased before lookup | Mixed case is fine. |
https://example.com/path |
Scheme and path are stripped | Only the host portion is used. |
.example.com. |
Leading and trailing dots are removed | Useful when copying from zone-style notation. |
example |
Rejected | A fully qualified name with at least one dot is required. |
münich.example with Unicode characters |
Rejected unless converted to an A-label | Use the ASCII form before lookup. |
Entity roles matter when you inspect contact details. RDAP commonly identifies registrant, administrative, technical, billing, and registrar entities separately. The page maps those roles into the Contacts and Registrar Details views when they are present. If the public record omits a role, the corresponding section stays sparse instead of inventing a placeholder.
Network and storage behavior also matter here because this is not a local-only calculation. The page fetches the IANA RDAP bootstrap file to discover an authoritative RDAP service, may query that RDAP server directly, may retry through a shared HTTPS proxy if direct browser access fails, and falls back to a WHOIS-based provider when RDAP does not yield a usable result. The checked domain is therefore transmitted to external registration-data services. The browser may cache the IANA bootstrap data for about seven days, and the current domain can also appear in the URL query string for shareable state.
Everyday Use & Decision Guide
A good first pass is simple: enter the bare domain name, run the lookup, and read the summary before opening the deeper sections. Start with Source, Status, Expires, and the nameserver badges. Those fields usually tell you whether you are dealing with a healthy registration record, a transfer lock, a hold, or a renewal problem.
- Use it before a transfer to see whether
Statusincludes transfer prohibitions that will block a registrar move. - Use it during outage triage to compare the listed nameservers with the DNS provider you think should be serving the zone.
- Use it during renewal reviews to spot domains where
Days to Expiryis already at0or dangerously low. - Use it for acquisition checks to confirm registrar identity, registration age, and whether the public record is heavily redacted.
The source badge is worth noticing. RDAP usually means the record came from a structured registration service and will be easier to interpret cleanly. WHOIS fallback can still be useful, but fields may be flatter, normalized, or missing compared with a richer RDAP response. If a detail matters for money, transfer timing, or incident response, compare the result with the registrar account or another authoritative registration-data client.
A common misread is to treat a normal-looking registration record as proof that the website should work. It does not. Status can be normal while the domain still points to the wrong nameservers or the zone itself is broken. Another common misread is to treat empty contact fields as suspicious by default. Public redaction is routine, so missing personal data often tells you more about disclosure policy than about the underlying domain.
The export actions help when you need an audit trail rather than a quick check. Each table can be copied as CSV, downloaded as CSV, or exported as DOCX, and the JSON tab captures the inputs, source details, summary, section rows, and raw provider payload. If the record will drive a transfer, renewal, or security review, save the export and keep the lookup date with it because registration data can change without much notice.
If Status shows any hold or transfer prohibition, or if Days to Expiry is at 0, pause there and contact the registrar before you spend time changing DNS or troubleshooting application hosts.
How-to ยท Step-by-Step Guide
- Enter the naked domain name only, such as
example.com. - Run the lookup and note the
Sourcebadge in the summary. - Read
Status,Created,Expires,Age (days), andDays to Expirybefore digging deeper. - Open
Registrant Overviewif you need a compact audit of the primary record fields. - Open
DNSandRegistrar Detailswhen you need to confirm delegation or identify the sponsoring registrar precisely. - Use
Contactsonly as a public-record hint, not as proof that no other protected contact data exists. - Use the
JSONtab or section exports when you need a saved snapshot for a ticket, transfer checklist, or incident note.
If the checked name is sensitive, clear the query string or open a fresh page after you finish so the domain is not left sitting in the shareable URL.
Interpreting Results
The most important outputs are Source, Status, Expires, Days to Expiry, and the nameserver list. Those fields answer most practical questions about transfer readiness, renewal urgency, and whether the domain is delegated to the provider you intended.
| Result pattern | What it usually means | What to verify next |
|---|---|---|
Status contains ok or active |
The registration is generally in a normal state. | Check nameservers before assuming the domain will resolve correctly. |
Status contains clientTransferProhibited or serverTransferProhibited |
A registrar or registry lock is blocking transfers. | Confirm whether the lock is protective, temporary, or dispute-related. |
Status contains clientHold or serverHold |
The domain may not be published in DNS even though the registration still exists. | Compare with live DNS and contact the registrar immediately. |
Days to Expiry = 0 |
The expiry timestamp has passed or the domain is within the current day of expiry. | Use the exact Expires value and registrar billing state, not the rounded day count alone. |
| Contact rows are sparse or empty | Public data may be redacted, limited, or not exposed for that role. | Rely on registrar, status, and dates, then verify through an authorized registrar view if needed. |
Do not overread Age (days) or Days to Expiry as exact to-the-minute deadlines. They are useful convenience fields, not formal registry countdowns. When the number is close to zero, check the exact timestamp and the registrar account before making a time-sensitive decision.
Worked Examples
A routine ownership check before a purchase discussion
You look up a candidate domain and the summary shows Source: RDAP, Status: active, Expires: 2027-09-14T23:59:59Z, and nameservers that clearly belong to a large hosted DNS provider. The Registrar Details view includes a registrar name and a registrar IANA ID. That is a healthy public record for a first pass. It does not prove the seller controls the registrar account, but it does tell you the name is registered, delegated, and not obviously sitting in a hold or deletion state.
A transfer that will not move yet
Another domain returns Status: clientTransferProhibited with Days to Expiry: 189. The long renewal runway is fine, but the transfer status matters more than the date. In practical terms, the name is not transfer-ready even though it is not close to expiry. The next step is to ask the current registrar whether the lock is a normal anti-hijack setting, a recent change lock, or part of a dispute or registry restriction.
A domain that needs immediate renewal review
Suppose the summary shows Expires: 2026-04-11T02:00:00Z and Days to Expiry: 0. That does not automatically tell you whether the name is already out of service, inside an auto-renew grace period, or still recoverable without a fee. It does tell you the deadline is no longer distant. At that point, the useful move is to stop treating the issue as routine planning and confirm the registrar's billing state, grace period, and DNS status immediately.
A lookup that fails before it starts
You paste https://münich.example/path. The page removes the scheme and path, but the remaining Unicode label still fails validation because the lookup expects an ASCII host form. No summary appears, so there is nothing useful to interpret yet. Convert the name to its A-label form, rerun the lookup, and then read Source, Status, and nameservers as usual.
FAQ:
Why are the contact fields blank even though the domain exists?
Because public registration data is often redacted or limited. The page only shows the contact roles and fields that the upstream record actually publishes. Empty contact rows do not mean the domain lacks an owner or admin contact.
What is the difference between RDAP and WHOIS in the Source badge?
RDAP usually means the result came from a structured registration-data service with clearer entities, events, and nameserver fields. WHOIS fallback means the page had to rely on a WHOIS-based provider path instead. Both can be useful, but RDAP is usually easier to interpret cleanly.
Why does Days to Expiry differ from my registrar dashboard by one day?
Because the page computes a convenience day count from the expiry timestamp and your current device time. It rounds up and never goes below zero. Registrar dashboards may use a different timezone, cutoff, or grace-period display rule.
Why do I get the message "Enter a valid domain such as example.com"?
The lookup needs a fully qualified domain with at least one dot and only ASCII letters, digits, and hyphens in each label. Full URLs are trimmed down to the host, but Unicode labels still need conversion to an A-label before the query can run.
Does the page store anything or send my query anywhere?
Yes, a live query is sent to external registration-data services, and the browser may cache the IANA RDAP bootstrap list for about seven days. The current domain can also appear in the URL query string so the page state can be shared. The page does not maintain a separate saved history of your lookups.
If Status says active, does that mean my site should resolve?
No. It means the registration itself does not show an obvious restriction. A domain can still fail because the nameservers are wrong, the zone data is broken, or the live DNS is not what you expected. Compare the nameservers here with a live DNS check before you rule out delegation problems.
Glossary:
- RDAP
- The structured registration data protocol now used as the main public lookup path for many domain records.
- WHOIS
- The older registration lookup model that often returns text rather than a structured JSON record.
- Registrar
- The company that sponsors and manages the domain registration for the registrant.
- Registry
- The operator that maintains the authoritative database for a top-level domain.
- Registrant
- The party recorded as holding the right to use the domain name.
- Nameserver
- A delegated DNS server that is meant to answer for the domain's zone.
- EPP status code
- A standardized status label that explains whether a domain is active, locked, on hold, pending deletion, or affected by another registry or registrar state.
- IANA ID
- A stable registrar identifier published in registration data when the source provides it.
- A-label
- The ASCII form of an internationalized domain label used for DNS and RDAP lookups.
References:
- Registration Data Access Protocol (RDAP), ICANN.
- ICANN Update: Launching RDAP; Sunsetting WHOIS, ICANN, 27 January 2025.
- EPP Status Codes | What Do They Mean, and Why Should I Know?, ICANN.
- Additional Registration Data Directory Services Information Policy, ICANN, 21 February 2024.
- Bootstrap Service Registry for Domain Name Space, IANA.
- Requirements for RDAP Servers providing Domain Name Data, IANA.
- Finding the Authoritative Registration Data Access Protocol (RDAP) Service, RFC Editor, March 2022.
- JSON Responses for the Registration Data Access Protocol (RDAP), RFC Editor, June 2021.