Can I find out who owns a domain when the WHOIS details are redacted?

Not from the public record. The registrar holds the registrant's details and forwards messages through a contact form or relay address shown in the record. Registrars also disclose redacted data to parties with a legitimate interest, such as a rights holder or law enforcement, through their own request process.

Why does the expiration date in WHOIS not match what my registrar shows?

Many registries renew a domain automatically on its expiration date and move the registry date forward a year, while the registrar still waits for the customer to pay. The registry record can then show a later date than the registrar's account page. The registrar's date is the one that decides whether the domain lapses.

Does the owner see that I looked up their domain?

No. A WHOIS or RDAP query goes to the registry or registrar, never to the domain owner or the site. The owner has no way to see who looked up the record.

Who owns a domain? WHOIS and RDAP lookups

To find out who owns a domain, run a WHOIS or RDAP lookup on it: whois example.com in a terminal, or an RDAP query over HTTPS such as curl -sL https://rdap.org/domain/example.com. What you will usually get is the registrar, the registration, expiration and last-changed dates, the status codes and the nameservers. The registrant’s name and contact details are mostly redacted, as they have been since the GDPR took effect in May 2018. When they are, the registrar’s contact form or relay address is the legitimate way to reach the owner.

WHOIS and RDAP: two ways to ask the same registry

WHOIS is one of the oldest internet protocols. A client opens TCP port 43 on a server, sends a domain name and gets plain text back. There is no fixed format, so every registry lays its answer out differently.

RDAP, the Registration Data Access Protocol, is the IETF-standardised successor. It serves the same registration data over HTTPS as JSON, with defined field names and a standard way to mark data as redacted. A bootstrap file published by IANA says which RDAP server answers for each top-level domain. Registries and registrars both run RDAP servers. For generic top-level domains such as .com and .org, ICANN has made RDAP the authoritative source and no longer requires the old WHOIS service, so some port-43 servers return less than they used to.

Two parties hold the data. The registry runs the top-level domain; the registrar sells the name to the customer. For some top-level domains the registry keeps only the core record and points to the registrar’s own server for the rest.

What a lookup still shows, and what it hides

Usually visible	Usually redacted
Registrar	Registrant’s name
Registration (creation) date	Postal address
Expiration date	Email address and phone number
Last-changed date	Administrative and technical contacts
Status codes, such as `clientTransferProhibited`
Nameservers

Some records still show the registrant’s organisation, region or country. Many show “REDACTED FOR PRIVACY”, or the name of a privacy service, in place of the contact fields.

How to look up who owns a domain by hand

With the whois command

whois example.com

The whois client ships with macOS and is a standard package on Linux distributions. The answer has this shape; the values here are illustrative:

Domain Name: EXAMPLE.COM
Registrar: Example Registrar, Inc.
Updated Date: 2026-08-14T09:12:03Z
Creation Date: 1995-08-14T04:00:00Z
Registry Expiry Date: 2027-08-13T04:00:00Z
Domain Status: clientDeleteProhibited
Domain Status: clientTransferProhibited
Name Server: NS1.EXAMPLE.NET
Name Server: NS2.EXAMPLE.NET
Registrant Name: REDACTED FOR PRIVACY

Many whois clients follow a referral from the registry to the registrar’s server and print both answers, so the same field can appear twice with different wording.

With an RDAP query

curl -sL https://rdap.org/domain/example.com

rdap.org is a redirector. It looks up the top-level domain in the IANA bootstrap file and answers with a redirect to the registry’s RDAP server. -L makes curl follow that redirect; without it, you get the redirect and no data. The full JSON is long, so jq helps:

curl -sL https://rdap.org/domain/example.com | jq '{status, events, nameservers: [.nameservers[].ldhName]}'

Illustrative output:

{
  "status": ["client delete prohibited", "client transfer prohibited"],
  "events": [
    { "eventAction": "registration", "eventDate": "1995-08-14T04:00:00Z" },
    { "eventAction": "expiration", "eventDate": "2027-08-13T04:00:00Z" },
    { "eventAction": "last changed", "eventDate": "2026-08-14T09:12:03Z" }
  ],
  "nameservers": ["NS1.EXAMPLE.NET", "NS2.EXAMPLE.NET"]
}

RDAP writes status codes as words (“client transfer prohibited”), where WHOIS uses the compact form (clientTransferProhibited). The registrar sits in the entities array, with the role registrar.

On a lookup web page

Most registrars offer a lookup form on their site, and ICANN runs one for generic top-level domains. They query the same records and show the same fields, which is convenient when you have no terminal at hand. Many country-code registries run their own lookup page.

In the StatsMyWeb domain report

Open the domain report for example.com, or replace the domain in the address with any other. Its WHOIS section shows the registrar, the registration date, the expiration date, the last-changed date, the status codes and the nameservers. It is a live check: the data is fetched through rdap.org via RDAP when you open the report. If the top-level domain offers no RDAP service, the section stays empty. The methodology page explains the source.

What the common status codes mean

Status codes come from EPP, the protocol registrars use to talk to registries. Codes starting with client are set by the registrar; codes starting with server are set by the registry and override them.

Code	Meaning
`ok`	No restrictions and no pending operation
`clientTransferProhibited`	The registrar blocks transfers to another registrar; the usual lock against hijacking
`clientUpdateProhibited`	The registrar blocks changes to the record, such as nameservers
`clientDeleteProhibited`	The registrar blocks deletion
`serverTransferProhibited`	The registry blocks transfers
`clientHold` / `serverHold`	The domain is not published in DNS, so it does not resolve
`redemptionPeriod`	The domain has been deleted but can still be restored by the registrant, at a fee
`pendingDelete`	The domain is about to be released and can no longer be restored

Several Prohibited codes together are normal for an active domain. A Hold code explains why a registered domain resolves to nothing.

How to contact a domain owner when details are redacted

The registrar’s contact form or relay address. Many records list an anonymised email address or a link to a web form in the registrant email field. The registrar forwards the message without revealing the address.
The site’s own contact page. If the domain serves a website, its contact page or legal notice is often the shortest route.
Abuse contacts, for abuse reports. Registrars accredited by ICANN publish an abuse email address, and it usually appears in the record. For content hosted on a server, the hosting network’s abuse contact is in the record for its IP address, which whois 192.0.2.10 returns from the regional internet registry.
A formal disclosure request. Registrars disclose redacted data to parties with a legitimate interest, such as a rights holder or law enforcement, through their own process.

What a WHOIS lookup does not tell you

Who runs the site. The registrant may be an agency, a reseller or an employee who left years ago. The site itself, its certificate and the domains it links to say more about who operates it. The Web Graph Explorer for example.com shows the domains a site links to and from, and the guide to checking an SSL certificate shows where certificates are logged.
Who is behind a privacy or proxy service. The registrant shown is the service; only the service knows its customer.
Whether the data is accurate. Registrant details are supplied by the registrant and only partly verified.
Anything for some country-code domains. Not every ccTLD offers RDAP. For those, the domain report shows nothing, and whois or the registry’s own lookup page may still answer.
Who owned it before. A lookup shows the current record, not its history.

The guides index collects the other checks you can run on a domain.

How to find out who owns a domain: WHOIS and RDAP lookups