Whois Checker Free Tool

Enter a URL

About Whois Checker

What This Tool Actually Does

This page runs a raw WHOIS query from the server that hosts limitlessreferrals.info. When you type a domain into the form above and press the submit button, the server opens a direct TCP connection to the WHOIS port of the registry that manages that domain's ending, sends a text query, and waits for the reply. The reply comes back as plain text lines. The tool shows you those lines exactly as the remote server returned them, with no reformatting, no highlighting, and no parsed summary.

Your browser only sends the domain name to this site. The actual WHOIS conversation happens between this server and the WHOIS server operated by the domain's registry, such as Verisign for .com and .net, or Nominet for .uk. Many WHOIS servers decide what to return based on the network address of the asker. A query from a residential browser would often produce a different answer than a query from a data center server.

The tool knows how to reach the right registry because it carries a built-in table of 285 domain endings. Each ending in that table maps to one registry WHOIS server. The table dates from around 2017. It covers the classic endings such as .com, .org, .uk, .de, .cn, and .io, and it does not cover hundreds of newer generic top-level domains that appeared after the table was frozen.

This tool does not use RDAP anywhere. No API key is needed. No caching layer stores results for later visitors. Every submission produces a fresh query to a live remote server. If that server is slow, you wait. If that server is down, you see an error. The tool has a 20-second timeout for each network attempt, and it will not invent data when the remote side stays silent.

You can check a name made of one label followed by an ending of two to eight characters of letters and dots, such as example.com or bbc.co.uk. The tool strips the www. prefix if you include it. It refuses inputs without a dot, rejects bare IP addresses that come with a path, and rejects longer multi-label names such as blog.example.com. The rejection is deliberate and comes from a validation pattern that expects exactly one label before the ending.

The output panel shows the domain with its first letter capitalised, then a one-column table titled "WHOIS DATA" where each row holds one raw text line from the remote server. Disclaimers, legal notices, and boilerplate appear inline. Nothing is filtered out. If the remote server sends 60 lines of legal text, you will see 60 lines of legal text.

A shared site-wide throttle applies to every page on this site. The throttle allows roughly fifteen requests within a single second from one visitor address. Exceeding that rate blocks the address for the rest of the day. This WHOIS tool itself has no CAPTCHA and no tool-specific request cap, but the registries on the other end have their own per-IP limits on the WHOIS port, and those limits are entirely outside this site's control.

How to Use This Tool

1. Open the tool page. Find the input box above this article, on the Whois Checker page under the Domains Tools category.
2. Type a domain name. Enter a simple two-label domain such as example.com or bbc.co.uk, with or without the www. prefix.
3. Press the submit button. The button carries a label similar to "Get WHOIS Data", and the form sends your input to the processing page.
4. Wait for the remote reply. The server opens a WHOIS connection with a 20-second timeout, so a slow registry can make the page hang for a while.
5. Read the raw text lines. Each line in the result table is one line of the original WHOIS reply, including disclaimers and legal notices.
6. Use the "Try New URL" link. This link appears below the result table and returns you to the form for another lookup.

What the Live Results Show

The live test run for this rewrite took place on September 4, 2026, and produced three results that expose the tool's behaviour. These three domains were chosen because each one lands on a different kind of WHOIS server and returns a different shape of record.

The first test used example.com. The registry for .com is Verisign, and Verisign's WHOIS server answered with a short record that names whois.iana.org as the WHOIS server for this domain. The tool then performed its automatic second hop and queried IANA's server. IANA returned a very short record that identifies the Internet Assigned Numbers Authority as the organisation responsible for example.com, with a creation date of January 1, 1992. This record is a special case. IANA holds the authoritative registration for example.com because that domain is reserved for documentation purposes under RFC 2606.

The second test used github.io. The registry for .io answered, and its reply named MarkMonitor as the registrar WHOIS server. The second hop went to whois.markmonitor.com. MarkMonitor's reply is a full registrar record with a creation date of March 8, 2013, the registrar name, the registrant organisation as GitHub, Inc., a list of name servers, and a DNSSEC status of unsigned. Email addresses in this record are replaced with "Select Request Email Form" links, which is how MarkMonitor handles contact privacy.

