ICANN’s Generic Names Supporting Organization (GNSO) works to address these and other gTLD WHOIS data and access issues by recommending changes to related policies.

For example, the GNSO often engages in activities to evaluate and document the importance of WHOIS to stakeholders. In 2006, a GNSO task force re-examined the purpose of WHOIS, detailing intended and actual uses of registrant contact information. Based on that work, ICANN approved recommendations to improve WHOIS usage notification and consent. At the same time, the RAA (the agreement ICANN has with its accredited registrars) was amended to require registrars to restrict bulk access to WHOIS data for marketing.

The GNSO also takes steps to make recommendations to improve WHOIS accuracy. For example, a GNSO policy recommendation was adopted by the ICANN Board to require registrars to provide each registrant at least annually with an opportunity to review and correct their domain name’s WHOIS data, accompanied by a reminder that false data can be grounds for registration cancellation. In addition, registrants that submit false data or fail to respond to registrar inquiries were given a grace period during which the domain name is temporarily held by the registrar until the registrant provides updated WHOIS data. Contractual compliance efforts to improve WHOIS data accuracy and accessibility are also underway, based in part on the findings of ICANN-sponsored studies which measured WHOIS data inaccuracies and trends.

ICANN continues to work to address concerns regarding potential conflicts between privacy laws or regulations and provisions of ICANN contracts relating to the collection, display and distribution of personal data via the gTLD WHOIS service. For example, ICANN adopted a procedure which details how it will respond to any situation where a registrar/registry can demonstrate that it is legally prevented by privacy laws or regulations from complying with the aforementioned contract requirements.

Recognizing concerns that the current WHOIS service might decrease in reliability and usefulness over time, the GNSO compiled a comprehensive set of technical requirements for WHOIS intended to address both known deficiencies in the current service and possible enhancements that may be needed to support various on-going policy initiatives. This inventory does not suggest policies or operational rules, but instead provides technical guidance to standards bodies and other organizations such as ARIN that are currently working on possible WHOIS successor protocols and services. ICANN recently adopted a new 2013 RAA that included many amendments to deal with WHOIS data, including validation and verification of certain WHOIS elements, service level agreements for WHOIS availability, circumstances requiring registration cancellation for false WHOIS data, and a verification process registrars might be required to undertake after receiving report of false WHOIS data. In addition, an Interim Specification was adopted defining policies for Privacy and Proxy services offered by Registrars and their affiliates – services currently used by some domain name registrants to avoid publishing their own contact information and/or identity in WHOIS data.

The WHOIS Data Reminder Policy (or WDRP) is an ICANN policy designed to protect domain name registrants. The policy requires your registrar to formally remind you once a year to review and update your contact information. The reminder, which is also referred to as a WDRP Notice, is usually sent via email and asks you to review the WHOIS information, including contact information, associated with your domain name(s) and make corrections or updates when necessary.

ICANN oversees the domain name system, but it does not send out WDRP notices. WDRP notices are sent by domain name registrars or resellers in order to comply with an ICANN policy. Although some registrars or resellers might send out messages from an "icann@" email account, these messages do not come from ICANN. ICANN requires domain name registrars to send WDRP notices to registrants in order to ensure that WHOIS records are maintained accurately.

In order to update your contact information, you will need to contact your registrar. See How do I correct my WHOIS information for more details.

ICANN does not maintain WHOIS data. In order to update your contact information in the WHOIS database, you will need to contact your registrar (or your reseller if you registered your domain name through a reseller).

See How do I correct my WHOIS information for more details.

The person or organization listed as the registrant of the domain name can make changes to the WHOIS data, including changes to the administrative contact. Contact your registrar or reseller to make the necessary changes.

There are several reasons why you might not recognize the name of your registrar. If you registered your domain name through a reseller instead of directly with the registrar, the reseller's name might not appear on the WHOIS record. You should contact the company or person used to register your domain name to see if your registrar is correct. It is also possible that your registrar's name may have changed since you registered the domain name. You should contact your registrar or ICANN (icann@icann.org) to determine if there has been a name change. If you believe your domain name was transferred to another registrar without your permission, you should contact your original registrar or reseller for assistance. If you continue to have questions about the transfer of your domain name, please visit ICANN's About Domain Name Transfer to a Different Registrar page for further assistance.

You should contact your registrar or the sender of the email message for more information.

The WHOIS service includes WHOIS clients, WHOIS servers, WHOIS data stores, and WHOIS data (domain name registration records). The WHOIS service is not a single centrally-managed data store. Rather, registration data is held in disparate locations and administered by multiple parties that conform to ICANN's standards and conventions for WHOIS service when applicable. For example, Registrars store and provide free, publicly available WHOIS data for the gtld registrations they sponsor that is accessed through a Port 43 service and a web-based service. Registries also provide WHOIS data for registrations in their gTLDs through a Port 43 service and a web-based service. In addition third parties may offer aggregated WHOIS services, sometimes for a fee, that may provide additional functionality and value added services.

