Domain WHOIS lookup

Look up domain registration through RDAP. Read the registrar, dates, status, nameservers and privacy notices from the responsible registry.

Public registry data for this exact domain.

Enter the exact domain, without a URL or path. Internationalized names are converted to ASCII. Subdomains are not automatically removed.

Check public domain registration data through the registry listed by IANA. The registry receives the domain you submit from our server.

Example report

Illustrative data. Run a lookup for live results.

Registration record returned

Example report

The selected registry returned a matching domain record. This describes its public registration response at the retrieval time.

Next step: Review the registry source, status and event dates. Confirm availability with the registrar separately; missing RDAP data does not prove a domain can be registered.

example.org

Registrar name

Demo registrar

Registry status values

  • clientTransferProhibited

Registered nameservers

  • ns1.example.org
  • ns2.example.org

Important dates

  1. Registration date
  2. Last changed
  3. Expiration date

Dates come from registry events. Open Registration events for full timestamps.

Registry source

RDAP source

Retrieved at (UTC):

DNSSEC declarations

DS record
Reported false
DNSKEY record
Reported false
Delegation signed
Not provided
Zone signed
Not provided

Record presence from Google Public DNS is separate from the registry’s DNSSEC declarations and is not a security grade.

Public contacts and roles (1)

Fields below are returned by this registry. Nested roles relate to their parent entity; an abuse contact under a registrar is not the registrant. Missing contact details may be omitted, restricted or redacted.

registrar

Registry handle
EXAMPLE-REGISTRAR
Name
Demo registrar
Declared field redactions
  • Registrant contact · Illustrative redaction · removal
Registration events (3)
registration (1)
2020-01-10T00:00:00Z
last changed (2)
2024-03-14T00:00:00Z
expiration (3)
2028-01-10T00:00:00Z
View the structured summary
Example report
Illustrative data. Run a lookup for live results.

{
  "scope": "Public registry RDAP summary; no registrar referral was fetched. Missing fields do not prove privacy protection or domain availability. DNSSEC values are registry declarations, not live validation. Summary does not include every RDAP extension.",
  "name": "example.org",
  "outcome": "found",
  "reason": null,
  "httpStatus": 200,
  "sourceUrl": "https://rdap.publicinterestregistry.org/rdap/domain/example.org",
  "observedAt": "2026-01-15T14:23:00.000Z",
  "directoryPublication": "2026-01-01T00:00:00Z",
  "record": {
    "name": "example.org",
    "unicodeName": null,
    "handle": "EXAMPLE-DOMAIN",
    "status": [
      "clientTransferProhibited"
    ],
    "nameservers": [
      "ns1.example.org",
      "ns2.example.org"
    ],
    "events": [
      {
        "action": "registration",
        "date": "2020-01-10T00:00:00Z",
        "actor": null
      },
      {
        "action": "last changed",
        "date": "2024-03-14T00:00:00Z",
        "actor": null
      },
      {
        "action": "expiration",
        "date": "2028-01-10T00:00:00Z",
        "actor": null
      }
    ],
    "delegationSigned": null,
    "zoneSigned": null,
    "entities": [
      {
        "path": "/entities/0",
        "handle": "EXAMPLE-REGISTRAR",
        "roles": [
          "registrar"
        ],
        "contacts": [
          {
            "field": "fn",
            "value": "Demo registrar"
          }
        ],
        "publicIds": [],
        "remarks": []
      }
    ],
    "notices": [],
    "links": [],
    "redactions": [
      {
        "name": "Registrant contact",
        "reason": "Illustrative redaction",
        "method": "removal"
      }
    ],
    "limited": false
  }
}

One domain per request. Clear removes this result from the page. The report is not a domain availability check.

Follow the authoritative registration source

  1. Exact domain

    Normalize internationalized input to its queried ASCII name.

  2. IANA directory

    Find the matching suffix and its registry endpoint.

  3. RDAP response

    Validate the returned domain object and bound its fields.

  4. Sourced registration

    Read registrar, events, statuses, contacts and redactions separately.

RDAP events and DNSSEC declarations are registry data, not live DNS or website security tests.
On this page

Learn more about Domain WHOIS lookup

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.

Domain WHOIS lookup questions

Can a domain WHOIS lookup discover the hidden owner?

No. The domain WHOIS lookup displays public registry information and any explicit redaction explanation. It does not establish a person's identity from an IP, expose private registration fields or authenticate ownership claims. If you have a legitimate administrative or abuse concern, use the appropriate published contact or the registry's authorized process.

Does a domain WHOIS lookup query my own IP address?

The domain WHOIS lookup sends the submitted domain from our server to the chosen registry. The registry sees that server connection; the tool does not attach your browser IP to the RDAP query. Our site receives your request, and external source links open the provider directly if you select them. Avoid submitting confidential internal names.

Why can a domain WHOIS lookup have no result for a registered name?

A domain WHOIS lookup may lack coverage, encounter an access policy, reach a timeout or receive an unsupported redirect. Those outcomes are shown separately from an RDAP 404. Check the exact name and source before drawing a conclusion. A functional website is also not proof that every registration service must answer every client.

Is a domain WHOIS lookup report a full WHOIS archive?

No. The domain WHOIS lookup produces a current public RDAP summary from one registry request. It does not combine registrar referrals, historical ownership datasets or DNS history. Read Data Sources and Methodology for the site's broader evidence boundaries, and use the registry link when you need its complete response.

Data Sources

Methodology

Does the tool remove www before querying registration?

No. The documented behavior queries the supplied name rather than guessing a registrable parent. If a subdomain has no RDAP record, investigate the intended registration name before concluding that the whole domain is unregistered.

Does a registration record prove that DNS resolves?

No. Registration and DNS are separate layers. A registered name can have missing or changed DNS records, and a DNS answer does not verify the registrant. Use the record tool to inspect the exact name and type you need.

Does no returned record guarantee a domain is available to buy?

No. An unavailable source, unsupported registry behavior or a query for the wrong name can produce no usable record. Availability requires a suitable current registration check, not an assumption drawn from one failed retrieval.

Should I treat every event timestamp as the creation date?

No. RDAP can report different kinds of events, such as registration or updates. Read the associated event action and preserve the source. A later update does not necessarily mean the website or its current operator began on that date.