1
Enter the Domain Name
Type the domain name (e.g., google.com) in the input field. Enter the bare domain only — no http://, no www prefix, no trailing slash.
Domain WHOIS Lookup |
Look up the registered owner, registrar, nameservers, and expiry date for any domain name.
More Tools
Domain WHOIS Lookup — What It Returns
Domain WHOIS lookup retrieves the registration record for any domain name by querying its authoritative RDAP server (RFC 9083) with a legacy WHOIS port 43 fallback (RFC 3912) when RDAP is unavailable. Results include the registrar, registered owner or organization, creation date, expiry date, nameservers, and EPP domain status codes. Data is sourced live from the domain's TLD registry via the IANA bootstrap routing service — no cached or third-party data is used.
| Field | Detail |
|---|---|
| Primary protocol | RDAP over HTTPS (RFC 9083, RFC 7480) |
| Fallback protocol | Legacy WHOIS, TCP port 43 (RFC 3912) |
| RDAP routing | rdap.org — IANA bootstrap redirect (RFC 7484) |
| Data redaction | gTLD registrant data redacted post-GDPR (May 2018) |
| Domain age | Calculated from creation date to today (years, months, days) |
| Status codes | EPP format per RFC 5731 (e.g., clientTransferProhibited) |
WHOIS vs RDAP — Two Protocols, One Record
WHOIS and RDAP query the same underlying registration data but differ in protocol, response format, and standardization. RDAP has been the ICANN-mandated standard for gTLD registration data since August 2019, though both protocols remain active.
| Feature | WHOIS (RFC 3912) | RDAP (RFC 9083) |
|---|---|---|
| Transport | Plain text, TCP port 43 | Structured JSON over HTTPS |
| Response format | Unstructured, varies by registrar | Standardized, machine-readable |
| Internationalization | Limited, ASCII-focused | Full Unicode support |
| Privacy controls | None native | Built-in redaction fields |
| ICANN mandate | Legacy standard | Official standard since 2019 |
| Error handling | Inconsistent text messages | HTTP status codes (404, 200, etc.) |
Domain WHOIS Lookup — How to Use
Look up RDAP and WHOIS registration data for any domain in seconds.
2
Submit the Lookup
Click "Lookup Domain WHOIS". The tool queries the authoritative RDAP server for the domain's TLD via the IANA bootstrap registry, with a WHOIS port 43 fallback.
3
Review Ownership and Registrar
Check the Ownership & Registrar section for the registered organization, registrar name, country, and abuse contact email.
4
Check Lifecycle and Expiry
Review the Lifecycle & History section for creation date, expiry date, domain age, and the days remaining until registration expires.
5
Read the Raw WHOIS Record
Scroll to Full WHOIS/RDAP Record for the complete raw data returned by the registry server. Use the Copy Record button to export it.
What Domain WHOIS Results Mean
| Field | Meaning | Example |
|---|---|---|
| Registrar | The accredited company where the domain was purchased | NameCheap, Inc. |
| Organization | Registered owner's company or individual name (may be redacted) | Cloudflare, Inc. |
| Abuse Contact | Email address to report domain abuse or spam | [email protected] |
| Created | Date the domain was first registered | 2010-03-15 |
| Expires | Date the registration expires if not renewed | 2027-03-15 |
| Domain Age | Time elapsed since first registration | 15y 2m 3d |
| Days Left | Calendar days until expiry date | 672 Days |
| Status Codes | EPP codes governing what actions are permitted on the domain | clientTransferProhibited |
| Source | Protocol used to retrieve the record | RDAP or Legacy |
How Domain WHOIS Lookup Works
Domain WHOIS lookup is driven by two protocols in sequence. The tool first attempts an RDAP query via rdap.org, which implements the IANA RDAP bootstrap registry (RFC 7484). The bootstrap registry maps each TLD to its authoritative RDAP server — for example, .com queries route to VeriSign's RDAP endpoint, while .org routes to the Public Interest Registry. The RDAP response conforms to RFC 9083, returning structured JSON with standardized field names across all TLDs.
When RDAP is unavailable for a domain or TLD, the tool falls back to legacy WHOIS over TCP port 43, as specified in RFC 3912. The legacy path first queries whois.iana.org to obtain the authoritative WHOIS server for the domain's TLD via a WHOIS referral, then sends the domain query directly to that server.
Domain status codes follow the Extensible Provisioning Protocol (EPP) format defined
in RFC 5731. Common codes include clientTransferProhibited
(transfer locked by the registrar), serverHold
(domain suspended by registry — not resolving in DNS), and
pendingDelete (domain in the deletion grace period, available soon).
Domain age and days-to-expiry are calculated server-side from the creation and
expiry dates returned by the registry.
Do it yourself
How to Run a Domain WHOIS Lookup Without an Online Tool
The whois command queries the same registry servers this tool uses.
Results may include full registrant data not shown here if queried from a server
outside the EU registrar zone.
Mac / Linux Built-in whois command
whois google.com# Query a specific WHOIS server directly (for known TLD servers)
whois -h whois.verisign-grs.com google.comThe whois command is built into macOS and most Linux distributions and automatically routes to the authoritative WHOIS server for the TLD.
Windows curl with RDAP API (built into Windows 10 version 1803+)
curl "https://rdap.org/domain/google.com"
Windows has no native whois command. The curl command above
queries the RDAP API (RFC 9083) and returns structured JSON — the same data source
this tool uses. curl is built into Windows 10 (version 1803 and later)
and Windows 11.
Windows PowerShell
Invoke-RestMethod "https://rdap.org/domain/google.com" | ConvertTo-Json -Depth 5Any platform RDAP with formatted JSON output (requires Python 3)
curl "https://rdap.org/domain/google.com" | python3 -m json.toolThe online tool and the commands above query the same IANA-routed RDAP servers. Results may differ from locally cached WHOIS data if registration records were recently updated, since RDAP queries the authoritative source directly.
Common Uses for Domain WHOIS Lookup
Domain acquisition due diligence. A startup founder wants to acquire
brandname.io, listed for sale on a broker site. Before negotiating, they
run a WHOIS lookup to confirm the creation date (registered in 2014 — not a
freshly parked speculative registration), verify the registrar, and check the expiry
date to assess whether the seller faces renewal pressure.
Phishing domain investigation. A SOC analyst receives a suspicious
email originating from secure-paymentupdate.net. The WHOIS lookup
shows the domain was created four days ago, the registrar is commonly associated
with throwaway registrations, and the status shows clientHold —
the registrar has already suspended it. The creation date and registrar pattern
are recorded in the threat intelligence report.
Expiry monitoring for client portfolios. A web agency managing 30 client domains runs WHOIS checks quarterly. During a routine pass, one domain shows 11 days until expiry — auto-renewal had failed silently after a card change. The WHOIS expiry date triggers an emergency manual renewal before DNS goes dark.
Frequently Asked Questions
What is a domain WHOIS lookup?
Domain WHOIS lookup queries a domain's registration data from the authoritative WHOIS or RDAP server for its TLD.
Results include the registrar, registered organization, creation date, expiry date, nameservers, and EPP domain status codes.
The protocol originates from RFC 954 (1985) and is now standardized as legacy WHOIS (RFC 3912, TCP port 43)
and RDAP (RFC 9083) for structured JSON responses over HTTPS.
How accurate is domain WHOIS data?
WHOIS accuracy varies by TLD and registration date. Since GDPR enforcement began in May 2018,
most gTLD registrars (.com, .net, .org) redact registrant name, email, and phone number, replacing
them with proxy contact data. The registrar name, creation date, expiry date, nameservers, and
domain status codes are maintained by the registry itself and are almost always accurate.
What is the difference between WHOIS and RDAP?
WHOIS (RFC 3912) queries a server on TCP port 43 and returns unstructured plain text whose format
varies by registrar. RDAP (RFC 9083, RFC 7480) returns structured JSON over HTTPS, with standardized
field names, full Unicode support, and built-in privacy controls. RDAP has been the ICANN-mandated
standard for gTLD registration data since 2019. This tool queries RDAP first and falls back to
legacy WHOIS port 43 if the RDAP server is unavailable.
Why does my domain WHOIS show 'Redacted for Privacy'?
GDPR (General Data Protection Regulation), effective May 2018, requires registrars operating in the
European Economic Area to limit public disclosure of personal data. Most gTLD registrars responded
by redacting registrant name, email, and phone number for all registrations globally.
The registrar name, domain status codes, nameservers, creation date, and expiry date remain
publicly accessible. Business and organization registrations sometimes retain more registrant data by choice.
Do you store or log the domains I look up?
No. This tool queries RDAP and WHOIS servers in real time and returns results directly to your browser.
The domain name entered is not stored, logged, or shared with third parties.
How do I contact the owner of a domain using WHOIS data?
WHOIS results include an abuse contact email that routes to the registrar's abuse department.
For business domains, a registered organization contact may also appear. If registrant data is
redacted, most registrars provide a web-based contact form — often linked in the RDAP record —
that forwards messages to the registrant without exposing their email address.
The registrar's general contact is always available as a fallback.