When people refer to WHOIS, they may mean several different things. Some mean the WHOIS protocol that specifies the network exchange between a WHOIS client and server, whereas others refer to a perceived or conceptual WHOIS database that registries or registrars support, or to the WHOIS data that registrants provide and ICANN accredited registrars are obliged to make public according to the terms of the Registrar Accreditation Agreement (RAA).

Registries satisfy their WHOIS obligations using different delivery services depending upon their contract terms. The two common models are often characterized as “thin” and “thick” WHOIS registries. A thin registry only includes technical data sufficient to identify the sponsoring registrar, status of the registration, and creation and expiration dates for each registration in its WHOIS data store. .COM and .NET are examples of thin registries. Thick registries maintain the registrant’s contact information and designated administrative and technical contact information, in addition to the sponsoring registrar and registration status information supplied by a thin registry. .INFO and .BIZ are examples of thick registries.

Given growing concerns about identity theft and other criminal activity, many people are concerned about making their personal data publicly available on the Internet. One option for registrants is to use a valid postal and email address from their business or place of employment. Another is to use privacy protection or proxy services, sometimes for an additional fee. Some registrars make these services available through a third-party proxy service that allows you to provide the required contact information to your registrar, and the proxy service becomes the registrant of record. Usually the proxy service can disclose personal data to respond to requests from law enforcement or conflicts related to infringements on legal rights of others or when presented with evidence of actionable harm.

Another option is to register through an intermediary, such as an Internet Service Provider (ISP) or webhosting company, which then becomes the registrant of record.

Registration Data (the data element values collected or generated in connection with a Registered Name) is indispensable to the smooth operation of the DNS and is used for many legitimate uses, including:

• To determine whether or not a given domain is available.
• To contact network administrators for resolution of technical matters related to networks associated with a domain name (e.g., DNS or routing matter, origin and path analysis of DoS and other network-based attacks).
• To diagnose registration difficulties. Registration Data Directory Service (RDDS or WHOIS) queries provide information that is often useful in resolving a registration ownership issue, such as the creation and expiration dates and the identity of the registrar.
• To contact web administrators for resolution of technical matters associated with a domain name.
• To obtain the real world identity, business location and contact information of an online merchant or business, or generally, any organization that has an online presence.
• To associate a company, organization, or individual with a domain name, and to identify the party that is operating a web or other publicly accessible service using a domain name, for commercial or other purposes.
• To contact a domain name registrant for the purpose of discussing and negotiating a secondary market transaction related to a registered domain name.
• To notify a domain name registrant of the registrant's obligation to maintain accurate registration information.
• To contact a domain name registrant on matters related to the protection and enforcement of intellectual property rights.
• To establish or look into an identity in cyberspace, and as part of an incident response following an Internet or computer attack. (Security professionals and law enforcement agents use Registration Data to identify points of contact for a domain name.)
• To gather investigative leads (i.e., to identify parties from whom additional information might be obtained). Law enforcement agents use Registration Data to find email addresses and attempt to identify the location of an alleged perpetrator of a crime involving fraud.
• To investigate spam, law enforcement agents look to the RDDS to collect information on the website advertised in the spam.

ICANN's WHOIS policy has been updated from time to time through contract changes and policy development activities that originate through a bottom-up, transparent process involving all necessary constituencies and stakeholders in the Internet Community.

ICANN policy begins its development in the applicable Supporting Organizations and Advisory Committees, such as the GNSO for changes affecting generic domain names . The recognition that a policy is needed may arise from anywhere in the Internet community, the international ICANN Supporting Organizations and Committees (such as the Regional Internet Registries (through the ASO), the GNSO, the ALAC or the GAC), or the Country Code Managers (ccTLDs). ICANN is in the midst of evolving the WHOIS policy for generic domain names in response to the recommendations made by the WHOIS Policy Review Team formed under the Affirmation of Commitments. These future improvements include initiating a series of GNSO policy development processes (PDP) to evaluate the policy implications of privacy and proxy services, issues related to the translation or transliteration of WHOIS data, and whether to require all registries to offer "thick" or full WHOIS contact data. In addition, the ICANN Board has convened a group of experts(EWG) to evaluate whether WHOIS should be replaced by an entirely new model of registration data directory services. The EWG work, once it concludes, is expected to be evaluated through a separate GNSO policy development process.

Send a Complaint to ICANN about Inaccurate or missing WHOIS data

It is very important to keep your contact information up-to-date at all times so that you receive important notifications about your domain name from your registrar. These notifications are typically sent via email, and if your email is not updated, you may not receive important notifications that are designed for your protection. For example, your registrar will notify you of changes to your account and domain name registrations so that you can confirm the changes. If your email information is not up-to-date, unauthorized changes could be made to your account without your knowledge. To learn more about why it's important to keep your contact information updated, read ICANN's blog on why it's important to keep your contact information up to date.

The purpose of the WDRP notice is to remind you of your obligation to update contact information on file for your domain names. This is for your benefit and protection. Although you should always be wary of phishing messages and other fraudulent emails, a legitimate WDRP notice email serves an important purpose. Contact your registrar if you are unsure about email notices regarding your domain name registrations.