1913:) recommended on 24 June 2013 that WHOIS should be scrapped. It recommends that WHOIS be replaced with a system that keeps information secret from most Internet users, and only discloses information for "permissible purposes". ICANN's list of permissible purposes includes domain-name research, domain-name sale and purchase, regulatory enforcement, personal data protection, legal actions, and abuse mitigation. Although WHOIS has been a key tool of journalists in determining who was disseminating certain information on the Internet, the use of WHOIS by the free press is not included in ICANN's proposed list of permissible purposes.
1508:
1725:
direct marketers, identity thieves or other attackers to loot the directory for personal information about these people. Although ICANN has been exploring changing WHOIS to enable greater privacy, there is a lack of consensus among major stakeholders as to what type of change should be made. Some domain registrars offer private registrations (also known as domain privacy), by which the contact information of the registrar is shown instead of the customer's. With the offer of private registration from many registrars, some of the risk has been mitigated.
1258:
1900:"make it a violation of trademark and copyright law if a person knowingly provided, or caused to be provided, materially false contact information in making, maintaining, or renewing the registration of a domain name used in connection with the violation," where the latter "violation" refers to a prior violation of trademark or copyright law. The act does not make the submission of false WHOIS data illegal in itself, only if used to shield oneself from prosecution for crimes committed using that domain name.
1809:
1744:(GDPR), effective in the European Union 25 May 2018, which places strict regulations on the processing and publication of personally identifiable information. ICANN stated in November 2017 that it would not reprimand "noncompliance with contractual obligations related to the handling of registration data" if registrars provide alternative solutions for compliance with its rules, until the WHOIS requirements are updated to take GDPR into account.
105:
2224:
the users submitting queries via Whois. The protocol is now so fragmented in terms of information flow and output that queries yield inconsistent results under current conditions. To address the needs of today's
Internet, the IETF Cross Registry Internet Service Protocol (CRISP) working group is developing a new protocol, the Internet Registry Information Service (IRIS), to replace Whois.
1648:
RWhois is intended to replace WHOIS, providing an organized hierarchy of referral services where one could connect to any RWhois server, request a look-up and be automatically re-directed to the correct server(s). However, while the technical functionality is in place, adoption of the RWhois standard
301:
and registrar associations, especially as the management of
Internet infrastructure has become more internationalized. As such, performing a WHOIS query on a domain requires knowing the correct, authoritative WHOIS server to use. Tools to do WHOIS domain searches have become common and are offered by
2223:
The
Nicname/Whois protocol has served well, but it remains unchanged since it was first published in the early 1980s, despite great change in the infrastructure and administration of the Internet. There is now more diversity with domain names and IP networks and associated contacts, as well as among
1794:
ICANN requires that every registrant of a domain name be given the opportunity to correct any inaccurate contact data associated with their domain. For this reason, registrars are required to periodically send the holder the contact information on record for verification, but they do not provide any
2264:
CRISP – Cross-Registry
Internet Service Protocol: The CRISP Working Group was tasked with finding a solution to the problems that currently infest the Nicname/Whois protocol. The CRISP Working Group created a list of functional requirements. Proposals meeting these requirements were evaluated. IRIS
1057:
This status code indicates that your registrar has asked the registry to delete the domain. The domain will be held in this status for 30 days. After five calendar days following the end of the redemptionPeriod, the domain is purged from the registry database and becomes available for registration.
1405:
A WHOIS command line client passes a phrase given as an argument directly to the WHOIS server. Various free open source examples can still be found on sites such as sourceforge.net. However, most modern WHOIS tools implement command line flags or options, such as the -h option to access a specific
227:. WHOIS was standardized in the early 1980s to look up domains, people, and other resources related to domain and number registrations. As all registration was done by one organization at that time, one centralized server was used for WHOIS queries. This made looking up such information very easy.
1724:
of those owning or administering a domain name to be made publicly available through the "WHOIS" directories. The registrant's (domain owner's) contact details, such as address and telephone number, are easily accessible to anyone who queries a WHOIS server. However, that policy enables spammers,
869:
Connect to the service host TCP: service port 43 decimal NCP: ICP to socket 43 decimal, establishing two 8-bit connections Send a single "command line", ending with <CRLF>. Receive information in response to the command line. The server closes its connections as soon as the output is
1566:
Some registry operators are wholesalers, meaning that they typically provide domain name services to a large number of retail registrars, who in turn offer them to consumers. For private registration, only the identity of the wholesale registrar may be returned. In this case, the identity of the
261:
20th-century WHOIS servers were highly permissive and would allow wild-card searches. A WHOIS query of a person's last name would yield all individuals with that name. A query with a given keyword returned all registered domains containing that keyword. A query for a given administrative contact
2168:
The CRISP (Cross-Registry
Information Service Protocol) WG will define a standard mechanism that can be used for finding authoritative information associated with a label, a protocol to transport queries and responses for accessing that information, and a first profile (schema & queries) to
1790:
in 2007, the rightful domain holder with privacy-protected registrations may have difficulty regaining the administration of their domain name. Registrants using "private registration" can attempt to protect themselves by using a registrar that places customer data in escrow with a third party.
1208:
The thick model usually ensures consistent data and slightly faster queries, since only one WHOIS server needs to be contacted. If a registrar goes out of business, a thick registry contains all important information (if the registrant entered correct data, and privacy features were not used to
1459:
and
Macintosh computers had no WHOIS clients installed by default, so registrars had to find a way to provide access to WHOIS data for potential customers. Many end-users still rely on such clients, even though command line and graphical clients exist now for most home PC platforms. Microsoft
1026:
This status code indicates that your registrar has asked the registry to restore the domain that was in redemptionPeriod status. Your registry will hold the domain in this status while waiting for your registrar to provide required restoration documentation. If your registrar fails to provide
898:
43. Clients are simple applications that establish a communications channel to the server, transmit a text record with the name of the resource to be queried and await the response in form of a sequence of text records found in the database. This simplicity of the protocol also permits an
1155:
A WHOIS database consists of a set of text records for each resource. These text records consists of various items of information about the resource itself, and any associated information of assignees, registrants, administrative information, such as creation and expiration dates.
553:
In 2013, the IETF acknowledged that IRIS had not been a successful replacement for WHOIS. The primary technical reason for that appeared to be the complexity of IRIS. Further, non-technical reasons were deemed to lie in areas upon which the IETF does not pass judgment. Meanwhile,
1916:
The EWG collected public input on the initial report until 13 September 2013. Its final report was issued on 6 June 2014, without meaningful changes to the recommendations. As of March 2015, ICANN is in the "process of re-inventing WHOIS," working on "ICANN WHOIS Beta."
945:
This grace period is provided after a domain name registration period expires and is extended (renewed) automatically by the registry. If the registrar deletes the domain name during this period, the registry provides a credit to the registrar for the cost of the renewal.
1924:
Ramp-Up Period of 180 days starting with the effectiveness of this amendment. 360 days after this period is defined as the WHOIS Services Sunset Date, after which it is not a requirement for registries and registrars to offer a WHOIS service and instead only an
1068:
This grace period is provided after a domain name registration period is explicitly extended (renewed) by the registrar. If the registrar deletes the domain name during this period, the registry provides a credit to the registrar for the cost of the renewal.
1136:
This grace period is provided after the successful transfer of a domain name from one registrar to another. If the new registrar deletes the domain name during this period, the registry provides a credit to the registrar for the cost of the transfer.
314:
committee was formed to create a new standard for looking up information on domain names and network numbers: Cross
Registry Information Service Protocol (CRISP). Between January 2005 and July 2006, the working name for this proposed new standard was
1114:
This status code prevents the domain from being transferred from your current registrar to another. It is an uncommon status that is usually enacted during legal or other disputes, at your request, or when a redemptionPeriod status is in place.
1771:
In the case of private registrations, ascertaining registration information may be more difficult. If a registrant, who acquired a domain name, wants to verify the registrar has completed the registration process, three steps may be required:
1534:
will return a placeholder pointing to the RIPE WHOIS server. This lets the WHOIS user making the query know that the detailed information resides on the RIPE server. In addition to the RIRs servers, commercial services exist, such as the
1474:
modules available that work with WHOIS servers. Many of them are not current and do not fully function with the current (2005) WHOIS server infrastructure. However, there is still much useful functionality to derive including looking up
1212:
If a WHOIS client did not understand how to deal with this situation, it would display the full information from the registrar. The WHOIS protocol has no standard for determining how to distinguish the thin model from the thick model.
878:
server query is normally a single name specification. i.e. the name of a resource. However, servers accept a query, consisting of only the question mark (?) to return a description of acceptable command line formats. Substitution or
1002:
status code indicates that the domain has been in redemptionPeriod status for 30 days and not restored. The domain will remain in this status for several days, after which time the domain will be dropped from the registry database.
1728:
Studies have shown that spammers can and do harvest plain-text email addresses from WHOIS servers. For this reason, some WHOIS servers and websites offering WHOIS queries have implemented rate-limiting systems, such as web-based
293:
support so that the same program could operate a web-based WHOIS lookup, and an external TLD table to support multiple WHOIS servers based on the TLD of the request. This eventually became the model of the modern WHOIS client.
1209:
obscure the data) and registration information can be retained. But with a thin registry, the contact information might not be available, and it could be difficult for the rightful registrant to retain control of the domain.
1747:
The WHOIS protocol was not written with an international audience in mind. A WHOIS server and/or client cannot determine the text encoding in effect for the query or the database content. Many servers were originally using
1103:
This status code indicates the domain's
Registry Operator will not allow your registrar to renew the domain. It is an uncommon status that is usually enacted during legal disputes or when the domain is subject to deletion.
934:
This grace period is provided after the initial registration of a domain name. If the registrar deletes the domain name during this period, the registry may provide credit to the registrar for the cost of the registration.
1626:, hierarchical fashion, potentially creating a system with a tree-like architecture. Queries are deterministically routed to servers based on hierarchical labels, reducing a query to the primary repository of information.
2556:
Current gTLD registry agreements vary between thin and thick Whois outputs: com, net and jobs are thin; all other gTLD agreements – aero, asia, biz, cat, coop, info, mobi, museum, name, org, pro, tel, travel – are
1125:
This status code locks the domain preventing it from being updated. It is an uncommon status that is usually enacted during legal disputes, at your request, or when a redemptionPeriod status is in place.
566:. The charter (drafted in February 2012) provided for separate specifications, for number registries first and for name registries to follow. The working group produced five proposed standard documents:
64:, but it is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format. The current iteration of the WHOIS protocol was drafted by the
1752:
and
Internationalization concerns were not taken into consideration until much later. This might impact the usability or usefulness of the WHOIS protocol in countries outside the USA. In the case of
1563:
Normally the contact information of the resources assignee is returned. However, some registrars offer private registration, in which case the contact information of the registrar is shown instead.
2380:
1079:
This status code prevents the domain from being deleted. It is an uncommon status that is usually enacted during legal disputes, at your request, or when a redemptionPeriod status is in place.
316:
1449:. Most early web-based WHOIS clients were merely front-ends to a command-line client, where the resulting output just gets displayed on a web page with little, if any, clean-up or formatting.
1452:
Currently, web based WHOIS clients usually perform the WHOIS queries directly and then format the results for display. Many such clients are proprietary, authored by domain name registrars.
297:
By 2005, there were many more generic top-level domains than there had been in the early 1980s. There are also many more country-code top-level domains. This has led to a complex network of
1555:(defined in RFC 2782) to allow clients to discover the address of the WHOIS server. Some WHOIS lookups require searching the procuring domain registrar to display domain owner details.
1190:
A Thick WHOIS server stores the complete WHOIS information from all the registrars for the particular set of data (so that one WHOIS server can respond with WHOIS information on all
2967:
234:
of the United States government (created during 1958.). The responsibility of domain registration remained with DARPA as the ARPANET became the
Internet during the 1980s.
1200:
A Thin WHOIS server stores only the name of the WHOIS server of the registrar of a domain, which in turn has the full details on the data being looked up (such as the
1929:
service is required. All voting thresholds were met within the 60 day voting period and the amendment was approved by the ICANN Board. The date for WHOIS Sunset for
2827:
2579:
238:
began offering domain registration service; however, they simply handled the paperwork which they forwarded to the DARPA Network Information Center (NIC). Then the
2914:
3162:
2990:
2879:
1547:
There is currently no widely extended way for determining the responsible WHOIS server for a DNS domain, though a number of methods are in common use for
289:. At the time, these TLDs were converted to a thin WHOIS model. Existing WHOIS clients stopped working at that time. A month later, it had self-detecting
286:
1756:
it is the responsibility of the client application to perform the translation of the domain name between its native language script and the DNS name in
212:
Network Information Center (NIC) which acted as a directory that could retrieve relevant information about people or entities. She and the team created
3137:
2959:
1027:
documentation to the registry operator within a set time period to confirm the restoration request, the domain will revert to redemptionPeriod status.
2372:
3220:
1686:
The referral features of RWhois are different than the feature of a WHOIS server to refer responses to another server, which RWhois also implements.
2237:
2540:
2474:
956:
This status code indicates that delegation information (name servers) has not been associated with the domain. The domain is not activated in the
1786:
This provides some confidence that the retailer actually registered the name. But if the registrar goes out of business, as with the failure of
2853:
1819:
1455:
The need for web-based clients came from the fact that command-line WHOIS clients largely existed only in the Unix and large computing worlds.
2342:
2308:
1437:
monopoly, looking up WHOIS information via the web has become quite common. At present, popular web-based WHOIS-queries may be conducted from
3306:"2023 Global Amendments to the Base gTLD Registry Agreement (RA), Specification 13, and 2013 Registrar Accreditation Agreement (RAA) - ICANN"
3313:
1236:, operate a thin WHOIS, requiring domain registrars to maintain their own customers' data. The other global top-level registries, including
1882:
to track down the holders of domain names. As a result, law enforcement agencies have sought to make WHOIS records both open and verified:
2210:
2035:
2731:
231:
2937:
2680:
1920:
On January 19, 2023, ICANN opened voting on a global amendment to all its registry and registrar agreements. In it they defined an
230:
At the time of the emergence of the internet from the ARPANET, the only organization that handled all domain registrations was the
2503:
2655:
31:
3210:"Final Report from the Expert Working Group on gTLD Directory Services: A Next-Generation Registration Directory Service (RDS)"
3108:
3090:
2125:
1768:
In cases where the registrant's (Domain Owner) identity is public, anyone can easily confirm the status of a domain via WHOIS.
1037:
This status code indicates that a request to transfer the domain to a new registrar has been received and is being processed.
1985:
2410:
3187:
3127:"Initial Report from the Expert Working Group on gTLD Directory Services: A Next Generation Registration Directory Service"
2706:
1694:
One criticism of WHOIS is the lack of full access to the data. Few parties have realtime access to the complete databases.
2823:
2569:
2147:
3015:
3068:
1741:
855:
3283:
3045:
2906:
3349:
3166:
1995:
1926:
1921:
1849:
1570:
Below is an example of WHOIS data returned for an individual resource holder. This is the result of a WHOIS query of
548:
188:
30:
This article is about the method for checking information about ownership of a domain name. For the IRC command, see
3253:
2987:
169:
3385:
3038:"Accuracy of "WHOIS" Internet Database Essential to Law Enforcement, FTC Tells Congress - Federal Trade Commission"
1330:
216:, with Feinler's suggestion that domains be divided into categories based on the physical address of the computer.
141:
784:
739:
699:
659:
619:
579:
500:
452:
412:
372:
332:
311:
2875:
998:. In such case, depending on the status set in the domain name, otherwise (not combined with other status), the
1753:
1630:
126:
1421:
to its destination server. The WHOIS protocol manages the transmission of the query and reception of results.
1005:
Once deletion occurs, the domain is available for re-registration in accordance with the registry's policies.
2329:
The Cross Registry Information Service Protocol (crisp) working group in the Applications Area has concluded.
2277:
1653:
891:
491:
As of March 2009, the CRISP IETF Working Group concluded, after a final RFC 5144 was published by the group
262:
returned all domains the administrator was associated with. Since the advent of the commercialized Internet,
148:
3126:
2525:
2265:
was selected as the protocol to publish as a standard. Now an IETF Proposed Standard: RFCs: 3981, 3982, 3983
1539:
used by some large networks (e.g., large Internet providers that acquired other ISPs in several RIR areas).
242:
directed that commercial, third-party entities would handle the management of Internet domain registration.
2376:
1862:
WHOIS has generated policy issues in the United States federal government. As noted above, WHOIS creates a
1476:
536:
61:
3209:
911:
In 2014, June ICANN published the recommendation for status codes, the "Extensible Provisioning Protocol (
408:
Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
3410:
3405:
1282:
1047:
This status code indicates that a request to update the domain has been received and is being processed.
980:
This status code indicates that a request to create the domain has been received and is being processed.
239:
208:) were responsible for creating the first WHOIS directory in the early 1970s. Feinler set up a server in
2248:
1622:) is an extension of the original WHOIS protocol and service. RWhois extends the concepts of WHOIS in a
1016:
This status code indicates that a request to renew the domain has been received and is being processed.
2466:
1975:
1701:
as a criticism, although this problem is strongly mitigated by domain privacy services. Currently, the
1634:
1516:
1399:
1351:
155:
2608:
1390:
operating systems (i.e. Solaris, Linux etc.). WHOIS client and server software is distributed as free
1520:
496:
A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)
2849:
1398:
systems. Various commercial Unix implementations may use a proprietary implementation (for example,
2350:
2316:
1930:
1887:
1496:
290:
137:
3305:
1980:
1874:. However, WHOIS is an important tool for law enforcement officers investigating violations like
1642:
1536:
1414:
859:
115:
41:
1893:
Congressional hearings have been conducted about the importance of WHOIS in 2001, 2002 and 2006.
1406:
server host, but default servers are preconfigured. Additional options may allow control of the
970:
This is the standard status for a domain, meaning it has no pending operations or prohibitions.
1795:
guarantee about the accuracy of information if the registrant provided inaccurate information.
1379:
1149:
539:'s (NRO) Team of the same name "Consolidated RIR IANA Stewardship Proposal Team" (CRISP Team).
122:
2182:
2092:
1410:
to connect on, displaying additional debugging data, or changing recursion/referral behavior.
1089:
This status code is set by the domain's Registry Operator. The domain is not activated in the
3339:
1488:
1204:
WHOIS servers, which refer the WHOIS query to the registrar where the domain was registered).
298:
83:
systems used to make WHOIS protocol queries. In addition, WHOIS has a sister protocol called
17:
2031:
1461:
3008:"FTC Calls for Openness, Accessibility in Whois Database System - Federal Trade Commission"
2806:
2772:
2449:
1990:
1970:
1909:
The Expert Working Group (EWG) of the Internet Corporation for Assigned Names and Numbers (
1492:
1391:
1217:
798:
753:
713:
673:
633:
593:
514:
466:
426:
386:
346:
258:. The General Atomics contract was canceled after several years due to performance issues.
201:
3112:
3094:
2934:
2727:
1242:, operate a thick model. Each country-code top-level registry has its own national rules.
8:
3380:
2629:
1713:
1507:
1335:
209:
2676:
368:
IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)
2647:
2499:
2202:
1318:
213:
3345:
1875:
1672:
1638:
1456:
1434:
848:
263:
247:
2117:
2796:
2762:
2439:
2206:
2194:
2148:"CRISP (Cross-Registry Information Service Protocol) Working Group Meeting Minutes"
1676:
1664:
1641:
run RWhois or WHOIS servers, although RWhois is intended to be run by even smaller
1548:
1342:
1298:
1221:
840:
832:
788:
743:
703:
663:
623:
583:
504:
456:
416:
376:
336:
270:
220:
162:
69:
65:
1257:
899:
application, and a command line interface user, to query a WHOIS server using the
2994:
2941:
2402:
1526:
The records of each of these registries are cross-referenced, so that a query to
1418:
826:
251:
2809:
2790:
2775:
2756:
2702:
1957:
1776:
Perform a WHOIS and confirm that the resource is at least registered with ICANN,
1680:
1668:
1159:
Two data models exist for storing resource information in a WHOIS database, the
801:
778:
756:
733:
716:
693:
676:
653:
636:
613:
596:
573:
517:
494:
469:
446:
429:
406:
389:
366:
349:
326:
73:
2452:
2433:
1950:
1943:
1827:
1721:
1698:
1430:
1323:
844:
836:
224:
3007:
2789:
Williamson, S.; Kosters, M.; Blacka, D.; Singh, J.; Zeilstra, K. (June 1997).
2309:"WG Action: Conclusion of Cross Registry Information Service Protocol (crisp)"
2155:
887:(period) to the query name returns all entries beginning with the query name.
847:
in 1982 by Ken Harrenstien and Vic White of the Network Information Center at
3399:
2247:. Internet Corporation for Assigned Names and Numbers (ICANN). Archived from
1890:
has testified about how inaccurate WHOIS records thwart their investigations.
3195:
3076:
3037:
890:
On the modern Internet, WHOIS services are typically communicated using the
3275:
1717:
3163:"ICANN earmarks domains record WhoIs for the scrapheap - New Legal Review"
2935:"SAC 023: Is the WHOIS Service a Source for email Addresses for Spammers?"
2403:"Web Extensible Internet Registration Data Service (weirds) Working Group"
266:
and unethical spammers, such permissive searching is no longer available.
3245:
1867:
1787:
1657:
1623:
1571:
1407:
1347:
895:
53:
2198:
448:
XML Pipelining with Chunks for the Internet Registry Information Service
2183:"Replacing the Whois Protocol: IRIS and the IETF's CRISP Working Group"
1831:
1734:
1552:
1265:
129: in this section. Unsourced material may be challenged and removed.
57:
2467:"EPP Status Codes - What Do They Mean, and Why Should I Know? - ICANN"
2169:
support commonly-required queries for domain registration information.
2801:
2767:
2444:
1871:
1395:
1387:
1378:
The first applications written for the WHOIS information system were
1307:
884:
793:
748:
708:
668:
628:
588:
509:
461:
421:
381:
341:
2960:"ICANN makes last minute WHOIS changes to address GDPR requirements"
2118:"Whois Domain Lookup UK » Check detailed info for free | IONOS"
1645:, to provide more granular information about IP address assignment.
1417:
applications, a WHOIS client takes the user input and then opens an
1175:
WHOIS information can be stored and looked up according to either a
328:
IRIS: The Internet Registry Information Service (IRIS) Core Protocol
104:
1879:
1782:
Contact the wholesaler and obtain the name of the retail registrar.
1757:
1363:
1270:
559:
243:
49:
45:
2285:
1629:
Lookups of IP address allocations are often limited to the larger
862:
suite was standardized across the ARPANET and later the Internet.
777:
Zhou, L.; Kong, N.; Shen, S.; Sheng, S.; Servin, A. (March 2015).
615:
Security Services for the Registration Data Access Protocol (RDAP)
485:
52:
resource's registered users or assignees. These resources include
1863:
1730:
1311:
255:
205:
2236:
Sanz, Marcos; Newton, Andrew; Daigle, Leslie (12 January 2005).
1499:(PIR) maintains the .ORG registry and associated WHOIS service.
319:(IRIS) The initial IETF Proposed Standards RFCs for IRIS are:
3341:
Broad Band: The Untold Story of the Women Who Made the Internet
2574:
900:
695:
JSON Responses for the Registration Data Access Protocol (RDAP)
2373:"Consolidated RIR IANA Stewardship Proposal Team (CRISP Team)"
1633:(CIDR) blocks (e.g., /24, /22, /16), because usually only the
865:
The protocol specification is the following (original quote):
535:: The IETF CRISP working group is not to be confused with the
246:
was formed in 1993 under contract with the NSF, consisting of
3365:
2945:
2536:
1910:
1818:
deal primarily with the United States and do not represent a
1749:
1706:
1446:
1152:
application, but now many alternative web-based tools exist.
235:
2788:
2703:"A DNS RR for specifying the location of services (DNS SRV)"
484:
The status of RFCs this group worked on can be found on the
40:(pronounced as the phrase "who is") is a query and response
3072:
2600:
2238:"The Internet Registry Information Service (IRIS) Protocol"
1710:
1531:
1527:
1471:
1467:
1442:
1438:
1383:
1303:
1238:
1232:
1226:
1201:
1191:
563:
555:
80:
79:
Whois is also the name of the command-line utility on most
1567:
individual as well as the retail registrar may be hidden.
839:(1977). The NICNAME/WHOIS protocol was first described in
735:
Finding the Authoritative Registration Data (RDAP) Service
575:
HTTP Usage in the Registration Data Access Protocol (RDAP)
572:
Newton, Andrew; Ellacott, Byron; Kong, Ning (March 2015).
3370:
1588:% for more information on IANA, visit http://www.iana.org
1273:(original BSD client), Marco d'Itri (modern Linux client)
957:
204:
and her team (who had created the Resource Directory for
3390:
3375:
1216:
Specific details of which records are stored vary among
3371:
The Internet Corporation for Assigned Names and Numbers
2948:
Security and Stability Advisory Committee, October 2007
2928:
2570:"reactos/whois.c at master · reactos/reactos · GitHub"
2728:"Getting WHOIS Server Address Directly from Registry"
2032:"Whois(1) — whois — Debian stretch — Debian Manpages"
1652:
RWhois services are typically communicated using the
655:
Registration Data Access Protocol (RDAP) Query Format
1656:(TCP). Servers listen to requests on the well-known
894:(TCP). Servers listen to requests on the well-known
780:
Inventory and Analysis of WHOIS Registration Objects
2073:
2061:
2049:
1703:
Internet Corporation for Assigned Names and Numbers
2701:Gulbrandsen, Arnt; Esibov, Levon (February 2000).
2154:. Minneapolis, Minnesota USA: IETF. Archived from
1904:
1779:Determine the name of the wholesale registrar, and
1675:, but the specification was superseded in 1997 by
1148:WHOIS lookups were traditionally performed with a
571:
2826:. Internet Governance Project. 12 February 2011.
2754:
2700:
2677:"DNS and WHOIS - How it Works | ICANN WHOIS"
1597:organisation: Internet Assigned Numbers Authority
821:The WHOIS protocol had its origin in the ARPANET
776:
232:Defense Advanced Research Projects Agency (DARPA)
32:List of Internet Relay Chat commands § WHOIS
3397:
2431:
2235:
692:Newton, Andrew; Hollenbeck, Scott (March 2015).
691:
652:Newton, Andrew; Hollenbeck, Scott (March 2015).
651:
2494:
2492:
1733:and limited amounts of search queries per user
1519:(RIR) can be queried directly to determine the
1502:
1394:and binary distributions are included with all
219:The process of registration was established in
2876:"The Privacy Conundrum in Domain Registration"
2306:
1960:– WHOIS protocol specification (2004, current)
611:
493:Newton, Andrew; Sanz, Marcos (February 2008).
2755:Williamson, S.; Kosters, M. (November 1994).
1816:The examples and perspective in this section
2489:
612:Hollenbeck, Scott; Kong, Ning (March 2015).
2957:
2523:
2432:Harrenstien, K.; White, V. (1 March 1982).
3109:"Fraudulent Online Identity Sanctions Act"
3069:"Whois at heart of congressional hearings"
2824:"Battle Begins Over IP Address Whois Data"
2750:
2748:
1834:, or create a new section, as appropriate.
1763:
1256:
492:
404:
364:
324:
2800:
2766:
2443:
2343:"[CRISP] RFC 5144 up and running"
2013:
2011:
1850:Learn how and when to remove this message
1740:The WHOIS requirements conflict with the
1464:that includes a whois client at no cost.
1170:
792:
747:
707:
667:
627:
587:
508:
460:
420:
380:
340:
189:Learn how and when to remove this message
1898:Fraudulent Online Identity Sanctions Act
1506:
854:WHOIS was originally implemented on the
731:
3376:The Internet Assigned Numbers Authority
2782:
2745:
1523:responsible for a particular resource.
1433:and especially the loosening up of the
858:(NCP) but found its major use when the
302:providers such as IONOS and Namecheap.
269:On December 1, 1999, management of the
14:
3398:
3066:
3018:from the original on 27 September 2006
2852:. KerbsonSecurity. 16 September 2013.
2340:
2180:
2145:
2008:
1936:
883:formats also exist, e.g., appending a
444:
3386:ICANN Whois Inaccuracy Complaint Form
3337:
3226:from the original on 24 February 2015
2901:
2899:
2897:
2546:from the original on 18 December 2010
2079:
2067:
2055:
1986:Routing Policy Specification Language
405:Newton, A.; Sanz, M. (January 2005).
365:Newton, A.; Sanz, M. (January 2005).
325:Newton, A.; Sanz, M. (January 2005).
317:Internet Registry Information Service
3048:from the original on 16 October 2006
2907:"WHATIS Going to Happen With WHOIS?"
2526:"Thick vs. Thin Whois for New gTLDs"
1802:
127:adding citations to reliable sources
98:
2341:Mevzek, Patrick (21 January 2009).
1542:
990:This status code may be mixed with
88:
24:
3256:from the original on 19 April 2020
2894:
2856:from the original on 16 March 2015
2383:from the original on 4 August 2022
1742:General Data Protection Regulation
1697:Others cite the competing goal of
542:
25:
3422:
3359:
2882:from the original on 7 March 2023
2830:from the original on 9 April 2015
2282:IETF Tools: CRISP WG Status Pages
1996:Registration Data Access Protocol
1798:
1610:
1487:WHOIS services are mainly run by
1143:
549:Registration Data Access Protocol
305:
3286:from the original on 21 May 2020
3143:from the original on 3 July 2015
2758:Referral Whois Protocol (RWhois)
2634:RIPE Network Coordination Centre
2413:from the original on 9 July 2015
2307:IESG Secretary (26 March 2009).
2213:from the original on 2 June 2015
2146:Murphy, Cathy (2 October 2003).
1953:– NICNAME/WHOIS (1985, obsolete)
1946:– NICNAME/WHOIS (1982, obsolete)
1807:
1558:
906:
562:managed to serve WHOIS data via
103:
3344:. New York: Portfolio/Penguin.
3316:from the original on 2023-04-07
3298:
3268:
3244:
3238:
3208:
3202:
3188:"SJMC: COMMON SENSE JOURNALISM"
3180:
3155:
3119:
3101:
3083:
3060:
3030:
3000:
2981:
2970:from the original on 2018-05-24
2951:
2917:from the original on 2018-04-29
2868:
2850:"WHOIS Privacy Plan Draws Fire"
2842:
2816:
2734:from the original on 2021-07-26
2720:
2709:from the original on 2021-07-23
2694:
2683:from the original on 2021-01-26
2669:
2658:from the original on 2017-10-20
2640:
2622:
2611:from the original on 2012-09-10
2593:
2582:from the original on 2022-02-01
2562:
2517:
2506:from the original on 2008-01-16
2500:".COM and .NET: Thick Or Thin?"
2477:from the original on 2018-03-13
2459:
2425:
2395:
2365:
2334:
2300:
2270:
2229:
2152:Internet Engineering Task Force
2128:from the original on 2022-07-26
2038:from the original on 2021-04-01
1905:ICANN proposal to abolish WHOIS
771:and an informational document:
114:needs additional citations for
2988:"WHOIS Internalization Issues"
2174:
2139:
2110:
2085:
2024:
1754:internationalized domain names
1663:Rwhois was first specified in
1631:Classless Inter-Domain Routing
1591:% This query returned 1 object
1530:for a record which belongs to
13:
1:
3067:Bowman, Lisa (11 July 2001).
2001:
1654:Transmission Control Protocol
892:Transmission Control Protocol
732:Blanchet, Marc (March 2015).
2792:Referral Whois (RWhois) V1.5
2377:Number Resource Organization
2181:Newton, Andrew (July 2006).
2021:, L. Daigle (September 2004)
2019:WHOIS Protocol Specification
1933:was set as 28 January 2025.
1866:issue which is also tied to
1709:) broadly requires that the
1689:
1635:regional Internet registries
1551:(TLDs). Some registries use
1517:regional Internet registries
1511:Regional Internet registries
1503:Regional Internet registries
537:Number Resource Organization
7:
2958:Vaughan-Nichols, Steven J.
2524:Sarah Stoll (30 May 2009).
2347:IETF CRISP WG: Mail Archive
2313:IETF CRISP WG: Mail Archive
1964:
1830:, discuss the issue on the
1245:
816:
240:National Science Foundation
10:
3427:
3331:
2098:(Report). DARPA. July 2016
1976:Regional Internet registry
1515:WHOIS servers operated by
1482:
546:
445:Newton, A. (August 2007).
94:
44:that is used for querying
29:
3338:Evans, Claire L. (2018).
1643:local Internet registries
1594:domain: EXAMPLE.COM
1521:Internet service provider
1479:and registrant contacts.
1358:
1341:
1329:
1317:
1297:
1293:
1281:
1277:
1264:
1255:
27:Computer network protocol
3276:"What's on the Horizon?"
1888:Federal Trade Commission
1600:created: 1992-01-01
1576:
1497:Public Interest Registry
1110:serverTransferProhibited
856:Network Control Protocol
291:Common Gateway Interface
3136:. ICANN. 24 June 2013.
2187:IEEE Internet Computing
1981:Routing Assets Database
1764:Accuracy of information
1537:Routing Assets Database
1429:With the advent of the
915:) domain status codes"
248:Network Solutions, Inc.
68:, and is documented in
3219:. ICANN. 6 June 2014.
2284:. IETF. Archived from
1512:
1424:
1380:command-line interface
1288:5.5.19 / 2023-10-08
1218:domain name registries
1194:domains, for example).
1171:Thin and thick lookups
1150:command line interface
1121:serverUpdateProhibited
1075:serverDeleteProhibited
960:and will not resolve.
872:
299:domain name registrars
3381:XML Whois Server list
1510:
1099:serverRenewProhibited
867:
825:and was based on the
2648:"APNIC Whois search"
2278:"Crisp Status Pages"
1991:Shared Whois Project
1971:Domain name registry
1828:improve this section
1392:open-source software
828:NAME/FINGER Protocol
564:RESTful web services
123:improve this article
2878:. Act Now Domains.
2407:IETF-88 Proceedings
2199:10.1109/MIC.2006.86
2093:Innovation at DARPA
1937:Standards documents
1585:% IANA WHOIS server
1350:(BSD and ReactOS),
1252:
264:multiple registrars
3411:Internet Standards
3406:Internet protocols
3391:Whois status codes
3366:IANA WHOIS Service
3079:on 27 August 2005.
2993:2012-05-14 at the
2940:2010-12-04 at the
1603:source: IANA
1582:whois example.com
1513:
1495:; for example the
1462:Sysinternals Suite
1250:
62:autonomous systems
3115:on July 17, 2012.
3097:on July 17, 2012.
1860:
1859:
1852:
1673:Network Solutions
1639:domain registrars
1549:top-level domains
1457:Microsoft Windows
1435:Network Solutions
1413:Like most TCP/IP
1376:
1375:
1222:top-level domains
1141:
1140:
849:SRI International
271:top-level domains
202:Elizabeth Feinler
199:
198:
191:
173:
16:(Redirected from
3418:
3355:
3325:
3324:
3322:
3321:
3302:
3296:
3295:
3293:
3291:
3272:
3266:
3265:
3263:
3261:
3250:whois.icann.org/
3242:
3236:
3235:
3233:
3231:
3225:
3214:
3206:
3200:
3199:
3194:. Archived from
3184:
3178:
3177:
3175:
3174:
3165:. Archived from
3159:
3153:
3152:
3150:
3148:
3142:
3131:
3123:
3117:
3116:
3111:. Archived from
3105:
3099:
3098:
3093:. Archived from
3087:
3081:
3080:
3075:. Archived from
3064:
3058:
3057:
3055:
3053:
3034:
3028:
3027:
3025:
3023:
3014:. 18 July 2006.
3004:
2998:
2985:
2979:
2978:
2976:
2975:
2955:
2949:
2932:
2926:
2925:
2923:
2922:
2903:
2892:
2891:
2889:
2887:
2872:
2866:
2865:
2863:
2861:
2846:
2840:
2839:
2837:
2835:
2820:
2814:
2813:
2804:
2802:10.17487/RFC2167
2786:
2780:
2779:
2770:
2768:10.17487/RFC1714
2752:
2743:
2742:
2740:
2739:
2724:
2718:
2717:
2715:
2714:
2698:
2692:
2691:
2689:
2688:
2673:
2667:
2666:
2664:
2663:
2644:
2638:
2637:
2626:
2620:
2619:
2617:
2616:
2597:
2591:
2590:
2588:
2587:
2566:
2560:
2559:
2553:
2551:
2545:
2530:
2521:
2515:
2514:
2512:
2511:
2496:
2487:
2486:
2484:
2482:
2463:
2457:
2456:
2447:
2445:10.17487/RFC0812
2429:
2423:
2422:
2420:
2418:
2399:
2393:
2392:
2390:
2388:
2369:
2363:
2362:
2360:
2358:
2349:. Archived from
2338:
2332:
2331:
2326:
2324:
2315:. Archived from
2304:
2298:
2297:
2295:
2293:
2274:
2268:
2267:
2261:
2259:
2253:
2242:
2233:
2227:
2226:
2220:
2218:
2178:
2172:
2171:
2165:
2163:
2143:
2137:
2136:
2134:
2133:
2114:
2108:
2107:
2105:
2103:
2097:
2089:
2083:
2077:
2071:
2065:
2059:
2053:
2047:
2046:
2044:
2043:
2028:
2022:
2015:
1855:
1848:
1844:
1841:
1835:
1811:
1810:
1803:
1604:
1601:
1598:
1595:
1592:
1589:
1586:
1583:
1581:
1543:Server discovery
1372:
1369:
1367:
1365:
1299:Operating system
1260:
1253:
1249:
1241:
1235:
1229:
1092:
1053:redemptionPeriod
992:redemptionPeriod
918:
917:
914:
823:NICNAME protocol
812:
810:
808:
796:
794:10.17487/RFC7485
767:
765:
763:
751:
749:10.17487/RFC7484
727:
725:
723:
711:
709:10.17487/RFC7483
687:
685:
683:
671:
669:10.17487/RFC7482
647:
645:
643:
631:
629:10.17487/RFC7481
607:
605:
603:
591:
589:10.17487/RFC7480
528:
526:
524:
512:
510:10.17487/RFC5144
480:
478:
476:
464:
462:10.17487/RFC4992
440:
438:
436:
424:
422:10.17487/RFC3983
400:
398:
396:
384:
382:10.17487/RFC3982
360:
358:
356:
344:
342:10.17487/RFC3981
285:was assigned to
284:
280:
276:
194:
187:
183:
180:
174:
172:
131:
107:
99:
66:Internet Society
21:
3426:
3425:
3421:
3420:
3419:
3417:
3416:
3415:
3396:
3395:
3362:
3352:
3334:
3329:
3328:
3319:
3317:
3304:
3303:
3299:
3289:
3287:
3280:whois.icann.org
3274:
3273:
3269:
3259:
3257:
3243:
3239:
3229:
3227:
3223:
3217:whois.icann.org
3212:
3207:
3203:
3186:
3185:
3181:
3172:
3170:
3161:
3160:
3156:
3146:
3144:
3140:
3134:whois.icann.org
3129:
3125:
3124:
3120:
3107:
3106:
3102:
3089:
3088:
3084:
3065:
3061:
3051:
3049:
3036:
3035:
3031:
3021:
3019:
3006:
3005:
3001:
2997:, November 2012
2995:Wayback Machine
2986:
2982:
2973:
2971:
2956:
2952:
2942:Wayback Machine
2933:
2929:
2920:
2918:
2905:
2904:
2895:
2885:
2883:
2874:
2873:
2869:
2859:
2857:
2848:
2847:
2843:
2833:
2831:
2822:
2821:
2817:
2787:
2783:
2753:
2746:
2737:
2735:
2726:
2725:
2721:
2712:
2710:
2699:
2695:
2686:
2684:
2675:
2674:
2670:
2661:
2659:
2646:
2645:
2641:
2628:
2627:
2623:
2614:
2612:
2599:
2598:
2594:
2585:
2583:
2568:
2567:
2563:
2549:
2547:
2543:
2528:
2522:
2518:
2509:
2507:
2498:
2497:
2490:
2480:
2478:
2465:
2464:
2460:
2430:
2426:
2416:
2414:
2401:
2400:
2396:
2386:
2384:
2371:
2370:
2366:
2356:
2354:
2339:
2335:
2322:
2320:
2305:
2301:
2291:
2289:
2276:
2275:
2271:
2257:
2255:
2251:
2240:
2234:
2230:
2216:
2214:
2179:
2175:
2161:
2159:
2144:
2140:
2131:
2129:
2116:
2115:
2111:
2101:
2099:
2095:
2091:
2090:
2086:
2078:
2074:
2066:
2062:
2054:
2050:
2041:
2039:
2030:
2029:
2025:
2016:
2009:
2004:
1967:
1939:
1907:
1856:
1845:
1839:
1836:
1825:
1812:
1808:
1801:
1766:
1692:
1649:has been weak.
1613:
1606:
1605:
1602:
1599:
1596:
1593:
1590:
1587:
1584:
1579:
1578:
1561:
1553:DNS SRV records
1545:
1505:
1485:
1427:
1419:Internet socket
1362:
1289:
1248:
1237:
1231:
1225:
1173:
1146:
1090:
1033:pendingTransfer
941:autoRenewPeriod
912:
909:
871:
831:, described in
819:
806:
804:
761:
759:
721:
719:
681:
679:
641:
639:
601:
599:
551:
545:
543:WEIRDS and RDAP
522:
520:
486:IETF Tools site
474:
472:
434:
432:
394:
392:
354:
352:
308:
282:
278:
274:
252:General Atomics
195:
184:
178:
175:
132:
130:
120:
108:
97:
35:
28:
23:
22:
15:
12:
11:
5:
3424:
3414:
3413:
3408:
3394:
3393:
3388:
3383:
3378:
3373:
3368:
3361:
3360:External links
3358:
3357:
3356:
3350:
3333:
3330:
3327:
3326:
3297:
3267:
3237:
3201:
3198:on 2005-01-12.
3179:
3154:
3118:
3100:
3082:
3059:
3044:. 2 May 2002.
3029:
2999:
2980:
2950:
2927:
2913:. 2018-02-02.
2893:
2867:
2841:
2815:
2781:
2744:
2719:
2693:
2668:
2639:
2621:
2605:whois.arin.net
2592:
2561:
2516:
2488:
2458:
2424:
2394:
2364:
2353:on 2 June 2015
2333:
2319:on 2 June 2015
2299:
2288:on 1 June 2015
2269:
2254:on 1 June 2015
2245:gnso.icann.org
2228:
2173:
2158:on 1 June 2015
2138:
2109:
2084:
2082:, p. 120.
2072:
2070:, p. 119.
2060:
2058:, p. 116.
2048:
2023:
2006:
2005:
2003:
2000:
1999:
1998:
1993:
1988:
1983:
1978:
1973:
1966:
1963:
1962:
1961:
1954:
1947:
1938:
1935:
1906:
1903:
1902:
1901:
1894:
1891:
1858:
1857:
1822:of the subject
1820:worldwide view
1815:
1813:
1806:
1800:
1799:Law and policy
1797:
1784:
1783:
1780:
1777:
1765:
1762:
1722:e-mail address
1699:domain privacy
1691:
1688:
1616:Referral Whois
1612:
1611:Referral Whois
1609:
1577:
1560:
1557:
1544:
1541:
1504:
1501:
1484:
1481:
1431:World Wide Web
1426:
1423:
1374:
1373:
1360:
1356:
1355:
1345:
1339:
1338:
1333:
1327:
1326:
1324:Cross-platform
1321:
1315:
1314:
1301:
1295:
1294:
1291:
1290:
1287:
1285:
1283:Stable release
1279:
1278:
1275:
1274:
1268:
1262:
1261:
1247:
1244:
1206:
1205:
1198:
1195:
1188:
1172:
1169:
1145:
1144:Implementation
1142:
1139:
1138:
1134:
1132:transferPeriod
1128:
1127:
1123:
1117:
1116:
1112:
1106:
1105:
1101:
1095:
1094:
1087:
1081:
1080:
1077:
1071:
1070:
1066:
1060:
1059:
1055:
1049:
1048:
1045:
1039:
1038:
1035:
1029:
1028:
1024:
1022:pendingRestore
1018:
1017:
1014:
1008:
1007:
996:pendingRestore
988:
982:
981:
978:
972:
971:
968:
962:
961:
954:
948:
947:
943:
937:
936:
932:
926:
925:
922:
908:
905:
868:
818:
815:
814:
813:
769:
768:
728:
688:
648:
608:
547:Main article:
544:
541:
482:
481:
441:
401:
361:
307:
306:CRISP and IRIS
304:
197:
196:
111:
109:
102:
96:
93:
85:Referral Whois
48:that store an
26:
9:
6:
4:
3:
2:
3423:
3412:
3409:
3407:
3404:
3403:
3401:
3392:
3389:
3387:
3384:
3382:
3379:
3377:
3374:
3372:
3369:
3367:
3364:
3363:
3353:
3351:9780735211759
3347:
3343:
3342:
3336:
3335:
3315:
3311:
3310:www.icann.org
3307:
3301:
3285:
3281:
3277:
3271:
3255:
3251:
3247:
3246:"About WHOIS"
3241:
3222:
3218:
3211:
3205:
3197:
3193:
3189:
3183:
3169:on 2014-01-14
3168:
3164:
3158:
3139:
3135:
3128:
3122:
3114:
3110:
3104:
3096:
3092:
3086:
3078:
3074:
3070:
3063:
3047:
3043:
3039:
3033:
3017:
3013:
3009:
3003:
2996:
2992:
2989:
2984:
2969:
2965:
2961:
2954:
2947:
2943:
2939:
2936:
2931:
2916:
2912:
2908:
2902:
2900:
2898:
2881:
2877:
2871:
2855:
2851:
2845:
2829:
2825:
2819:
2811:
2808:
2803:
2798:
2794:
2793:
2785:
2777:
2774:
2769:
2764:
2760:
2759:
2751:
2749:
2733:
2729:
2723:
2708:
2704:
2697:
2682:
2678:
2672:
2657:
2653:
2649:
2643:
2635:
2631:
2625:
2610:
2606:
2602:
2596:
2581:
2577:
2576:
2571:
2565:
2558:
2542:
2538:
2534:
2527:
2520:
2505:
2501:
2495:
2493:
2476:
2472:
2471:www.icann.org
2468:
2462:
2454:
2451:
2446:
2441:
2437:
2436:
2435:NICNAME/WHOIS
2428:
2412:
2408:
2404:
2398:
2382:
2378:
2374:
2368:
2352:
2348:
2344:
2337:
2330:
2318:
2314:
2310:
2303:
2287:
2283:
2279:
2273:
2266:
2250:
2246:
2239:
2232:
2225:
2212:
2208:
2204:
2200:
2196:
2192:
2188:
2184:
2177:
2170:
2157:
2153:
2149:
2142:
2127:
2123:
2119:
2113:
2094:
2088:
2081:
2076:
2069:
2064:
2057:
2052:
2037:
2033:
2027:
2020:
2014:
2012:
2007:
1997:
1994:
1992:
1989:
1987:
1984:
1982:
1979:
1977:
1974:
1972:
1969:
1968:
1959:
1955:
1952:
1948:
1945:
1941:
1940:
1934:
1932:
1928:
1923:
1918:
1914:
1912:
1899:
1895:
1892:
1889:
1885:
1884:
1883:
1881:
1877:
1873:
1869:
1865:
1854:
1851:
1843:
1833:
1829:
1823:
1821:
1814:
1805:
1804:
1796:
1792:
1789:
1781:
1778:
1775:
1774:
1773:
1769:
1761:
1759:
1755:
1751:
1745:
1743:
1738:
1736:
1732:
1726:
1723:
1719:
1715:
1712:
1708:
1704:
1700:
1695:
1687:
1684:
1682:
1678:
1674:
1670:
1666:
1661:
1659:
1655:
1650:
1646:
1644:
1640:
1636:
1632:
1627:
1625:
1621:
1617:
1608:
1575:
1573:
1568:
1564:
1559:Query example
1556:
1554:
1550:
1540:
1538:
1533:
1529:
1524:
1522:
1518:
1509:
1500:
1498:
1494:
1490:
1480:
1478:
1473:
1469:
1465:
1463:
1460:provides the
1458:
1453:
1450:
1448:
1444:
1440:
1436:
1432:
1422:
1420:
1416:
1415:client–server
1411:
1409:
1403:
1401:
1397:
1393:
1389:
1385:
1381:
1371:
1361:
1357:
1353:
1349:
1346:
1344:
1340:
1337:
1334:
1332:
1328:
1325:
1322:
1320:
1316:
1313:
1309:
1305:
1302:
1300:
1296:
1292:
1286:
1284:
1280:
1276:
1272:
1269:
1267:
1263:
1259:
1254:
1243:
1240:
1234:
1228:
1223:
1219:
1214:
1210:
1203:
1199:
1196:
1193:
1189:
1186:
1185:
1184:
1182:
1178:
1168:
1166:
1162:
1157:
1153:
1151:
1135:
1133:
1130:
1129:
1124:
1122:
1119:
1118:
1113:
1111:
1108:
1107:
1102:
1100:
1097:
1096:
1088:
1086:
1083:
1082:
1078:
1076:
1073:
1072:
1067:
1065:
1062:
1061:
1056:
1054:
1051:
1050:
1046:
1044:
1043:pendingUpdate
1041:
1040:
1036:
1034:
1031:
1030:
1025:
1023:
1020:
1019:
1015:
1013:
1010:
1009:
1006:
1001:
1000:pendingDelete
997:
993:
989:
987:
986:pendingDelete
984:
983:
979:
977:
976:pendingCreate
974:
973:
969:
967:
964:
963:
959:
955:
953:
950:
949:
944:
942:
939:
938:
933:
931:
928:
927:
923:
920:
919:
916:
907:Augmentations
904:
902:
897:
893:
888:
886:
882:
877:
866:
863:
861:
857:
852:
850:
846:
842:
838:
834:
830:
829:
824:
803:
800:
795:
790:
786:
782:
781:
774:
773:
772:
758:
755:
750:
745:
741:
737:
736:
729:
718:
715:
710:
705:
701:
697:
696:
689:
678:
675:
670:
665:
661:
657:
656:
649:
638:
635:
630:
625:
621:
617:
616:
609:
598:
595:
590:
585:
581:
577:
576:
569:
568:
567:
565:
561:
557:
550:
540:
538:
534:
530:
519:
516:
511:
506:
502:
498:
497:
489:
487:
471:
468:
463:
458:
454:
450:
449:
442:
431:
428:
423:
418:
414:
410:
409:
402:
391:
388:
383:
378:
374:
370:
369:
362:
351:
348:
345:. STD 8.
343:
338:
334:
330:
329:
322:
321:
320:
318:
313:
303:
300:
295:
292:
288:
272:
267:
265:
259:
257:
253:
249:
245:
241:
237:
233:
228:
226:
222:
217:
215:
211:
207:
203:
193:
190:
182:
179:February 2017
171:
168:
164:
161:
157:
154:
150:
147:
143:
140: –
139:
135:
134:Find sources:
128:
124:
118:
117:
112:This section
110:
106:
101:
100:
92:
90:
86:
82:
77:
75:
71:
67:
63:
59:
55:
51:
47:
43:
39:
33:
19:
3340:
3318:. Retrieved
3309:
3300:
3288:. Retrieved
3279:
3270:
3258:. Retrieved
3249:
3240:
3228:. Retrieved
3216:
3204:
3196:the original
3191:
3182:
3171:. Retrieved
3167:the original
3157:
3145:. Retrieved
3133:
3121:
3113:the original
3103:
3095:the original
3085:
3077:the original
3062:
3050:. Retrieved
3041:
3032:
3020:. Retrieved
3011:
3002:
2983:
2972:. Retrieved
2963:
2953:
2930:
2919:. Retrieved
2910:
2884:. Retrieved
2870:
2858:. Retrieved
2844:
2832:. Retrieved
2818:
2791:
2784:
2757:
2736:. Retrieved
2722:
2711:. Retrieved
2696:
2685:. Retrieved
2671:
2660:. Retrieved
2652:wq.apnic.net
2651:
2642:
2633:
2630:"Webupdates"
2624:
2613:. Retrieved
2604:
2595:
2584:. Retrieved
2573:
2564:
2555:
2550:17 September
2548:. Retrieved
2532:
2519:
2508:. Retrieved
2479:. Retrieved
2470:
2461:
2434:
2427:
2415:. Retrieved
2406:
2397:
2385:. Retrieved
2367:
2355:. Retrieved
2351:the original
2346:
2336:
2328:
2321:. Retrieved
2317:the original
2312:
2302:
2290:. Retrieved
2286:the original
2281:
2272:
2263:
2256:. Retrieved
2249:the original
2244:
2231:
2222:
2215:. Retrieved
2193:(4): 79–84.
2190:
2186:
2176:
2167:
2160:. Retrieved
2156:the original
2151:
2141:
2130:. Retrieved
2121:
2112:
2100:. Retrieved
2087:
2075:
2063:
2051:
2040:. Retrieved
2026:
2018:
1919:
1915:
1908:
1897:
1861:
1846:
1837:
1817:
1793:
1785:
1770:
1767:
1746:
1739:
1727:
1718:phone number
1702:
1696:
1693:
1685:
1662:
1651:
1647:
1628:
1619:
1615:
1614:
1607:
1569:
1565:
1562:
1546:
1525:
1514:
1486:
1470:has several
1466:
1454:
1451:
1428:
1412:
1404:
1377:
1266:Developer(s)
1224:, including
1215:
1211:
1207:
1183:data model:
1180:
1176:
1174:
1164:
1160:
1158:
1154:
1147:
1131:
1120:
1109:
1098:
1084:
1074:
1063:
1052:
1042:
1032:
1021:
1012:pendingRenew
1011:
1004:
999:
995:
991:
985:
975:
965:
951:
940:
929:
924:Description
921:Status Code
910:
889:
880:
876:command line
875:
873:
864:
853:
827:
822:
820:
805:. Retrieved
779:
770:
760:. Retrieved
734:
720:. Retrieved
694:
680:. Retrieved
654:
640:. Retrieved
614:
600:. Retrieved
574:
552:
532:
531:
521:. Retrieved
495:
490:
483:
473:. Retrieved
447:
433:. Retrieved
407:
393:. Retrieved
367:
353:. Retrieved
327:
310:In 2003, an
309:
296:
268:
260:
229:
218:
200:
185:
176:
166:
159:
152:
145:
133:
121:Please help
116:verification
113:
84:
78:
54:domain names
37:
36:
3192:jour.sc.edu
3052:11 November
3042:www.ftc.gov
3022:11 November
3012:www.ftc.gov
2911:Motherboard
2601:"Whois-RWS"
2122:ionos.co.uk
1868:free speech
1788:RegisterFly
1671:in 1994 by
1658:port number
1637:(RIRs) and
1572:example.com
1408:port number
1348:BSD License
1064:renewPeriod
896:port number
60:blocks and
3400:Categories
3320:2023-04-07
3173:2014-01-13
2974:2018-05-29
2921:2018-04-28
2738:2021-07-26
2713:2021-07-26
2687:2020-12-27
2662:2022-08-04
2615:2012-09-10
2586:2019-07-29
2533:memorandum
2510:2008-01-17
2132:2022-07-27
2080:Evans 2018
2068:Evans 2018
2056:Evans 2018
2042:2020-12-27
2017:RFC 3912,
2002:References
1735:IP address
1493:registries
1489:registrars
1477:AS numbers
1382:tools for
1085:serverHold
903:protocol.
210:Stanford's
149:newspapers
58:IP address
3282:. ICANN.
3252:. ICANN.
2102:August 7,
1956:RFC
1949:RFC
1942:RFC
1872:anonymity
1832:talk page
1690:Criticism
1396:Unix-like
1388:Unix-like
1308:Unix-like
930:addPeriod
885:full-stop
881:wild-card
870:finished.
46:databases
3314:Archived
3290:24 March
3284:Archived
3260:24 March
3254:Archived
3230:24 March
3221:Archived
3147:24 March
3138:Archived
3091:"THOMAS"
3046:Archived
3016:Archived
2991:Archived
2968:Archived
2938:Archived
2915:Archived
2886:26 March
2880:Archived
2854:Archived
2828:Archived
2732:Archived
2707:Archived
2681:Archived
2656:Archived
2609:Archived
2580:Archived
2541:Archived
2504:Archived
2481:14 March
2475:Archived
2411:Archived
2409:. IETF.
2387:4 August
2381:Archived
2211:Archived
2126:Archived
2036:Archived
1965:See also
1880:phishing
1840:May 2018
1826:You may
1758:punycode
1624:scalable
1368:/rfc1036
1319:Platform
1271:RIPE NCC
1246:Software
1163:and the
952:inactive
817:Protocol
560:RIPE NCC
256:AT&T
244:InterNIC
50:Internet
42:protocol
3332:Sources
2860:4 April
2834:4 April
2379:(NRO).
2207:8514005
1864:privacy
1731:CAPTCHA
1714:address
1711:mailing
1483:Servers
1400:Solaris
1359:Website
1354:(Linux)
1343:License
1336:Command
1312:ReactOS
1220:. Some
1167:model.
807:July 8,
775:7485 -
762:July 8,
730:7484 -
722:July 8,
690:7483 -
682:July 8,
650:7482 -
642:July 8,
610:7481 -
602:July 8,
570:7480 -
475:June 1,
443:4992 -
435:June 1,
403:3983 -
395:June 1,
363:3982 -
355:June 1,
323:3981 -
273:(TLDs)
214:domains
206:ARPANET
163:scholar
138:"WHOIS"
95:History
3348:
2575:GitHub
2557:thick.
2417:8 July
2357:2 June
2323:2 June
2292:2 June
2258:1 June
2217:1 June
2205:
2162:1 June
1679:
1667:
1660:4321.
1620:RWhois
1370:/whois
1364:github
901:Telnet
860:TCP/IP
843:
835:
523:1 June
281:, and
223:
165:
158:
151:
144:
136:
89:RWhois
72:
3224:(PDF)
3213:(PDF)
3141:(PDF)
3130:(PDF)
2964:ZDNet
2946:ICANN
2544:(PDF)
2537:ICANN
2529:(PDF)
2252:(PDF)
2241:(PDF)
2203:S2CID
2096:(PDF)
1931:gTLDs
1911:ICANN
1750:ASCII
1707:ICANN
1447:APNIC
1251:whois
1187:Thick
1179:or a
1177:thick
1161:thick
287:ICANN
236:UUNET
170:JSTOR
156:books
38:WHOIS
18:Whois
3346:ISBN
3292:2015
3262:2015
3232:2015
3149:2015
3073:CNET
3054:2006
3024:2006
2888:2013
2862:2015
2836:2015
2810:2167
2776:1714
2552:2011
2483:2018
2419:2015
2389:2022
2359:2015
2325:2015
2294:2015
2260:2015
2219:2015
2164:2015
2104:2021
1958:3912
1927:RDAP
1922:RDAP
1896:The
1886:The
1878:and
1876:spam
1870:and
1720:and
1681:2167
1669:1714
1580:>
1532:RIPE
1528:ARIN
1491:and
1472:Perl
1468:CPAN
1445:and
1443:RIPE
1439:ARIN
1402:7).
1386:and
1384:Unix
1366:.com
1331:Type
1304:Unix
1230:and
1202:.com
1197:Thin
1192:.org
1181:thin
1165:thin
874:The
809:2015
802:7485
785:IETF
764:2015
757:7484
740:IETF
724:2015
717:7483
700:IETF
684:2015
677:7482
660:IETF
644:2015
637:7481
620:IETF
604:2015
597:7480
580:IETF
558:and
556:ARIN
533:Note
525:2015
518:5144
501:IETF
477:2015
470:4992
453:IETF
437:2015
430:3983
413:IETF
397:2015
390:3982
373:IETF
357:2015
350:3981
333:IETF
312:IETF
254:and
142:news
81:UNIX
74:3912
2807:RFC
2797:doi
2773:RFC
2763:doi
2453:812
2450:RFC
2440:doi
2195:doi
1951:954
1944:812
1748:US-
1677:RFC
1665:RFC
1425:Web
1352:GPL
1239:org
1233:net
1227:com
1091:DNS
994:or
958:DNS
913:EPP
845:812
841:RFC
837:742
833:RFC
799:RFC
789:doi
754:RFC
744:doi
714:RFC
704:doi
674:RFC
664:doi
634:RFC
624:doi
594:RFC
584:doi
515:RFC
505:doi
467:RFC
457:doi
427:RFC
417:doi
387:RFC
377:doi
347:RFC
337:doi
283:org
279:net
275:com
225:920
221:RFC
125:by
91:).
70:RFC
3402::
3312:.
3308:.
3278:.
3248:.
3215:.
3190:.
3132:.
3071:.
3040:.
3010:.
2966:.
2962:.
2944:,
2909:.
2896:^
2805:.
2795:.
2771:.
2761:.
2747:^
2730:.
2705:.
2679:.
2654:.
2650:.
2632:.
2607:.
2603:.
2578:.
2572:.
2554:.
2539:.
2535:.
2531:.
2502:.
2491:^
2473:.
2469:.
2448:.
2438:.
2405:.
2375:.
2345:.
2327:.
2311:.
2280:.
2262:.
2243:.
2221:.
2209:.
2201:.
2191:10
2189:.
2185:.
2166:.
2150:.
2124:.
2120:.
2034:.
2010:^
1760:.
1737:.
1716:,
1683:.
1574::
1441:,
1310:,
1306:,
1093:.
966:ok
851:.
797:.
787:.
783:.
752:.
742:.
738:.
712:.
702:.
698:.
672:.
662:.
658:.
632:.
622:.
618:.
592:.
582:.
578:.
529:.
513:.
503:.
499:.
488:.
465:.
455:.
451:.
425:.
415:.
411:.
385:.
375:.
371:.
335:.
331:.
277:,
250:,
76:.
56:,
3354:.
3323:.
3294:.
3264:.
3234:.
3176:.
3151:.
3056:.
3026:.
2977:.
2924:.
2890:.
2864:.
2838:.
2812:.
2799::
2778:.
2765::
2741:.
2716:.
2690:.
2665:.
2636:.
2618:.
2589:.
2513:.
2485:.
2455:.
2442::
2421:.
2391:.
2361:.
2296:.
2197::
2135:.
2106:.
2045:.
1853:)
1847:(
1842:)
1838:(
1824:.
1705:(
1618:(
811:.
791::
766:.
746::
726:.
706::
686:.
666::
646:.
626::
606:.
586::
527:.
507::
479:.
459::
439:.
419::
399:.
379::
359:.
339::
192:)
186:(
181:)
177:(
167:·
160:·
153:·
146:·
119:.
87:(
34:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
