Showing posts with label WHOIS accuracy. Show all posts
Showing posts with label WHOIS accuracy. Show all posts

2015-12-19

What Are You Agreeing To When You Register That Domain Name?

Re: ICANN 2013 RAA: Domain Name Registrant Provisions

So what are you agreeing to when you register that domain name?

Better read both the terms of your Registrar's Registration Agreement and the terms of that Registrar's Agreement with ICANN (RAA), the current version of which is the 2013 RAA:

ICANN: Current Agreement - 2013 Registrar Accreditation Agreement
(For Registrar Accreditation Agreements entered into after 28 June 2013)
2013 RAA PDFs: English | Español | العربية | Français | 日本語 | 한국어 | Português | русский | 中文
Redline of 2013 RAA against 2009 RAA [PDF, 425 KB]
2013 RAA Frequently Asked Questions

2009 Registrar Accreditation Agreement
(For Registrar Accreditation Agreements entered into between 21 May 2009 and 28 June 2013)

ICANN 2013 Registrar Accreditation Agreement (2013 RAA) (excerpts follow, emphasis added):

3.7.7 Registrar shall require all Registered Name Holders to enter into an electronic or paper registration agreement with Registrar including at least the provisions set forth in Subsections 3.7.7.1 through 3.7.7.12, and which agreement shall otherwise set forth the terms and conditions applicable to the registration of a domain name sponsored by Registrar. The Registered Name Holder with whom Registrar enters into a registration agreement must be a person or legal entity other than the Registrar, provided that Registrar may be the Registered Name Holder for domains registered for the purpose of conducting its Registrar Services, in which case the Registrar shall submit to the provisions set forth in Subsections 3.7.7.1 through 3.7.7.12 and shall be responsible to ICANN for compliance with all obligations of the Registered Name Holder as set forth in this Agreement and Specifications and Policies. Registrar shall use commercially reasonable efforts to enforce compliance with the provisions of the registration agreement between Registrar and any Registered Name Holder that relate to implementing the requirements of Subsections 3.7.7.1 through 3.7.7.12 or any Consensus Policy.

3.7.7.1 The Registered Name Holder shall provide to Registrar accurate and reliable contact details and correct and update them within seven (7) days of any change during the term of the Registered Name registration, including: the full name, postal address, e-mail address, voice telephone number, and fax number if available of the Registered Name Holder; name of authorized person for contact purposes in the case of an Registered Name Holder that is an organization, association, or corporation; and the data elements listed in Subsections 3.3.1.2, 3.3.1.7 and 3.3.1.8.

3.7.7.2 A Registered Name Holder's willful provision of inaccurate or unreliable information, its willful failure to update information provided to Registrar within seven (7) days of any change, or its failure to respond for over fifteen (15) days to inquiries by Registrar concerning the accuracy of contact details associated with the Registered Name Holder's registration shall constitute a material breach of the Registered Name Holder-registrar contract and be a basis for suspension and/or cancellation of the Registered Name registration.

3.7.7.3 Any Registered Name Holder that intends to license use of a domain name to a third party is nonetheless the Registered Name Holder of record and is responsible for providing its own full contact information and for providing and updating accurate technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the Registered Name. A Registered Name Holder licensing use of a Registered Name according to this provision shall accept liability for harm caused by wrongful use of the Registered Name, unless it discloses the current contact information provided by the licensee and the identity of the licensee within seven (7) days to a party providing the Registered Name Holder reasonable evidence of actionable harm.

3.7.7.4 Registrar shall provide notice to each new or renewed Registered Name Holder stating:
3.7.7.4.1 The purposes for which any Personal Data collected from the applicant are intended;
3.7.7.4.2 The intended recipients or categories of recipients of the data (including the Registry Operator and others who will receive the data from Registry Operator);
3.7.7.4.3 Which data are obligatory and which data, if any, are voluntary; and
3.7.7.4.4 How the Registered Name Holder or data subject can access and, if necessary, rectify the data held about them.

3.7.7.5 The Registered Name Holder shall consent to the data processing referred to in Subsection 3.7.7.4.
3.7.7.6 The Registered Name Holder shall represent that notice has been provided equivalent to that described in Subsection 3.7.7.4 to any third-party individuals whose Personal Data are supplied to Registrar by the Registered Name Holder, and that the Registered Name Holder has obtained consent equivalent to that referred to in Subsection 3.7.7.5 of any such third-party individuals.
3.7.7.7 Registrar shall agree that it will not process the Personal Data collected from the Registered Name Holder in a way incompatible with the purposes and other limitations about which it has provided notice to the Registered Name Holder in accordance with Subsection 3.7.7.4 above.
3.7.7.8 Registrar shall agree that it will take reasonable precautions to protect Personal Data from loss, misuse, unauthorized access or disclosure, alteration, or destruction.
3.7.7.9 The Registered Name Holder shall represent that, to the best of the Registered Name Holder's knowledge and belief, neither the registration of the Registered Name nor the manner in which it is directly or indirectly used infringes the legal rights of any third party.
3.7.7.10 For the adjudication of disputes concerning or arising from use of the Registered Name, the Registered Name Holder shall submit, without prejudice to other potentially applicable jurisdictions, to the jurisdiction of the courts (1) of the Registered Name Holder's domicile and (2) where Registrar is located.
3.7.7.11 The Registered Name Holder shall agree that its registration of the Registered Name shall be subject to suspension, cancellation, or transfer pursuant to any Specification or Policy, or pursuant to any registrar or registry procedure not inconsistent with any Specification or Policy, (1) to correct mistakes by Registrar or the Registry Operator in registering the name or (2) for the resolution of disputes concerning the Registered Name.
3.7.7.12 The Registered Name Holder shall indemnify and hold harmless the Registry Operator and its directors, officers, employees, and agents from and against any and all claims, damages, liabilities, costs, and expenses (including reasonable legal fees and expenses) arising out of or related to the Registered Name Holder's domain name registration.

