How to use the domain WHOIS lookup
Enter a domain such as example.com and select Look up domain. This registration query requests public registration data through RDAP, using the registry endpoint published in IANA's directory. The registration query result identifies the queried name, the registry URL and the retrieval time. Registration information can help explain a transfer problem, identify a registrar or find published contacts. It does not identify the person operating a website reliably.
Read more
Enter the exact registration name. A subdomain is not removed or replaced with a guessed registrable domain. If a query for www.example.com has no record, investigate the intended registration name rather than treating that result as proof that the website is unregistered.
Internationalized names are converted to their ASCII DNS representation, which stays visible in the result. Similar-looking Unicode characters can refer to different names; normalization does not endorse the domain’s identity.
RDAP behind the domain WHOIS lookup
The IANA RDAP directory supplies the longest matching label-suffix endpoint. Our server queries that registry and validates the returned name. Registrar links remain available for manual inspection; the application does not automatically fetch arbitrary URLs contained in a record.
Read the domain WHOIS lookup result
Begin with the outcome and source. A successful registration query requires a domain object whose normalized name matches your submission. A response for another name is not shown as a successful result. The registry handle is an identifier within that registry's system; it is not a password, transfer authorization code or proof that a particular account controls the domain. Keep it alongside the source when opening a support case.
Read more
The registrar name comes from an entity explicitly marked as a registrar. Public identifiers can include its IANA identifier. Missing names remain unavailable. An organization appearing elsewhere in the record is not automatically the registrar or domain owner.
Events retain the source’s action and date. Registration, expiration, last changed and database update are different events, and multiple rows remain separate. Retrieval time describes when the response was obtained. It does not replace the source’s dates or predict the next registry update.
Registry status values in the registration query are preserved as returned. A transfer-prohibited state can explain why a transfer needs further action; it does not alone demonstrate a security incident. Several statuses may coexist. Use the registrar's instructions and ICANN's status-code reference to interpret the exact combination. Avoid removing a protective lock merely because a troubleshooting guide mentions transfers.
Registered nameservers are the names supplied by the registry, rather than a live DNS propagation measurement. Compare an explicit NS query in DNS lookup when investigating delegation. A listed server is not a guarantee that it responds correctly.
The registration query also displays the registry's delegation-signed and zone-signed declarations when present. False and missing are different outcomes. A true declaration is not a live validation of DNSSEC signatures or the chain of trust, and it says nothing about the website's TLS certificate. The underlying fields are defined in the RDAP response specification. Use a dedicated DNS investigation when you need validation evidence.
Domain WHOIS lookup contacts, privacy and redaction
Expand Public contacts and roles after a registration query to inspect returned names, organizations, email addresses, telephone details and postal addresses. Empty values stay absent. The tool displays contact text rather than automatically calling, emailing or requesting those addresses. Treat public contact information as purpose-specific registration data. A contact row can represent a service provider or privacy service and should not automatically be labeled the website owner's personal identity.
Declared field redactions in the registration query show structured redaction names, reasons and methods when the registry includes them. The RDAP redaction specification defines a way to describe withheld or replaced fields. The registration query does not attempt to reconstruct withheld values. It does not query historical contact databases, bypass access restrictions or claim that a missing field can be recovered from a different spelling of the domain.
Domain WHOIS lookup limits and failure states
A registration query can return a registry RDAP 404 for the exact submitted name. This is not a purchasing recommendation or an availability guarantee. A spelling mistake, subdomain query, reserved name or registry-specific policy may need further investigation. If you are considering a registration, check with an appropriate registrar. This tool does not place orders, reserve names, provide prices or determine trademark rights.
Read more
An unsupported outcome in the registration query means the IANA directory did not provide a usable HTTPS service for this query. It does not establish that the suffix is invalid or that the domain is unregistered. Some suffixes have different public registration arrangements. Consult the responsible registry's published service. We do not silently send the name to an unrelated commercial lookup provider to replace missing coverage.
Access-restricted and rate-limited outcomes stay separate in the registration query. The former reports an HTTP 401 or 403; the latter reports HTTP 429. A shared server address can encounter a provider restriction even when a browser on another network reaches that provider. Repeated submissions do not improve the evidence. Wait before retrying, or inspect the named source directly. A restriction must never be presented as a clean or empty registration record.
The registration query summary covers the fields described on this page, not every possible RDAP extension. Long lists, deep entity structures and oversized display values are bounded, and shortening is flagged. The original registry source remains available for inspection. A structured summary can help compare routine fields, but preserve the source response separately when an investigation requires every extension, signature, policy statement or machine-readable field.