A registration lookup helps you inspect a domain’s public registration record. It can provide the registrar, status information and relevant dates, but it is not a complete biography of the holder or a certificate that the domain is safe to use.
People still call this a WHOIS lookup. For gTLDs, ICANN’s transition notice identifies RDAP as the definitive registration-data service from 28 January 2025. Country-code extensions can follow their own arrangements, so check the operator’s current lookup instructions.
Enter the exact name and record the source
Use ICANN Lookup for supported names or the relevant official registry or registrar service. Enter the domain itself, with the correct extension, rather than a full page URL. Keep the time and source of the result with your notes.
If a result is missing or unexpected, check the spelling and lookup service’s scope. An unsupported extension, temporary service problem or cached third-party record can explain uncertainty. Do not interpret an empty response as proof of registration availability.
Our registration check guide explains why the registrar’s current order result is a separate acquisition check. A website failing to load is another observation again.
Read the fields according to their purpose
- The registrar identifies the registration service associated with the name.
- Event dates describe the events the record labels; they are not a full history of website use.
- Nameservers identify DNS delegation rather than prove who runs the website.
- Status codes describe particular registration or operational conditions.
- Contact fields may be public, redacted or represented through a privacy or proxy service.
Use ICANN’s EPP status guide to interpret codes. A transfer prohibition may be a protective lock. An expiry-related status may involve holder rights or restrictions, so do not convert the label into a predicted release time.
Understand the limits of public contact data
ICANN’s privacy and proxy guidance distinguishes the services. A privacy arrangement can substitute contact details while the customer remains the holder; under a proxy arrangement the provider is the holder of record and licenses use. Public-data redaction is another distinct issue.
A hidden personal email is not evidence of criminal behaviour. Use the published contact or forwarding route where appropriate and respect its conditions. A registration record does not establish that a person claiming to sell the name has authority to complete a sale.
Our privacy guide explains the implications for owners. Do not publish or collect unrelated personal details merely because they appear in a lookup result.
Connect the lookup to the question you are answering
For an acquisition, verify the listing and delivery route independently. For a suspected security problem, preserve the exact domain and relevant evidence, then use the appropriate provider’s official reporting process; a lookup cannot diagnose everything behind a malicious page.
For historical use, inspect archives and other dated evidence rather than assuming the current record lists every previous holder. Our historical review checklist helps keep those sources separate.
In a hypothetical assessment, record “public registration found; contact redacted; current sale authority unverified”. That is an accurate research position and a better basis for the next check than calling the domain anonymous or automatically safe.