3.7.8 Registrar shall comply with the obligations specified in the Whois Accuracy Program Specification. In addition, notwithstanding anything in the Whois Accuracy Program Specification to the contrary, Registrar shall abide by any Consensus Policy requiring reasonable and commercially practicable (a) verification, at the time of registration, of contact information associated with a Registered Name sponsored by Registrar or (b) periodic re-verification of such information. Registrar shall, upon notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy.
3.7.9 Registrar shall abide by any Consensus Policy prohibiting or restricting warehousing of or speculation in domain names by registrars.
3.7.10 Registrar shall publish on its website(s) and/or provide a link to the Registrants' Benefits and Responsibilities Specification attached hereto and shall not take any action inconsistent with the corresponding provisions of this Agreement or applicable law.
3.7.11 Registrar shall make available a description of the customer service handling processes available to Registered Name Holders regarding Registrar Services, including a description of the processes for submitting complaints and resolving disputes regarding the Registrar Services.
3.7.12 Nothing in this Agreement prescribes or limits the amount Registrar may charge Registered Name Holders for registration of Registered Names. 


Caveat Emptor!

See also: 



DISCLAIMER

2015-08-26

ICANN Webinar August 26 on WHOIS Accuracy Reporting System Phase I

As announced by ICANN on August 12, 2015:

ICANN plans to publish the WHOIS Accuracy Reporting System Phase I report in the coming weeks. A webinar is scheduled for 26 August 2015, and will focus on the findings of the report and its implications for the community, including domain name registrants:

Date / Time: 26 August 2015, 15:00 - 16:00 UTC (time zone converter) 11:00AM ET (US)
Online: https://icann.adobeconnect.com/gdd
Teleconference: Download numbers [PDF, 124 KB] (Passcode: GDD)

The webinar will be conducted in English. Recordings will be published in the knowledge center of WHOIS website at: http://whois.icann.org/en/knowledge-center.

Additional background and webinar info:

Participants will learn about the results of the Phase 1 Syntactical Validation Study, which measured the overall syntactical (formatting) accuracy of WHOIS records. The results will include comparisons based on Registrar Accreditation Agreements (2009 RAA v. 2013 RAA), top-level domain types (e.g., new or "legacy" gTLDs) and across ICANN regions.


The WHOIS Accuracy Reporting System is an ICANN initiative born out of recommendations from the 2012 WHOIS Review to improve oversight of the WHOIS Program. ICANN committed to proactively identifying potentially inaccurate gTLD WHOIS contact data and forwarding potentially inaccurate records to gTLD registrars for investigation and follow up. A pilot study conducted in 2014, which acted as a proof of concept of this system, was designed with the intention of testing its key components so the framework could be leveraged to develop repeatable processes to produce assessments. Phase 1 takes lessons learned from the pilot study and operationalizes the Accuracy Reporting System. The Phase 1 report will provide information to the community on overall WHOIS accuracy, leading types of nonconformances (based on the applicable Registrar Accreditation Agreement), and data that ICANN's Compliance team will be required to follow up on with registrars regarding potentially inaccurate records.

See also:

2015-02-18

ICANN WHOIS Accuracy Pilot Study Report, Comment Period Ends 27 FEB

ICANN WHOIS Accuracy Pilot Study Report, Comment Period Ends 27 Feb 2015 23:59 UTC:

WHOIS Accuracy Pilot Study Report - ICANN: "The WHOIS Pilot Study Report published today [Dec 23, 2014] for public comment describes the results of a pilot accuracy study conducted by NORC at the University of Chicago. The Report illustrates the findings and methodology to be deployed in the WHOIS Accuracy Reporting System (ARS) under development by ICANN. By publishing it for public comment, ICANN is seeking feedback on the approach, methodology, and reporting formats used in the Pilot Study to help shape the final design of the ARS...." (read more at the link above)

NORC WHOIS Accuracy Pilot Report [PDF, 1.5 MB]

more info:

2014-12-22

Avoid Website Suspension, ICANN Verification Tutorial (video)

The Oatmeal was temporarily shutdown by ICANN: here’s how to avoid having this happen | Name.com Blog: 31 Jul 2014 "... Today, however, we were shocked and saddened to see that The Oatmeal had been taken down. One of the most popular websites on the ‘Net had been eviscerated. The content was gone; the enlightening and hilarious glow darkened. What happened? Well if we were shocked it was down, we were even more surprised the site wasn’t resolving because of one simple little task: ICANN Verification. (We said ‘simple’ but we’re not going to say it’s not annoying.) We’re also very happy that we can help. To avoid waking up to your website disappeared by the international agents of ICANN, here’s the scoop on what ICANN verification is and how you verify your domain...."

ICANN Verification Tutorial -

ICANN now requires that each contact information for domains be verified via email or phone. (Name.com video published on Apr 3, 2014)

further information about WHOIS accuracy:
https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois-accuracy
and
https://www.icann.org/resources/pages/contact-verification-2013-05-03-en




Domain Mondo archive