The third test used bbc.co.uk. The .uk registry is Nominet, and Nominet's server answered directly with a record that shows the domain was registered before August 1996, has an expiry date of December 13, 2034, and lists name servers. The same record carries a prominent notice that the .UK WHOIS service will end on February 9, 2027, and will be replaced by RDAP. This notice is a real-world signal that the WHOIS protocol is being retired for this namespace.

The three results demonstrate the second-hop mechanism in action. For example.com, the visible output comes from IANA after a pointer from Verisign. For github.io, the visible output comes from MarkMonitor after the .io registry reply. Only for bbc.co.uk does the registry reply stand alone, because Nominet's reply does not name a separate registrar server.

These results also demonstrate that the output is raw text. The dates appear in the middle of lines with labels, not in a neat table of fields. The registrar name sits inside a longer line. The name servers appear one per line. A human reader can extract meaning from this text, and the tool leaves the text unstructured.

How to Read a Raw WHOIS Record

Reading a raw WHOIS record takes practice, because the format varies from one registry to another. A .com record from Verisign looks different from a .uk record from Nominet, and both look different from a .de record from DENIC. The tool does not normalise these formats. You see whatever the remote server sends.

The labels include "Creation Date", "Registered on", "Expiry Date", or "Registry Expiry Date". The exact label depends on the registry. Verisign uses "Creation Date" and "Registry Expiry Date". Nominet uses "Registered on" and "Expiry date". IANA uses a simpler "created" label. These dates tell you when the domain was first registered and when the current registration term ends.

Status codes appear on lines labelled "Status" or "Domain Status". These codes follow the Extensible Provisioning Protocol (EPP) status vocabulary. The most common status is clientTransferProhibited, which means the registrar has locked the domain against unauthorised transfers. Other statuses include clientDeleteProhibited, serverHold, and clientRenewProhibited. Each status has a specific meaning under the EPP standard, and a domain can carry several statuses at once.

Name server lines usually begin with "Name Server" or "NS". These lines list the DNS servers that answer queries for the domain. A domain with no name servers will not resolve, so this section tells you whether the domain is actually in use. Some records also show DNSSEC information. It can appear as a DNSSEC field whose value reads unsigned. That is the full status. The value can also be a list of DS records.

The registrant section is where you will see the biggest change in recent years. Before the General Data Protection Regulation (GDPR) took effect in May 2018, WHOIS records for most domains showed the registrant's name, address, phone number, and email address in full. After GDPR, registries and registrars began redacting personal data. You will now see lines such as "Registrant Organization" with a company name, but "Registrant State/Province" and "Registrant Country" may be the only location data present. Personal contact fields typically show a placeholder or a redaction notice.

The raw text also includes legal boilerplate. Verisign's replies end with a long disclaimer about the terms of use, the prohibition on using WHOIS data for marketing, and the rate limits that apply to automated queries. Nominet's replies include a notice about the RDAP transition. IANA's short record carries almost no boilerplate at all. The tool passes all of this through unchanged.

The Second Hop and Why It Changes What You See

The automatic second hop is the most important detail to understand about this tool. The flow follows a specific sequence. The tool sends a query to the registry server for the domain's ending. The registry server replies with a record. That record often contains a line labeled WHOIS Server whose value is the hostname of the registrar's own server. This line shows the server name. The line appears in the output. This line is part of the record. This line identifies the server. That line names the registrar's own WHOIS server. When that line exists, the tool reads the server name from it, opens a new WHOIS connection to that server, and sends the same domain query again. If the second reply is non-empty, the tool discards the registry reply and shows you the registrar reply.

Why do registries name another server in their replies? Because the registry holds administrative data about the domain, but the registrar holds the customer relationship data. For a .com domain, Verisign maintains the registry and knows the registrar of record. MarkMonitor, GoDaddy, Namecheap, and hundreds of other registrars hold the registrant's contact details. Verisign's reply typically contains a line pointing to the registrar's WHOIS server, and the registrar's server returns the fuller record.

