Free WHOIS Lookup Online

WHOIS Lookup: Find Who Registered a Domain, When, and When It Expires

A WHOIS lookup answers a different question than a DNS lookup does — instead of asking what a domain resolves to, it asks who registered it, through which registrar, on what date, and when the registration is due to lapse. This tool takes a domain name, contacts the WHOIS system on your behalf, and hands back both a structured summary — registrar, creation date, last-updated date, expiry date, name servers, and status codes — and the complete raw response text underneath it, so nothing the registry actually said gets hidden behind the summary.

The lookup itself happens on the server, not in your browser: the domain you enter is sent to FreeConvertingTools, which then queries the WHOIS system over the classic port-43 protocol and returns whatever comes back. WHOIS predates the modern web by decades and was never standardized into a single machine-readable format — every registry formats its response slightly differently, which is exactly why this tool gives you both a best-effort parsed view for the fields people check most often, and the raw text underneath for anything the parser didn't catch.

How to Run a WHOIS Lookup with This Tool

1. Enter the domain you want to check into the field — a bare domain such as example.com works; a pasted URL has its protocol and any trailing path stripped automatically before the query goes out.
2. Click Lookup (or press Enter). Behind the scenes, the server first asks whois.iana.org which server is authoritative for that domain's top-level domain, then queries that specific referral server for the domain itself — two hops, both to fixed, well-known WHOIS servers rather than anything you control.
3. A summary card appears first, listing the registrar, creation date, last-updated date, expiry date, and which WHOIS server actually answered the second query.
4. If the registry published a name server list, it appears in its own section as a set of hostnames — useful for cross-checking against what an NS record lookup independently reports.
5. Domain status codes (things like clientTransferProhibited or clientDeleteProhibited) show up in their own section when the registry included them, describing locks and restrictions currently applied to the registration.
6. A collapsed "Raw WHOIS response" panel sits underneath everything else — expand it any time to read the registry's original, unedited text, which is the authoritative record if a field you need wasn't picked up by the summary.

Why People Look Up WHOIS Records

• Checking when a domain expires. Whether you're evaluating whether a domain someone else owns might become available, or making sure your own registration doesn't lapse unexpectedly, the expiry date is the single most commonly checked field in a WHOIS record.
• Identifying the registrar behind a domain. Knowing which company a domain is registered through matters for anything from a transfer request to a legal notice to simply figuring out where to even begin if you need to contact whoever controls it.
• Confirming a domain's registration history. The creation date establishes how long a domain has existed, which is a common signal used informally when evaluating whether a site is an established, long-running property or a domain registered very recently.
• Cross-checking name server delegation. The name servers listed in a WHOIS record should match what a DNS lookup's NS query reports; a mismatch usually means a delegation change hasn't fully propagated yet, or points at a misconfiguration worth investigating further.
• Understanding a domain lock or transfer block. Status codes like clientTransferProhibited explain, directly from the registry, why an attempted transfer to a new registrar might be failing — information that isn't visible anywhere else without asking WHOIS specifically.
• Due diligence before a purchase or partnership. Anyone considering buying a domain, evaluating a business's web presence, or investigating a suspicious site benefits from an independent, registry-sourced view rather than relying only on what the site itself displays.

How the Two-Hop Query Actually Works

WHOIS has no single central server that knows every domain in every top-level domain — instead, whois.iana.org acts as a directory that, given a top-level domain like ".com" or ".org," tells you which registry's WHOIS server is authoritative for it. This tool queries IANA first, extracts that referral server from the response, and then sends a second query — this time for the actual domain — to whichever server IANA pointed at. Both of those connections are to servers the tool decides on its own (the fixed IANA host, then the referral host IANA itself supplied), never to a server you specify directly, which is a meaningfully different security shape from a tool that connects to an arbitrary host you type in.

Field	What it describes	Completeness
Registrar	The company through which the domain is registered	Present for nearly all gTLDs; varies for some ccTLDs
Created	The original registration date	Widely present
Last Updated	Date of the most recent registration record change	Widely present
Expires	Date the current registration term ends	Widely present
Name Servers	Authoritative DNS servers the registry has on file	Usually present, format varies
Status	Registry-applied locks/states (transfer, delete, update prohibitions, etc.)	Present when the registry applies any

