About this whois lookup
WHOIS is the old name for the public record of who registered a domain or holds an IP block. This tool reads the same data through RDAP, the modern JSON version of WHOIS that registries and regional internet registries run over HTTPS. The classic WHOIS service on TCP port 43 is blocked for outgoing connections on our web host, so RDAP is used instead and the results are the registry's own.
For a domain you normally see the registrar, the registration, last change and expiry dates, the status codes such as clientTransferProhibited, and the authoritative name servers. For an IP address you see the allocated range, the network name and the country of the block. The full raw RDAP answer is available under the table for anyone who needs every field.
Since privacy rules took effect, registries usually redact the personal details of owners, so names, emails and phone numbers are mostly hidden. Some country domains publish no RDAP service at all, and the tool then says so instead of guessing. The text you type is sent to our API at /api/whois-lookup.php, which asks the registry for you; we do not store searches.
Which controls should I check first?
The Whois Lookup form labels its controls as Domain name or IP address. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Registration information can be redacted or represented by a privacy contact. A registration date concerns the domain record, not necessarily the launch of the current website. A registrar is different from a hosting provider. Read the record's labels and any available status explanation before assigning meaning to dates or contacts. This check cannot establish the identity of a site operator when the relevant data are withheld, and it should not fill those gaps with a guessed person.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| whois-lookup; a b.com | /api/whois-lookup.php?q=a%20b.com |
| example.com ; x | example.com |
Whose network view does this result represent?
A server-side check observes the target from the checking service's network location. Your browser, a mobile connection and another resolver can see different answers because of caching, geolocation, routing, filtering or load balancing. Keep the exact queried target and the time of your check when comparing observations. A timeout means this attempt did not obtain a result within its limit; it does not prove the target is unavailable everywhere. To investigate a discrepancy, compare the same target and protocol from the relevant client environment as a separate step.
How should I prepare a target?
Use a public target whose spelling and scope you can explain. A hostname, an IP address and a complete URL carry different information. A URL includes a scheme, path and possibly a query string, while a hostname identifies a host without those request details. Follow this page's stated input convention and omit credentials or confidential query values from demonstration targets. Correct an invalid-target message before retrying. The address is sent to the checking service for processing, so this workflow is different from a local parser that merely splits the supplied text into components.
What can I infer from missing fields?
A missing field can reflect the target, the available response or the check's scope. It should not be replaced with a guessed value. Read any status or explanation beside the output and distinguish an empty answer from an error. Compare the same type of evidence across repeated checks rather than treating every field as an independent verdict. A registration record, resolver result and HTTP response describe different layers and can disagree without any of them being fabricated. Follow a discrepancy to the layer it concerns before changing DNS, application settings or certificate configuration.
How can I document a reproducible observation?
Record the exact input, result fields that matter, and any timeout or error text. If the target is a URL, preserve the path and protocol because checking the homepage can differ from checking a specific resource. When a value appears to change, repeat a narrowly scoped check and compare the complete response, including intermediate context if the tool exposes it. Avoid attributing a difference to a named provider or person based only on one field. These outputs are observations from a limited check, not a record of ownership or an exhaustive audit of every configuration on the target.
Why can't I see the owner's name and email?
Registries and registrars redact personal contact data to comply with privacy law. You will see the registrar, dates and status, but usually not the person.
What is RDAP and how does it differ from WHOIS?
RDAP is the standard replacement for WHOIS. It returns structured JSON over HTTPS, with consistent field names, instead of free text over port 43.
Why is my country domain not found?
Some registries have not published an RDAP service. The tool reports that case rather than inventing data.
How do I find when a domain expires?
Look for the event called expiration in the table. The date is given in UTC by the registry.