The second hop changes what you see in several ways. The registrar reply usually contains more lines about the registrant, because the registrar holds the customer data. The registrar reply also contains the registrar's own disclaimer text. The date formats may differ between the registry and the registrar. And in some cases, the registrar reply contains redaction notices that the registry reply does not have, because the registrar is the party that applied the redaction.

The example.com test shows an unusual variant of this mechanism. Verisign's reply for example.com names whois.iana.org as the WHOIS server. The tool follows that pointer and queries IANA. IANA's reply is much shorter than a typical Verisign reply. This is the correct behaviour for a reserved domain, because IANA is the authoritative source for example.com under the RFC 2606 reservation.

The github.io test shows the more common variant. The .io registry reply names MarkMonitor as the registrar. The tool queries MarkMonitor and receives the full registrar record with GitHub, Inc. as the registrant organisation. The registry reply alone would have been shorter and would have lacked the registrant details that MarkMonitor provides.

The second hop is not configurable. You cannot ask the tool to skip it and show only the registry reply. The tool always follows the pointer when one exists and the second reply is non-empty. If the registrar server is down or rate-limited, the tool falls back to showing the registry reply, because the second reply would be empty.

Correcting the Old Description of This Tool

The previous version of this page made several claims that do not match the tool's actual behaviour. The old copy said the tool "queries the appropriate WHOIS or RDAP source". The tool only queries WHOIS over the standard WHOIS port. It never sends an RDAP request. This tool uses a raw TCP text protocol. The two are different in every technical respect.

The old copy also claimed the tool "returns it in a readable format" and presented fields such as who registered it, which registrar, when it was created, when it expires, and name servers as if they were parsed into a structured table. The actual output is a one-column table of raw text lines. The dates and registrar names appear inside those lines, but the tool does not extract them into separate fields. A human reading the output can find the creation date, but the page itself will not show a line that says "Creation Date" next to a value in a clean two-column layout.

The old copy said you could "enter a root domain or a subdomain". The tool rejects subdomains. Entering blog.example.com produces the text "Invalid Input" because the validation expects exactly one label before the ending. The same applies to longer multi-label names. Only names made of one label plus a valid ending, such as example.com and bbc.co.uk, pass the validation.

The old copy did not mention the built-in table of 285 endings. It did not mention the automatic second hop to the registrar server named in the registry reply. It did not mention the example.com quirk where the output comes from IANA after a pointer from Verisign. These three facts explain most of what you will actually see when you run a lookup, and their absence from the old description made the tool look simpler than it is.

The Ending Table and Its Gaps

The tool's ability to find the right registry depends entirely on its built-in table of domain endings. Each ending maps to a registry WHOIS server. The table includes the classic generic top-level domains and many country-code domains. The table includes .com mapped to whois.verisign-grs.com, .org mapped to whois.pir.org, .uk mapped to whois.nic.uk, .io mapped to whois.nic.io, .de mapped to whois.denic.de, and .cn mapped to whois.cnnic.net.cn.

The table dates from around 2017. Hundreds of new generic top-level domains were delegated after that time as part of ICANN's new gTLD program. Endings such as .app, .dev, .xyz, .online, .shop, .site, .store, .tech, and .ai are not in the table. If you submit a domain with one of these endings, the tool returns an error message stating that no appropriate Whois server was found for that domain. That message appears in full. That message is the full response. This message appears as an error. This error indicates a missing server entry for that ending.

This error message is accurate but unhelpful. The domain exists, the registry exists, and the WHOIS server exists. The tool simply does not know about it. The table was frozen before these endings were delegated or before they became popular, and no update mechanism exists to refresh it.

The table also has a structural quirk. The tool matches the last label of the domain against the table. For bbc.co.uk, the last label is uk, which maps to Nominet. The tool does not need to know that co.uk is a second-level domain under .uk. It only needs the final label. This works for most country-code domains where the registry operates a single WHOIS server for the whole namespace.