Because this is a free-text protocol with no universal schema, the "Completeness" column above is a realistic expectation rather than a guarantee — some country-code registries omit fields entirely, redact registrant details for privacy reasons, or format dates and labels in ways the parser simply won't recognize. That's a limitation of WHOIS itself, not of this tool specifically, which is exactly why the raw response is always included: if a field you need isn't in the summary, it's very often still sitting in the raw text in a slightly different label than the parser was looking for.

A Note on Security and What Gets Contacted

Unlike some other tools in this network category, WHOIS lookup doesn't take a URL or hostname and connect to whatever you supply — it only ever contacts two fixed, known-good WHOIS servers (IANA's own, and the referral server IANA's own response names), never a server address you control or type in yourself. That narrows the risk profile considerably compared with, say, a tool that opens a connection to an arbitrary host a visitor provides. Even so, both of those connections still pass through the same public-address validation this site applies to every outbound network hop, purely as an extra layer of caution — cheap insurance against a tampered or unexpected referral response, even though the registration lookup itself was never the tool category's primary SSRF concern the way host-supplied targets are for tools like the SSL certificate checker.

Common WHOIS Pitfalls

The biggest one is expecting a fully populated result every time. Privacy services, redaction rules that vary by registry, and country-code top-level domains that simply don't publish certain fields all mean a "blank" registrar or date field is common and doesn't indicate an error in the lookup — it usually reflects what the registry itself chose to disclose. A second pitfall is confusing the registrar with the actual owner: WHOIS tells you who the domain is registered through, and in some cases contact details for the registrant, but many registrations use privacy/proxy services precisely to keep the underlying owner's information out of the public record, so the registrar name is not the same thing as knowing who runs the site. A third is treating name server data from WHOIS as more current than an actual DNS lookup — WHOIS name server fields are what the registry has on file, which can lag slightly behind a delegation change that already took effect at the DNS level; if the two disagree, the live DNS answer is the more current one.

Manual WHOIS Lookup vs. Using This Tool

• The whois command-line client. Available by default on macOS and most Linux distributions, it does the same two-hop query this tool does, but isn't installed on Windows without extra setup, and dumps raw text with no summary.
• A registrar's own WHOIS page. Many domain registrars offer a lookup box on their own site, but some limit results to domains registered through them, or add marketing prompts to buy an available-looking domain rather than a clean, neutral result.
• ICANN's Lookup service. A reasonable general-purpose option, though its output format and field coverage differ from what any given registry actually returns, since it's applying its own normalization layer on top.
• Scripting the raw protocol. Opening a socket to port 43 and sending a query manually is straightforward in most languages, and makes sense if WHOIS checks need to run as one step inside a larger automated process.
• This tool's API. For anyone wiring registration checks into a renewal tracker, a monitoring dashboard, or a script instead of clicking through a browser, this lookup is also exposed as a metered API call — post a domain and receive the parsed fields plus the raw text as JSON; the API documentation details exactly what to send and what it costs in credits.

Why are some fields in my WHOIS result blank?

WHOIS has no single required format, so registries vary in what they publish and how they label it. A blank registrar, date, or name-server field usually means that particular registry either didn't include it in this response or formatted it differently than the parser expected — check the raw response panel, since the value is often present there under a slightly different label.

Does looking up a domain reveal the owner's personal contact information?

Not reliably. Many registrations use a privacy or proxy service that substitutes the provider's own contact details for the registrant's, and this is standard practice for the large majority of domains registered by individuals. This tool reports exactly what the registry's WHOIS server returns — it doesn't attempt to look behind a privacy service.

Is this the same information a DNS lookup provides?

No. A DNS lookup shows what a domain currently resolves to — its IP addresses, mail servers, and similar records, sourced live from the domain name system. A WHOIS lookup shows registration details from the registry instead — who registered the domain, through which registrar, and when it expires. The DNS lookup tool covers the first question; this one covers the second.

Can I check a domain that hasn't been registered yet?

Yes, and the response itself usually makes that clear — an unregistered domain typically returns a "No match" or "Not found" style response from the registry rather than any registrar or date fields, which is a reasonably reliable (though not perfectly authoritative) signal that the name is currently available.

Related Network Tools

Registration details are only part of the picture for a domain. Pair this lookup with the DNS lookup tool to see what the domain currently resolves to, or the SSL certificate checker to confirm whatever host answers for it is presenting a valid certificate. If you're evaluating a site more broadly, the website status checker and HTTP headers viewer round out the picture with how the live site actually responds.