Domain WHOIS
Look up raw WHOIS registration text for a single domain name. The tool normalizes and validates an ASCII domain such as example.com, chooses a WHOIS server from its TLD map, queries port 43, and displays the server response in a copyable textarea.
Domain WHOIS Lookup retrieves the raw WHOIS response for one domain name. Enter a domain such as example.com, submit the form, and the tool validates the input, selects a WHOIS server for the domain's top-level domain, opens a port 43 WHOIS connection, and displays the returned text in a textarea that can be copied.
This is a direct WHOIS text lookup, not a domain availability checker or a parsed ownership report. WHOIS output varies heavily by registry and registrar. Some responses include registrar, creation date, expiration date, status, and nameserver details, while others may be redacted, limited, referral-based, rate-limited, unavailable, or incomplete.
How to use Domain WHOIS Lookup
- Enter a domain in the input field using the visible style shown by the placeholder, such as
example.com. - Use a single registered-domain style value. The current validator expects one label plus a top-level domain, not a subdomain or a full URL path.
- Click the submit button to start the lookup.
- Review any validation or connection message if the lookup cannot run.
- When a WHOIS response is returned, read the raw text in the result textarea.
- Use the copy button beside the result to copy the textarea value for notes, support tickets, or follow-up review.
Each new lookup clears the previous output and error state before the request runs. If the server-side PHP environment does not have fsockopen available, the tool reports that the service is unavailable instead of attempting the network request.
Accepted input
The submitted value is first normalized with the site's URL filtering helper, then checked against a strict domain pattern. The accepted shape is intentionally simple: an ASCII domain label followed by a dot and an alphabetic top-level domain of at least two characters.
| Input area | Verified behavior | Practical note |
|---|---|---|
| Example accepted shape | example.com |
The domain must start and end with a letter or number around the main label. |
| Domain label length | The regex allows a first character, 1 to 61 middle characters, and a final character before the dot. | Hyphens may appear inside the label, but not as the first or last character. |
| TLD format | Alphabetic letters only, at least two characters. | The lookup only continues when the extracted TLD exists in the tool's WHOIS server map. |
| Unsupported examples | Subdomains, underscores, paths, query strings, and values that do not match the single-label pattern. | Use the registrable domain form, such as example.com, rather than www.example.com/page. |
| IDN and punycode handling | No special IDN or punycode handling is exposed in the verified workflow. | Use plain ASCII domains unless you have confirmed how the normalized value will be submitted. |
What the lookup returns
The result is the raw text returned by the selected WHOIS server. The tool does not parse the response into separate fields, merge registry and registrar records, or decide whether a domain is available to buy. It places the full returned text into a textarea with the ID whois and provides a copy button that copies that textarea value.
For some TLDs, a registry WHOIS server may return a compact record with a referral to a registrar WHOIS server. For other TLDs, the response may include registrar, domain status, important dates, nameservers, DNSSEC information, abuse contact details, or policy notices. The exact fields, labels, date formats, language, and redaction behavior depend on the registry or registrar server that answers the query.
How the tool chooses a WHOIS server
On page initialization, the Livewire component builds a large top-level-domain to WHOIS-server map. The map covers many generic TLDs, country-code TLDs, newer gTLDs, sponsored and regional extensions, and some brand TLDs. The settings group tool-domain-whois can override or add server entries through DomainWhoisSettings::$servers.
After validation, the tool extracts the registered domain and top-level domain with the site's domain helpers, trims dots and spaces from the TLD, and checks whether that TLD exists in the server map. If no server is configured for the TLD, the page returns an unsupported-TLD error instead of guessing a server.
Technical method
The verified implementation is a Laravel Livewire tool with public fields for domain, whoisInfo, error, and servers. The lookup method returns early when the service is unavailable, clears previous output, normalizes the domain, validates it, finds the TLD's configured WHOIS server, and then calls the query method.
The query method opens a socket connection with fsockopen($server, 43, $errno, $errstr, 10), sets a 10-second stream timeout, writes the requested domain followed by \r\n, reads until end of file, closes the connection, and returns the collected text. If the connection cannot be opened, the method returns false and the page shows a connection-failed error.
A production sanity test confirmed that example.com could be queried through whois.verisign-grs.com:43 and returned WHOIS text beginning with Domain Name: EXAMPLE.COM. That confirms the core port 43 path for that sample domain, but it does not guarantee that every configured TLD server will be reachable or return the same style of data.
Example lookup
If you enter example.com, the tool normalizes and validates the domain, extracts com as the TLD, selects the mapped .com WHOIS server, and sends the domain over a port 43 WHOIS connection. In the verified production test, the response began with Domain Name: EXAMPLE.COM.
That response should be treated as registry WHOIS text at the time of the request. A different domain, a different TLD, a later request, or a rate-limited server can produce a different response structure. When you need authoritative registration details for a legal, billing, recovery, or security decision, confirm the information with the registrar, registry, or an official RDAP/WHOIS source for that TLD.
Limitations and caveats
WHOIS is not uniform across the internet. Privacy rules, registry policies, registrar practices, anti-abuse controls, and data-protection requirements can all affect what appears in a response. Many modern records redact registrant names, street addresses, email addresses, and phone numbers. This tool cannot unmask private registration data or bypass policy-based redaction.
The current page does not use RDAP, perform a registrar follow-up query, parse fields, check DNS records, show registrar pricing, compare registrars, export a file, run batch lookups, or guarantee that a domain can be registered. It also does not prove freshness or completeness. Some registry servers may return thin data and require a separate registrar WHOIS or RDAP check for deeper details.
Because the request is made from the Digital Domain Kit server, rate limits, firewall rules, WHOIS server outages, network reachability, and TLD-specific query rules may affect results. If a lookup fails, the failure may be caused by the remote WHOIS service or the server-to-server connection rather than by the domain itself.
Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The domain is rejected as invalid | The input does not match the current single-label plus TLD pattern. | Enter only the registrable domain, such as example.com. Remove protocols, paths, spaces, underscores, and subdomains. |
| The TLD is unsupported | The extracted TLD is not present in the configured WHOIS server map. | Check the spelling of the domain and, for uncommon TLDs, confirm the official WHOIS or RDAP service outside this tool. |
| The connection fails | The mapped WHOIS server did not accept or complete the port 43 connection within the configured timeout. | Retry later, compare with the registry's own lookup, or use an RDAP service if the TLD supports it. |
| The output is short or only points elsewhere | The registry may provide thin WHOIS data or refer users to a registrar WHOIS/RDAP service. | Follow the referral information in the response when available and verify details with the registrar. |
| Registrant contact information is missing | The record may be redacted by privacy service, registrar policy, registry policy, or data-protection rules. | Use the listed registrar, abuse contact, contact form, or official dispute process instead of expecting the tool to reveal private data. |
| The service is unavailable | The server environment does not provide fsockopen, which this implementation requires. |
Try again later or report the issue so the site operator can review server configuration. |
Responsible use
Use WHOIS output for legitimate domain research, troubleshooting, compliance review, abuse reporting, registrar confirmation, and ownership due diligence. Do not treat a raw WHOIS response as permission to contact people outside appropriate policy channels, scrape registrant data, or make a final legal conclusion about ownership, trademark rights, or domain transfer status.
For business-critical changes, compare the WHOIS result with your registrar dashboard, registry guidance, DNS records, account email, transfer-lock status, and billing records. WHOIS text can help you spot nameserver changes, status codes, registrar names, or date fields, but it should be one part of a broader domain-management check.
Related tools
- DNS Lookup helps inspect DNS records after you confirm which domain or nameservers you are investigating.
- DNS Propagation Check compares selected DNS records across public resolvers after nameserver or zone changes.
- Domain Generator helps brainstorm names before you verify registration details with WHOIS or a registrar.
- HTTP Status Code Checker can confirm the web response after a domain resolves to a site.
Editorial information
Built and maintained by Digital Domain Kit. Technical behavior for this draft was reviewed on September 14, 2026 against the verified production facts for app/Http/Livewire/Tools/DomainWhois.php, the matching domain-whois Livewire view, the header/selector, and settings group tool-domain-whois.
The verified method is a server-side port 43 WHOIS socket query using the component's configured TLD server map and any server overrides supplied by DomainWhoisSettings::$servers. To report a problem with this tool page, use the site's contact page and include the domain searched, the approximate time, and the error or unexpected output you saw.