The gap for new gTLDs is the most practical limitation you will encounter. If you work with modern endings such as .app or .dev, this tool will not help you. You would need an RDAP client or a different WHOIS service that keeps its server table current. The Internet Assigned Numbers Authority maintains a public list of WHOIS servers for all top-level domains, and that list is updated as new registries come online, but this tool does not consult it.

RDAP and the Future of WHOIS

The WHOIS protocol has served the internet since the 1980s, but its replacement is already here. Registration Data Access Protocol, known as RDAP, is the modern standard for querying domain registration data. RDAP uses HTTP and returns JSON, which makes it far easier for software to parse. RDAP also supports authenticated access for gated data, while WHOIS offers no standard authentication mechanism.

ICANN made RDAP mandatory through later amendments to its registry and registrar agreements. The transition has been gradual. Most registries now operate RDAP endpoints alongside their legacy WHOIS servers. Some have announced retirement dates for WHOIS. Nominet, the registry for .uk, has announced that its WHOIS service will end on February 9, 2027, and that RDAP will be the only way to query .uk registration data after that date.

The live test for bbc.co.uk shows this transition in action. Nominet's WHOIS reply includes a notice about the shutdown that is scheduled for February of that year. The notice appears as plain text within the WHOIS record itself, which is a fitting symbol of the protocol's age. A protocol that cannot retire without announcing its own funeral inside its own output is a protocol that has outlived its design assumptions.

This tool does not speak RDAP. It sends WHOIS queries over the standard WHOIS port only. When Nominet stops answering WHOIS queries in that year, this tool will no longer work for .uk domains. The same fate awaits other registries as they follow Nominet's path.

RDAP also solves a problem that WHOIS never handled well. WHOIS responses are free text, and every registry formats its records differently. RDAP responses are structured JSON with standardised field names. A client can reliably extract the creation date, the registrar name, and the name servers from any RDAP response without writing a parser for each registry's quirks. This is why the future belongs to RDAP, even though this tool remains firmly in the WHOIS era.

Limitations

This tool shows you raw text from a remote server and nothing more. It does not parse dates into a structured table. It does not compute the domain's age for display. It does not extract the registrar name into its own field. The code contains logic to extract creation, update, and expiry dates and to compute an age, but the page does not display any of those computed values. You see the raw lines, and you do the reading yourself.

The tool rejects subdomains and long multi-label names. Enter blog.example.com and you get "Invalid Input". This is a deliberate validation choice, but it means the tool cannot check a subdomain's parent domain or any domain with more than two labels. The validation pattern expects one label, a dot, and an ending of two to eight characters of letters and dots. The tool simply sends a bare IPv4 address to LACNIC's server, which is the only IP registry it knows.

The ending table stops at the year that is about a decade ago. Hundreds of newer generic top-level domains are missing, including popular ones such as .app, .dev, .xyz, .online, .shop, .site, .store, .tech, and .ai. These domains produce the "No appropriate Whois server found" error. The table is frozen in the code and cannot be updated without a code change.

Registries impose their own rate limits on the WHOIS port. Verisign, for example, is known to throttle or block automated queries that exceed a modest rate. If the registry or registrar server decides your query is part of an automated sweep, you may receive an empty reply or a "Socket Error" message. The tool has no way to bypass these limits, and it should not try to bypass them. The 20-second timeout means a slow registry will make you wait, and a silent registry will eventually produce an error.

Privacy redaction is a hard limit that no WHOIS tool can overcome. Since the GDPR took effect in May 2018, most registries and registrars have stopped publishing personal data in WHOIS records. Registrant names, addresses, phone numbers, and email addresses are usually redacted. A WHOIS lookup will show the registrar's name and the registrant's organisation if one is public, but the individual behind a private domain registration stays hidden. This tool cannot reveal redacted data, and no legitimate tool can.

