www.icann.org
Open in
urlscan Pro
2606:4700::6812:35d
Public Scan
Submitted URL: https://cclinks.hostgator.com/?e=QyyNZV57GS86k/8Z3FEc8SJs43sUmF77+8809QNG4i0hF14tIsHl2nQ+R6SsgXPelpKjNFeif/tYNr4TFJvpAZvRuj96a...
Effective URL: https://www.icann.org/resources/pages/wdrp-2012-02-25-en
Submission: On November 15 via api from US — Scanned from DE
Effective URL: https://www.icann.org/resources/pages/wdrp-2012-02-25-en
Submission: On November 15 via api from US — Scanned from DE
Form analysis 1 forms found in the DOM
<form class="search-form"><label class="hidden" for="search_text">Search ICANN.org</label><input type="search" name="search_text" id="search_text" value="" placeholder="Search ICANN.org" class="SearchBox-textField searchText"><input type="hidden"
name="previous_text" id="previous_text" autocomplete="off"><input type="submit" name="commit" value="" class="SearchBox-submit" data-disable-with=""></form>Text Content
Skip to main content
* Search ICANN.org
* Log In
* Sign Up
Get Started
ICANN for BeginnersFellowship ProgramNextGen@ICANN ProgramHistory
News and Media
AnnouncementsBlogMedia ResourcesPress ReleasesGlobal NewslettersICANN News
SubscriptionsRegional Reports
Policy
Develop PolicyOperational Design Phase (ODP)Implement Policy
Public Comment
Public Comment HomeUpcoming ProceedingsOpen ProceedingsClosed ProceedingsAbout
Public CommentOther Public Consultations
Resources
Board Activities and MeetingsAccountability MechanismsRegistrarsRegistry
OperatorsDomain Name RegistrantsContractual ComplianceDomain Name Security
ThreatsPrivacy and Proxy ServicesGovernment EngagementCareersComplaints OfficeI
Need HelpICANN 25th Anniversary Photo Mosaic
Community
Engagement Calendar
Quicklinks
Board Activities and MeetingsData Protection and PrivacyDomain Name
RegistrantsEngagement CalendarIANA ServicesICANN Acronyms and TermsICANN Grant
ProgramNew gTLD ProgramPublic Technical Identifiers (PTI)Open DataQuestion About
A Domain Name?Technology @ ICANNWSIS+20 Outreach Network
Resources
*
About ICANN
* Acronyms and Terms
* Courses and Learning
* ICANN for Beginners
*
Participate
* What ICANN Does
* Effect on the Internet
* What's Going On Now
* How to Participate
*
Fellowship Program
* Committee
* Terms & Conditions
* NextGen@ICANN Program
* President's Corner
* ICANN Management Organization Chart
* Staff
* Careers
*
In Focus
* Continuity
*
DNSSEC
* Standards
* IANA DNSSEC Root Information
* TLD DNSSEC Report
* Root Deployment
* Deployment Graph
* Tools
* Training
* Key Ceremony
* News
* Blog Posts
* Presentations
* Related Sites
* GNSO Improvements
* Travel Support
*
Media Resources
* Contacts
* ICANN News
* Subscribe and Follow
* Media Assets
* Leader Bios
* About ICANN
* Strategic Initiatives
* Additional Resources
* Board Activities and Meetings
*
Accountability
*
Accountability Mechanisms
* Reconsideration
*
Independent Review Process
* Updating the IRP
*
Ombudsman
* About
* Program
* Framework
* Standards of Practice
* Respectful Communication
* Reports
* Speeches
* Links
* Questions
*
Empowered Community
* Empowered Community Administration
* Empowered Community Administration Mailing List
* Empowered Community Correspondence
* Document Disclosure
*
Reviews
* Getting Started
*
Organizational Reviews
* ALAC
* ASO
* Board
* ccNSO
* GNSO
* Nominating Committee
* RSSAC
* SSAC
* Technical Liaison Group
*
Specific Reviews
* Accountability & Transparency
* Registration Directory Service
* Security, Stability, and Resiliency
* Competition, Consumer Trust & Consumer Choice
* CCT Metrics
* Expected Standards of Behavior
* Employee Practices and Resources
* Enhancing ICANN Accountability – Work Stream 2 Implementation
*
Governance
*
Governance Documents
* Guidelines
*
Articles of Incorporation
* Current
* Archive
*
Bylaws
* Current Bylaws
* Archive
* Board Code of Conduct
* Board Conflicts of Interest Policy
* Board Statements of Interest
*
Delegation of Authority Guidelines
* Current Guidelines
*
Archive
* DoA Guidelines (16 March 2017)
* DoA Guidelines (8 November 2016)
* Summary of Conflicts of Interest and Ethics Practices Review
* Evolving ICANN’s MSM
*
Agreements
*
NTIA IANA Functions' Stewardship Transition
* Call for Public Input: Draft Process to Develop the Proposal (8 April-8
May 2014
* Process to Develop the Proposal and Next Steps
*
Registry
* Archive
*
Affirmation of Commitments
* AOC Tracking
* ccTLD
* Partnership Memorandums of Understanding
*
Registrar
* Archive
* Annual Reports
*
Financials
* Financial Reports
* Policies, Guidelines and Procedures
* Annual Disclosure of Payments to Suppliers
* Lobbying Disclosures & Contribution Reports
*
Planning
*
Strategic Plan
* ICANN Strategic Plan for FY26-30
*
ICANN Strategic Plan for FY21-25
* Strategic Outlook Trends Program
* ICANN Strategic Plan for FY16-20
* Presentations
* RFPs
* Litigation
* Newsletter
*
Correspondence
* 2023
* 2022
* 2021
* 2020
* 2019
* 2018
* 2017
* 2016
* 2015
* 2014
* 2013
* 2012
* 2011
* 2010
* 2009
* 2008
* 2007
* 2006
* 2005
* 2004
* 2003
* 2002
* 2001
* 2000
* 1999
* 1998
* Quarterly Reports
*
Groups
* 2023 ICANN CEO Search Committee
*
RSSAC
* Charter
* SSAC
* GAC
* At-Large
* ASO
* ccNSO
* GNSO
*
Technical Liaison Group
* Technical Experts Group (TEG)
*
NomCom
* Past NomComs
* Customer Standing Committee
* Root Zone Evaluation Review Committee (RZERC)
* Business
* Civil Society
*
Complaints Office
* Complaints Report
* Domain Name System Abuse
*
Contractual Compliance
* About
*
Programs
* Approach & Process
* gTLD Registry Compliance
* Accredited Registrar Compliance
* Audit
* General Questions
* Complaint Submission & Learn More
*
Reporting & Performance Measurement
*
Notices
* Archive
* Performance Reports
* Reports
* Outreach
*
Registrars
*
Accreditation Agreement
*
Global Amendments
* 2024 Global Amendment to the RAA
* 2023 Global Amendment to the RAA
* Registrar Library
* News & Communications
*
How to Become a Registrar
* Registrar Application
* Registrar Application Instructions
* Registrar Training
*
Changes to Existing Accreditation
* Annual Registrar Compliance Certificate
* Bulk Transfers
* Data Retention Waiver
* Purchasing an ICANN-Accredited Registrar
* Registrar Data Escrow Program
* Registrar Mergers
* Registrar Name Changes
* Registrar Primary Contact Updates
* Registry-Registrar Agreement (RRA) Termination
* Renewing an Existing Accreditation
* Terminating an Accreditation
* Transferring (Assigning) an ICANN Accreditation
* Privacy and Proxy Service Providers
*
Registrar Resources
* Advisories
*
Agreements & Policies
* Policy Statement
* Billing Frequently Asked Questions (FAQ) for Registrars
* Consensus Policies
* Contact List
*
Domain Name Transfers
* Inter-Registrar Transfer Information
* Policy
* Operations Handbook for Registrars
* GDD Accounts and Services Team
* gTLD Lifecycle
* Naming Services portal
* Registration Data Access Protocol (RDAP)
* Registrar Data Escrow Reporting FAQ
* Registrar Data Escrow Agent Transition Resources
* Registrar Data Escrow Agent Change FAQ
* Registrar FAQs
* Security Response Waiver (SRW) Requests for Registrars
* Data Directory Services Privacy Law Conflicts
* Whois-Related Policies and Provisions
* History
*
Registry Operators
*
Advisories & Consensus Policies
* Advisories
*
Consensus Policies
*
Registration Data Policy
* Registration Data Policy Implementation Resources
*
Registry Service Evaluation Policy (RSEP)
* RSEP Implementation Notes
* Preliminary Determination of Competition Issues
* Reconciliation
* RSEP Announcements Archive
*
News & Events
* CP Summit
* ICANN News & Media
* ICANN Public Comment Page
* ICANN Public Meetings Calendar
*
Registry Agreements
*
Global Amendments
* 2024 Global Amendment to the Base New gTLD Registry Agreement
* 2023 Global Amendment to the Base New gTLD Registry Agreement
* 2017 Global Amendment to the Base New gTLD Registry Agreement
*
Registry Agreements Archive
* Proof of Concept Reports
* Terminated Registry Agreements
*
Registry Resources
* Bulk Transfers
* Data Protection and Privacy
*
Emergency Back-end Registry Operator (EBERO)
*
gTLD Registry Continuity
* Continuity Archive
* Form 6166 - U.S. Tax Residency Certification (TRC)
* Framework for Registry Operators to Respond to Security Threats
* Operations Handbook for Registry Operators
* GDD Accounts and Services Team
* gTLDs JSON Report
* List of Top-Level Domains
* Monthly Registry Reports
* Naming Services portal
* New gTLD Program
* New gTLD Program Case Studies
* New gTLD Registry Operator CSV Report
* Registration Data Access Protocol (RDAP)
* Registry FAQs
* Registry Listing Page
* Registry System Testing (RST)
* Service Level Agreement (SLA) Monitoring System API Specification
*
Services for Registry Operators
*
Assignment of Registry Agreement or Registry Operator Change of Control
*
Assignment of Registry Agreements
* Completed Direct Change of Control
* Registry Operator Change of Control
* Annual Certification of Compliance
* Continued Operations Instrument (COI)
* Centralized Zone Data Service (CZDS)
* Community gTLD Change Requests
* Cross-Ownership Notification Service
*
Data Escrow
* ICANN-Approved Registry Data Escrow Agents
* Registry Data Escrow Agent Change Requests
* Registry Data Escrow Agreement Amendments
* Registry Data Escrow Agent Application
* IDN Table Update and Publish
* Material Subcontracting Arrangement (MSA) Change
* New gTLD RA Renewals
* Registry Agreement Termination Service
* Registry Operator Name Change
*
RSEP Process
* Fast Track RSEP Process and Standard Authorization Language
* RSEP Process Workflow
* Technical Evaluation Panel
*
Registry Transition Processes
* EBERO Temporary Transition Process
* EBERO Transition Process - Communicate
* EBERO Transition Process - DNS
* EBERO Transition Process - Data Escrow
* EBERO Transition Process - RDDS
* EBERO Transition Process - SRS
* Prospective Registry Evaluation Matrix
* Registry Transition Process with Proposed Successor - Check Support
* Registry Transition Process with Proposed Successor - Communicate
* Registry Transition Process with Proposed Successor - Evaluate
* Registry Transition Process with Proposed Successor
* Registry Transition Process with Request for Proposals - Check Support
* Registry Transition Process with Request for Proposals - Communicate
* Registry Transition Process with Request for Proposals - Evaluate
* Registry Transition Process with Request for Proposals - RFP
* Registry Transition Process with Request for Proposals
* Removal of Cross-Ownership Restrictions
*
Reserved Names
*
Two-Character ASCII Labels
* Two-Character Archive
* Country & Territory Names
*
RRA Amendment
* RRA Amendment Procedure
* RRA Amendment with Temporary Specification
* Registry-Registrar Agreement (RRA) Termination
*
Rights Protection Mechanisms & Dispute Resolution Procedures
* INGO Claims Notification
* PDDRP
* PICDRP
* RRDRP
* TMCH
* TMCH Requirements
* URS
* Security Response Waiver (SRW) Requests for Registry Operators
*
Domain Name Registrants
* About Domain Names
* ICANN Policies
*
Registration Data Policies
*
WHOIS and Registration Data Directory Services
*
The Domain Name Registration Process
* Using Domain Name Registration Data
* Keeping Registration Data Accurate
* Access and the Evolution of the WHOIS System
* Domain Name Industry
* Registering Domain Names
*
Managing Domain Names
* Contact Information and WDRP
* Securely Managing Your Domain Name
* Transferring Domain Names
* Renewing Domain Names
* Rights and Responsibilities
* Spam, Phishing, and Website Content
* Trademark Infringement
* GDS Metrics
*
Identifier Systems Security, Stability and Resiliency (OCTO IS-SSR)
* IS-SSR Team Blogs
* Security Terminology
* Document Archive
*
ccTLDs
* Background Materials
* Agreements
* Delegation
* Root Zone Database
* Model MOU
* Workshops
* ICANN and ISO
*
Internationalized Domain Names
*
Root Zone Label Generation Rules (LGR)
* Generation Panel Update
* Maximal Starting Repertoire
* Proposals for Root Zone Label Generation Ruleset
* IDN Variant TLD Implementation
* LGR Toolset
* IDN ccTLD Fast Track
* IDN Implementation Guidelines
* Second-Level LGR Reference
* Resources
* Announcements and Blogs Posts
* New gTLD Program
*
Universal Acceptance Initiative
* Make your systems UA-ready
* Universal Acceptance Steering Group (UASG)
* UA Training
* UA Day
* UA Readiness Evaluations
* Announcements and Blogs Posts
*
Policy
* Policy Mission
* Policy Staff Goals
* Presentations
*
Global Addressing
* IPv6 Allocation
* ASN Allocation
* Post Exhaustion IPv4 Allocation
* New RIRs Criteria
* Review Procedures
* Policy Updates
* Operational Design Phase (ODP)
* Implementation
*
Public Comment
* Open
* Upcoming
* Archive
* Root Zone KSK Rollover
*
Technical Functions
* Tech Day Archive
*
ICANN Locations
* Report Security Issues
* PGP Keys
* Certificate Authority
* Registry Liaison
* Ombudsman
*
I Need Help
* Dispute Resolution
*
Domain Name Dispute Resolution
*
Charter Eligibility Dispute Resolution Policy
* Providers
* Rules
*
Eligibility Requirements Dispute Resolution Policy
* Providers
* Rules
*
Intellectual Property Defensive Registration Challenge Policy
* Providers
* Rules
*
Qualification Challenge Policy
* Providers
* Rules
*
Restrictions Dispute Resolution Policy
* Providers
* Rules
*
Transfer Dispute Resolution Policy
* Providers
*
Uniform Domain Name Dispute Resolution Policy
* Policy Document
* Providers
* Provider Approval Process
* Rules
* Principal Documents
* Proceedings
* Historical Documents
* Timeline
*
Name Collision
* FAQ: IT Professionals
* FAQ: Registries
* Guide for IT Professionals
* Recommendations for New ccTLDs
* Report a Problem
* Registrar Problems
* Whois Data Correction
* Independent Review Process
* Request for Reconsideration
* Document
WHOIS DATA REMINDER POLICY
THIS PAGE IS AVAILABLE IN:
* English
* العربية
* Español
* Français
* 日本語
* 한국어
* Português
* Pусский
* 中文
On 21 February 2024, an updated version of this policy was published to reflect
changes required to implement the Registration Data Policy. Click here to view
the updated version of this policy. You may view the changes in the redline.
At least annually, a registrar must present to the registrant the current Whois
information, and remind the registrant that provision of false Whois information
can be grounds for cancellation of their domain name registration. Registrants
must review their Whois data, and make any corrections.
--------------------------------------------------------------------------------
Notes
Introduction: The Whois Data Reminder Policy (WDRP) was adopted by ICANN as a
consensus policy on 27 March 2003. All ICANN-accredited registrars must comply
with the WDRP with respect to registrations they sponsor in all top-level
domains for which they are accredited. Details of compliance requirements are
provided below.
Process by Which the Policy Was Adopted: The WDRP was established as a consensus
policy by ICANN Board resolution 03.41, which was adopted by a 13-1-0 vote by
ICANN's Board of Directors on 27 March 2003. It was one of four policies
concerning Whois issues that the Generic Names Supporting Organization (GNSO)
Council, by a 21-3-0 vote on 20 February 2003, recommended be established as
consensus policies.
The GNSO Council and Board votes were based on the Final Report of the GNSO
Council's Whois Task Force on Whois Data Accuracy and Bulk Access. That report
documented the extent of agreement and disagreement among impacted groups, the
outreach process used to seek to achieve adequate representation of the views of
groups that are likely to be impacted, and the nature and intensity of reasoned
support and opposition to the proposed policy.
The report was posted on the ICANN web site on 11 March 2003, with a call for
public comment. Various public comments were received and considered by the
Board, and the report was discussed at the ICANN Public Forum session held in
Rio de Janeiro on 26 March 2003.
Pursuant to Resolution 03.42, notice of the adoption of this policy was given to
all registrars on 16 June 2003.
Time for Coming into Compliance: As provided in subsections 3.7.8, 4.1 and 4.4
of the ICANN Registrar Accreditation Agreement, all ICANN-accredited registrars
must come into compliance with the WDRP by their "Compliance Date", as described
in the next two sentences. The Compliance Date for registrars accredited before
16 June 2003 is 31 October 2003. The Compliance Date for registrars accredited
after 16 June 2003 is the effective date of their accreditation agreements.
Beginning on its Compliance Date, each registrar must provide, before the
passage of the anniversary of the creation date of each registration the
registrar sponsors, a WDRP Notice (described below) to the registrant for that
registration. By way of example, a registrar with a Compliance Date of 31
October 2003 is required to give a WRDP notice for registrations it sponsors on
the following schedule:
Compliance Date is 31 October 2003
Domain Name Creation Date WDRP Notice Required No Later Than example.com 14
October 1995 14 October 2004 (and by 14 October of every year thereafter)
example.biz 25 June 2003 25 June 2004 (and by 25 June of every year thereafter)
example.info 15 June 2003 15 June 2004 (and by 15 June of every year thereafter)
example.net 12 November 1997 12 November 2003 (and by 12 November of every year
thereafter) example.org 1 January 1993 1 January 2004 (and by 1 January of every
year thereafter) example.example.name 31 December 2002 31 December 2003 (and by
31 December of every year thereafter)
(Note: WDRP Notices for registrations with creation dates of 29 February may be
given no later than 1 March in non-leap years.)
What the WDRP Notice Must Include: Each WDRP notice must include a copy of the
data elements listed in RAA subsection 3.3.1 as contained in the registrar's
database for each registration, plus a statement reminding the registrant that
under the terms of the registration agreement the provision of false Whois
information can be grounds for cancellation of a domain name registration.
How, and to Whom, the WDRP Notice May Be Presented: The WDRP Notice can be
presented via web, fax, postal mail, e-mail, or other appropriate means. It can
be presented in one or more languages, including at least the language of the
registration agreement. The Notice may be presented to the registrant either
directly or through the administrative contact for each registration.
Documentation Requirements: Registrars must maintain either copies of each WDRP
Notice or an electronic database documenting the date and time, and the content,
of each WDRP notice sent under this policy. Registrars shall make these records
available for inspection by ICANN in accordance with the usual terms of the
Registrar Accreditation Agreement. ICANN will consider proper notification to
have been given for a registration if the registrar can show that a WDRP Notice
meeting the requirements stated above was given at any time in the year before
each anniversary of the registration's creation date (for anniversary dates on
or after the Compliance Date).
Model WDRP Notice: In order to assist registrars in preparing the required
notice, ICANN has provided the following Model WDRP Notice:
--------------------------------------------------------------------------------
[Sample] Whois Data Reminder
Dear Valued Customer,
This message is a reminder to help you keep the contact data associated with
your domain registration up-to-date. Our records include the following
information:
> > Domain: example.com
> > Registrar Name: IANA_RESERVED
> >
> > Registrant:
> > Name: Internet Assigned Numbers Authority (IANA)
> > Address: 4676 Admiralty Way, Suite 330
> > City: Marina del Rey
> > State/Province: CA
> > Country: US
> > Postal Code: 92092
> >
> > Administrative Contact:
> > Name: Internet Assigned Numbers Authority (IANA)
> > Address: 4676 Admiralty Way, Suite 330
> > City: Marina del Rey
> > State/Province: CA
> > Country: US
> > Postal Code: 92092
> > Phone: 310-823-9358
> > Fax: 310-823-8649
> > Email: res-dom@iana.org
> >
> > Technical Contact:
> > Name: Internet Assigned Numbers Authority (IANA)
> > Address: 4676 Admiralty Way, Suite 330
> > City: Marina del Rey
> > State/Province: CA
> > Country: US
> > Postal Code: 92092
> > Phone: 310-823-9358
> > Fax: 310-823-8649
> > Email: res-dom@iana.org
> >
> > Original Creation Date: 11/01/2001
> > Expiration Date: 11/01/2001
> >
> > Nameserver Information:
> > Nameserver: a.iana-servers.net.
> > Nameserver: b.iana-servers.net.
> > Nameserver: c.iana-servers.net.
If any of the information above is inaccurate, you must correct it by visiting
our website. (If your review indicates that all of the information above is
accurate, you do not need to take any action.) Please remember that under the
terms of your registration agreement, the provision of false Whois information
can be grounds for cancellation of your domain name registration.
Thank you for your attention.
Best regards,
Your ICANN-Accredited Registrar
A set of frequently asked questions concerning the WDRP, from the perspective of
the registrant, can be found here.
ICANN is not responsible for profile content or verification of user details.
* YouTube
* Twitter
* LinkedIn
* Flickr
* Facebook
* Newsletters
* Community Wiki
* ICANN Blog
WHO WE ARE
* Get Started
* ICANN Learn
* Participate
* Diversity at ICANN
* Groups
* Board Members
* President's Corner
* Staff
* Careers
* Public Responsibility
CONTACT US
* Locations
* I Need Help
* Report Security Issues
* Certificate Authority
* Registry Liaison
* Ombuds
* Complaints Office
* Media Resources
ACCOUNTABILITY AND TRANSPARENCY
* Accountability Mechanisms
* Document Disclosure
* Independent Review Process
* Request for Reconsideration
* Empowered Community
* Employee Anonymous Hotline Policy and Procedures
GOVERNANCE
* Governance Documents
* Agreements
* Organizational Reviews
* Specific Reviews
* Annual Report
* Financials
* Planning
* RFPs
* Litigation
* Correspondence
HELP
* Dispute Resolution
* Domain Name Dispute Resolution
* Name Collision
* ICANN Lookup
* Registration Data Request Service (RDRS)
DATA PROTECTION
* Data Privacy Practices
* Privacy Policy
* Terms of Service
* Cookies Policy
© Internet Corporation for Assigned Names and Numbers.Privacy PolicyTerms of
ServiceCookies Policy
A NOTE ABOUT OUR TERMS OF SERVICE:
We have updated our electronic terms of service to provide greater transparency
and align with laws applicable to us. Learn more.
This site uses cookies to deliver an efficient user experience and to help us
see how the site is used. Learn more.OK
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include
characters used in the local representation of languages that are not written
with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can
contain Latin letters with diacritical marks, as required by many European
languages, or may consist of characters from non-Latin scripts such as Arabic or
Chinese. Many languages also use other types of digits than the European
""0-9"". The basic Latin alphabet together with the European-Arabic digits are,
for the purpose of domain names, termed ""ASCII characters"" (ASCII = American
Standard Code for Information Interchange). These are also included in the
broader range of ""Unicode characters"" that provides the basis for IDNs. The
""hostname rule"" requires that all domain names of the type under consideration
here are stored in the DNS using only the ASCII characters listed above, with
the one further addition of the hyphen ""-"". The Unicode form of an IDN
therefore requires special encoding before it is entered into the DNS. The
following terminology is used when distinguishing between these forms: A domain
name consists of a series of ""labels"" (separated by ""dots""). The ASCII form
of an IDN label is termed an ""A-label"". All operations defined in the DNS
protocol use A-labels exclusively. The Unicode form, which a user expects to be
displayed, is termed a ""U-label"". The difference may be illustrated with the
Hindi word for ""test"" — परीका — appearing here as a U-label would (in the
Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated
ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A
domain name that only includes ASCII letters, digits, and hyphens is termed an
""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a
name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."