Normalize the name
The input is reduced to a registrable ASCII domain; URLs, paths and credentials are not sent to WHOIS.
Direct answer: A WHOIS lookup retrieves the registration text published by the responding registry or registrar, while preserving the source server, referral path and observation time.
The server sends the normalized domain to IANA and, when published, the referred registry or registrar WHOIS service. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this whois lookup tells you
Use this lookup when you need the legacy text record returned by a registry or registrar WHOIS service. The result preserves the responding server and raw response because labels and availability differ by operator.
- Which WHOIS service responded and whether it supplied a referral
- The registration dates, status codes, registrar and nameservers that service chose to publish
- Whether a legacy port 43 record is still available for this domain
When the free-form response is ambiguous, compare it with the structured RDAP lookup and keep the source URL and observation time for both results.
For a Unicode name, use the IDN and Punycode converter to confirm the exact ASCII form before interpreting the record.
To verify the sponsoring provider named in the record, follow the sponsoring registrar verification guide instead of treating a reseller or privacy service as the registrar.
How the evidence is collected
Follow the referral
The client starts with the relevant WHOIS service and follows a published referral only when it remains within safe network limits.
Preserve the evidence
Read the server, UTC query time and raw text together. Free-form field names are not silently treated as universal facts.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| Registrar | The sponsoring registration provider published by the service. | The website host or beneficial owner. |
| Registry expiry | A registry lifecycle timestamp when supplied. | A guaranteed deletion or public purchase time. |
| Status code | An EPP restriction or lifecycle state. | A reputation or safety score. |
| Nameserver | A delegation target associated with the domain. | The origin web server or site operator. |
A record shows clientTransferProhibited and a privacy service
Read the status as a registrar-set transfer lock. Read the privacy contact as the public contact selected for the record. Neither observation establishes who authors the website. For current gTLD registration data, compare the legacy response with RDAP because contracted WHOIS obligations were sunset in January 2025.
Common mistakes
- Treating a privacy provider as evidence of misconduct
- Confusing registry expiry with the registrar's customer renewal deadline
- Assuming no WHOIS response means the domain is available
- Dropping the source server and query time when saving a result
WHOIS Lookup FAQ
Why is contact data missing?
It may be redacted by policy, represented through a privacy or proxy service, or unavailable from that service. Missing public data is not proof that no registrant exists.
Is WHOIS still authoritative?
For gTLDs, RDAP became the definitive standardized service after legacy WHOIS obligations ended. Some ccTLDs and operators still provide useful WHOIS responses under their own policies.
Can I use the expiry date to catch a domain?
No. Renewal, grace, redemption, auction and registry processes intervene. Treat it as one monitoring signal, not a release promise.