The tool does not support IPv6 WHOIS. It only handles the legacy IPv4-based WHOIS protocol. It also does not handle domains whose registries have moved to RDAP-only operation. The Nominet shutdown in February of that year is the clearest example, but some registries have already stopped answering WHOIS queries. When a registry stops answering, this tool stops working for that namespace.

Output length is another practical annoyance. Some WHOIS replies, particularly from Verisign, include dozens of lines of legal disclaimer text. The tool shows every line. A single lookup can produce a result table with dozens of rows, most of them boilerplate. You will scroll past the legal text to find the data you need.

When This Tool Is Useful

Despite its limitations, this tool serves a real purpose for quick manual checks. If you need to know the registrar for a .com domain, the raw record will show it. If you want to confirm that a .uk domain is registered and when it expires, Nominet's reply will tell you. If you are curious about the special status of example.com, the IANA record is a small piece of internet history.

The tool is also useful for learning the WHOIS protocol itself. Because the output is raw text, you see exactly what a WHOIS query returns. You can compare the format from Verisign with the format from Nominet and see how different registries structure their replies. This is educational in a way that a parsed, pretty-printed WHOIS tool is not.

For automated or repeated lookups, this tool is the wrong choice. The shared site-wide throttle limits you to about fifteen requests per second from one address, and exceeding that blocks you for the day. The registries have their own limits that are often stricter. If you need to check hundreds of domains, you should use a proper WHOIS client library or an RDAP-based service with a commercial API.

The tool is also useful for understanding the registrar second hop. Many people do not realise that a WHOIS query for a .com domain can involve two servers. This tool makes that mechanism visible, because the output you see comes from whichever server answered last. When the output looks different from what you expected, the second hop is usually the reason.

Related Tools

When you need to know how long a domain has been registered and you want a computed age rather than raw date lines, use the Domain Age Checker, which parses the dates for you.

When you want to see whether a domain resolves and which name servers answer, use the DNS Checker, which queries DNS records across multiple locations.

When you need the IP address behind a domain and the hosting provider associated with that address, use the Domain into IP Converter, which performs the DNS resolution step.

Frequently Asked Questions

Why does the output look different from other WHOIS tools?

This tool shows the raw text reply from the remote WHOIS server, with no parsing or reformatting. Many other WHOIS services run the reply through a parser and display fields in a clean layout. This tool deliberately skips that step, so you see the exact lines returned over the WHOIS protocol, including disclaimers and legal notices.

Why does the WHOIS record not show the registrant's name and address?

Since the GDPR took effect in May of that year, most registries and registrars have redacted personal data from public WHOIS records. Registrant names, addresses, phone numbers, and email addresses are usually hidden. The tool can only display what the remote server sends, and the remote server no longer sends those personal details for most domains.

Why do I get an error for domains ending in .app, .dev, or .xyz?

The tool carries a built-in table of domain endings that dates from about a decade ago. Newer generic top-level domains such as .app, .dev, .xyz, .online, and .shop are not in that table. When the tool cannot find the ending in its table, it returns the same error message stating that no appropriate Whois server was found. That message appears in full. That message is the full response. This message is shown to you. The same message appears for any unrecognized ending.

Why does example.com show a record from IANA?

Verisign's registry reply for example.com names whois.iana.org as the WHOIS server for this domain. The tool automatically follows that pointer and sends a second query to IANA. IANA holds the authoritative registration for example.com because the domain is reserved for documentation under the relevant RFC.

Will this tool work for .uk domains after 2027?

Nominet has announced that its .UK WHOIS service will end on February 9 of that year, and will be replaced by RDAP. This tool only speaks WHOIS over the standard WHOIS port, so once Nominet stops answering WHOIS queries, .uk domains will no longer work here. The live test for bbc.co.uk shows Nominet's own notice about this shutdown inside the WHOIS record.

Why does the output include so many lines of legal text?

WHOIS servers attach lengthy disclaimers to their replies, and this tool passes every line through unchanged. Verisign's replies in particular include several paragraphs about acceptable use, rate limits, and data protection. The legal text is part of the raw record, and the tool does not filter it out.