MyIP.dogChecking…
Domain WHOIS lookup
Look up domain registration through RDAP. Read the registrar, dates, status, nameservers and privacy notices from the responsible registry.
Checking…
Look up domain registration through RDAP. Read the registrar, dates, status, nameservers and privacy notices from the responsible registry.
Checking…
Checking…
Check public domain registration data through the registry listed by IANA. The registry receives the domain you submit from our server.
One domain per request. Clear removes this result from the page. The report is not a domain availability check.
Ready when you are. No domain has been queried.
Enter a domain such as example.com and select Look up domain. This domain WHOIS lookup requests public registration data through RDAP, using the registry endpoint published in IANA's directory. The domain WHOIS lookup result identifies the queried name, the registry URL and the retrieval time. Registration information can help explain a transfer problem, identify a sponsoring registrar or find published administrative contacts. It does not identify the person currently operating a website with certainty.
The domain WHOIS lookup starts only after you submit a name. Use example fills the input without making a registration query. Clear removes the current input and report from this page. Stop waiting cancels this browser's wait, although a request may already have reached the registry. Copy report exports the domain WHOIS lookup summary currently displayed, including its source and limitations, so you can preserve the context when discussing a problem with your registrar.
Use the exact registration name in the domain WHOIS lookup. For a website at www.example.com, the registered domain is commonly example.com, but the domain WHOIS lookup does not silently remove labels or guess registration boundaries. Names under country-code suffixes may have more than two labels. If a subdomain produces no record, confirm the registration name before trying again. A valid DNS hostname is not necessarily a separate registration object.
Internationalized names are converted to their ASCII representation before the domain WHOIS lookup runs. The domain WHOIS lookup keeps that queried representation visible and shows a Unicode name if the registry supplies one. Check the entire spelling, especially when characters look similar across alphabets. URLs, paths, ports, IP addresses, service-record underscores and private-use hostnames are rejected. For an address rather than a name, use the separate IP WHOIS lookup.
RDAP provides structured registration responses over HTTP. ICANN describes it as providing WHOIS-like information with standardized formats, internationalization and mechanisms for locating authoritative services. Its requirements for generic top-level domain operators do not mean every country-code suffix has identical public coverage. This domain WHOIS lookup uses RDAP rather than opening a traditional port-43 WHOIS connection. ICANN's RDAP overview explains the protocol's role and transition requirements.
Our domain WHOIS lookup first finds the longest matching domain-label suffix in the IANA RDAP directory. That selection points to a registry service; it does not infer a registrar from the website's IP address. The directory is cached for a bounded period using its HTTP freshness information. The actual registration result is requested separately for each submitted lookup. These are different datasets with different timestamps.
For this domain WHOIS lookup, registry-provided registrar links remain visible for your inspection but are not automatically fetched. This matters when a registry returns a limited record and a registrar offers additional public fields. The domain WHOIS lookup summary does not merge unrelated responses or label registrar data as registry data. Follow an appropriate source link if you need that additional record, and compare both the name and retrieval time.
Begin with the outcome and source. A successful domain WHOIS lookup 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.
The registrar name in a domain WHOIS lookup comes from a returned entity explicitly marked as a registrar. Public identifiers may include an IANA registrar identifier. If the registry supplies only a handle or omits the display name, the summary shows that limitation instead of inventing a company name. A registrar, a reseller, a DNS provider and a web host can be different organizations. Their responsibilities should be investigated separately.
The domain WHOIS lookup lists registration events using the action and date returned by the source. Registration, expiration, last changed and database update events describe different things. Multiple event rows are retained rather than collapsed into an unexplained domain-age score. A changed timestamp does not tell you which field changed. A registration date does not establish when the current website began publishing or when its present operator acquired control.
An expiration entry in the domain WHOIS lookup is useful for investigation, but renewal decisions belong in the registrar account. Compare the published event with your billing records, renewal settings and registrar support information. Do not assume that an event guarantees deletion at an exact second, or that a displayed future date confirms a payment you recently attempted. The report is a snapshot of the registry response, not a renewal transaction receipt.
Registry status values in the domain WHOIS lookup 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 in the domain WHOIS lookup describe the names listed in the registration response. They are not measurements of current DNS propagation. Compare them with an explicit NS query in DNS lookup, keeping the resolver and query time visible. If the two sources disagree, investigate the timestamps and recent changes before deciding which system needs an update. The domain WHOIS lookup does not query every authoritative server or resolver.
The domain WHOIS lookup 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.
Expand Public contacts and roles after a domain WHOIS lookup 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.
Nested entities retain their parent path in the domain WHOIS lookup. For example, an abuse role beneath a registrar entity describes a contact associated with that registrar. It is not automatically the registrant's own contact. Public identifiers and entity remarks remain with their corresponding entity so that copied reports preserve this relationship. Flattening every email into an unlabeled list would lose information needed for responsible interpretation.
Declared field redactions in the domain WHOIS lookup 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 domain WHOIS lookup 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.
When the domain WHOIS lookup has no structured redaction entries, that does not mean all contact information is public. Read the registry notices and remarks too. A field might be absent from this service, available only through another authorized process, or described through a notice rather than structured redaction metadata. The interface distinguishes “not provided” from an explicit redaction statement instead of assigning a privacy score from missing data.
A domain WHOIS lookup 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.
An unsupported outcome in the domain WHOIS lookup 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 domain WHOIS lookup. 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 domain WHOIS lookup has a ten-second server deadline, bounded response size and local request quotas. It accepts redirects only between the exact query URLs derived from the selected IANA directory entry. A redirect to another destination is reported as unsupported for this request. These boundaries can make a legitimate provider unavailable through this tool; the outcome explains the limitation rather than substituting a fabricated registration result.
The domain WHOIS lookup 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.
For a transfer issue, run the domain WHOIS lookup with the exact registration name, confirm the registrar and inspect the status values. Compare these with the transfer request in your registrar account. Copy the sourced report if support needs it. Do not publish authorization codes or account screenshots alongside the report. This workflow gathers useful context without assuming the public record has access to private account actions.
For a website outage, use the domain WHOIS lookup to inspect registration context, then test DNS separately. Hostname lookup can show A, AAAA and CNAME evidence, while IP lookup investigates an address. Registration, resolution and network reachability answer different questions. A successful registration query does not establish that the website loads, and a failed website connection does not prove the domain registration has expired.
When documenting a change, save the domain WHOIS lookup report with its retrieval timestamp, then obtain a new report after the expected update. Compare like-for-like sources and fields. This page keeps no searchable history of your queries and does not manufacture historical records from the current response. A copied report reflects what was returned at that moment; the registry may update its information later.
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.
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.
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.
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.