Outreach Program 20 November 2013

Similar documents
Compliance Outreach Wednesday, 26 March 2014

Contractual Compliance

ICANN Contractual Compliance. ALAC Mee(ng. Sunday, 23 March 2014 #ICANN49

ICANN Contractual Compliance. IPC Mee(ng. Tuesday, 25 March 2014 #ICANN49

Contractual Compliance Update. Contractual Compliance ICANN 57 5 November 2016

Registrar Stakeholder Mee2ng Tuesday, 25 March 2014

Intellectual Property Constituency (IPC)

Contractual Compliance Update ICANN 52 February 2015

Contractual Compliance. Text. IPC Meeting. Tuesday, 24 June 2014 #ICANN50

Program Update. Contractual Compliance ICANN March 2017

Contractual Compliance Update. Contractual Compliance ICANN October 2015

Contractual Compliance Update ICANN June 2015

Internet Corporation for Assigned Names & Numbers Contractual Compliance Update

Contractual Compliance Update. Contractual Compliance ICANN 55 9 March 2016

Contractual Compliance Registrars Outreach With focus on AP March 27, 2014

Contractual ICANN. An Overview for Newcomers 11 March 2012

Next Steps for WHOIS Accuracy Global Domains Division. ICANN June 2015

Registry Outreach. Contractual Compliance ICANN February 2015

Registrar Session ICANN Contractual Compliance

Contractual Compliance 2014 Annual Report. Internet Corporation for Assigned Names & Numbers

Contractual Compliance. Registry Stakeholder Group March 2012

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

Internet Corporation for Assigned Names & Numbers Contractual Compliance Update

Update on ICANN Domain Name Registrant Work

Contractual Compliance Update. Registrar Stakeholder Meeting. 16 October 2012

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

Registry Outreach. Contractual Compliance ICANN October 2015

WHOIS Accuracy Reporting System (ARS): Phase 2 Cycle 1 Results Webinar 12 January ICANN GDD Operations NORC at the University of Chicago

gtld Compliance Program Contractual Compliance

Progress Report Negotiations on the Registrar Accreditation Agreement Status as of 1 March 2012

Public Safety Working Group (PSWG)

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

U85026A Detector 40 to 60 GHz

General Data Protection Regulation (GDPR)

Registry Outreach. Contractual Compliance ICANN March 2016

Privacy and Proxy Service Provider Accreditation. ICANN58 Working Meeting 11 March 2017

Programming Note. Agilent Technologies Quick Reference Guide For the 8757D/E Scalar Network Analyzer

RDAP Implementation. Francisco Arias & Gustavo Lozano 21 October 2015

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Topic LE /GAC position Registrar Position Agreement in Principle 1. Privacy and Proxy services

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Draft Thick RDDS (Whois) Consensus Policy and Implementation Notes

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Registrar Outreach. Contractual Compliance ICANN June 2015

Improving WHOIS- An Update. 20 November, 2013

Rights Protection Mechanisms: User Feedback Session

Safety. Introduction

Computer

Law Enforcement Recommended RAA Amendments and ICANN Due Diligence Detailed Version

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Payphone Origination Service Charge Rate Per Min. Mobile Origination Service Charge. MLB Switched Rate Per Min. MLB Dedicated Rate Per Min

Letter from the Vice President of Contractual Compliance

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Supplier Responding to New Products RFP Event

Step 1: New Portal User User ID Created Using IdentityIQ (IIQ)

Purchasing. Operations 3% Marketing 3% HR. Production 1%

Power Analyzer Firmware Update Utility Version Software Release Notes

The Role of SANAS in Support of South African Regulatory Objectives. Mr. Mpho Phaloane South African National Accreditation System

IATF Stakeholder Conference

Global entertainment and media outlook Explore the content and tools

.BIZ Agreement Appendix 10 Service Level Agreement (SLA) (22 August 2013)

Patent Portfolio Overview July The data in this presentation is current as of this date.

Introduction. Prepared by: ICANN Org Published on: 12 January 2018

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary

Inter-Registrar Transfer Policy (IRTP) Audit Report

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

END-OF-SALE AND END-OF-LIFE ANNOUNCEMENT FOR THE CISCO MEDIA CONVERGENCE SERVER 7845H-2400

Cisco Aironet In-Building Wireless Solutions International Power Compliance Chart

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE AND COURIER

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF TERMINATION OF REGISTRAR ACCREDITATION AGREEMENT

Draft Applicant Guidebook, v3

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

Managed LAN Service Level Agreement

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE AND COURIER RE: NOTICE OF TERMINATION OF REGISTRAR ACCREDITATION AGREEMENT

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

International Roaming Critical Information Summaries JULY 2017

Cisco Value Incentive Program Advanced Technologies: Period 7

Patent Portfolio Overview May The data in this presentation is current as of this date.

Name Collision Occurrence Management Framework

iclass SE multiclass SE 125kHz, 13.56MHz 125kHz, 13.56MHz

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER RE: NOTICE OF BREACH OF REGISTRAR ACCREDITATION AGREEMENT

addendum Uptime Cisco customer interactive solutions

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

Advisory Statement: Temporary Specification for gtld Registration Data

For: Ministry of Education From Date: 19 November 18-2 December 18 Venue: M1 Shops

Innovative Fastening Technologies

TRANSMITTED VIA ELECTRONIC MAIL, FACSIMILE, AND COURIER

gtld Registry Ongoing Operations

CYBERTECH MIDWEST Indianapolis, Indiana

OPERATIONS MANUAL Audio Conferencing

Enterprise price plan guide Vodafone One Net Business

International Business Mail Rate Card

Items exceeding one or more of the maximum weight and dimensions of a flat. For maximum dimensions please see the service user guide.

Transcription:

Contractual Compliance! Outreach Program 20 November 2013

Agenda Topics Ø Bulk Whois Inaccuracy Submission Update! Ø Expired Registration Recovery Policy Update! Ø 2013 RAA Readiness Update! Ø New Registry Agreement Readiness Update! Ø Audit Program Update! Ø Contractual Compliance Metrics! Ø Q & A! 2

Bulk Whois Inaccuracy Complaint Submission in Production! Ø Bulk means the ability to submit complaints through a single file upload." Ø Three-month pilot (10 July thru 11 October 2013)" Limited to 100 complaints per week/user" Three users invited to participate from the Security and Brand protection industry" Ø Bulk complaints are processed as single complaint " Ø Mandatory TERMS OF USE" Ø Please refer to appendix for more details" 3

Bulk Whois Inaccuracy Complaint Submission Pilot Highlights "! Outreach session with registrars and reporters about the bulk pilot in June 2013" Complaints resolved by registrar within the 1 st Notice turn-around time" 340 total bulk complaints received during pilot" All submissions from Brand Protection reporter " Second reporter submitted successfully to test/dev environment only" 4

Invalid Complaint Process! Ø Examples of invalid complaints: Whois complaints referring to data not in current Whois Complaints containing profanity, insulting, threatening or harassing language Complaints out of Contractual Compliance scope Ø ICANN sends a closure notice with the reason (why) Ø ICANN suspends repeat offender s ability to submit complaints 5

Invalid Complaint Process (continue)! Ø Two complainants suspended in past 2 years Ø Complainant A - Submitted 191 invalid Whois inaccuracy complaints within 8 weeks; received a closure notice/complaint with reason(s); Complainant s reports were that every Whois field was incorrect, including well-known registrars, privacy/proxy services, and Internet websites Ø Complainant B - 37 emails with offensive language and a threat. 6 Back to Top

Expired Registration Recovery Policy Update! 44 EDDP/ERRP complaints since 1 September 2013" Common issues:" - Registration agreements or auto-renewal and deletion policies not updated" - Renewal notices not properly sent" - Resolution path not interrupted after Sep 1 st if domain expired before Aug 31 st" - Link: http://www.icann.org/en/resources/registrars/ consensus-policies/errp" 7 Back to Top

Outreach Activities Summary! Ø 2013 RAA Registrar outreach meetings in Los Angeles, Xiamen and Berlin" Ø 2013 RAA Registrar outreach via webinars" Ø Latin America Registrar outreach" 8

2013 RAA Effective Upon Execu+on + Registrar Must enter into agreements with resellers (Section 3.12)" + Registration Data Directory Service Specification (Whois formatting)" + Must provide specific information to ICANN and publish on website: " - - Correspondence address for the Registrar" If the location or address of registrar s principal place of business is different from the correspondence address, provide details including address, phone number, fax number and email address" - Officer(s) full name, contact information, and position" - Name of the ultimate parent entity of the registrar, if applicable" + Must provide notice to ICANN in 7 days of bankruptcy, convictions and security breaches (Section 3.20)" + Additional Reasons for Suspension and Termination (Sections 5.5 and 5.7)" + CEO Certification - Due 20 January 2014 (Section 3.15)" 9

2013 RAA Update! + Two new Learn More pages (and complaint forms) were added to ICANN.ORG" - Privacy/Proxy Registration Service" - Whois Format" + Changes to 4 Current Complaint Types" - Whois Inaccuracy" - Registrar Contact Information" - Link to Registrant Rights and Responsibilities" - Data Retention" - All effective 1 January 2014" + Adding 11 New Complaint Types" + Enhanced Enforcement Tools" 10

2013 RAA Effective 1 January 2014! + Abuse Contact Requirements (Section 3.18)" + Description of Customer Service Handling Process (Section 3.7.11) " + Registrars and Resellers must provide a link to Registrant Benefits and Responsibilities (Sections 3.7.10 and 3.12.7)" + Whois Accuracy Program Specification" + Data Retention Specification" + Additional Registrar Operation Specification (DNSSEC, IDNs and IPV6)" + Section 2.2 of the Registration Data Directory Service Specification RE: Whois Service Level Agreement" + Registrars and Resellers shall comply with the Proxy and Privacy Registration Program (Sections 3.12.4 and 3.14) " 11

Registrar Related Complaint Types! Effec+ve at Execu+on Effec+ve 1 January 2014 Reseller Agreement Sec$on 3.12 Abuse Contact Data Sec$on 3.18 CEO Cer;fica;on Sec$on 3.15 Registrar Informa;on Specifica;on Sec$on 3.17 and Registrar Informa$on Specifica$on Whois Format Registra$on Data Directory Service (Whois) Specifica$on Whois SLA Sec$on 2.2 of Registra$on Data Directory Service (Whois) Specifica$on Customer Service Handling Process Sec$on 3.7.11 Failure to Support DNSSEC, IDNs, and IPv6 Sec$on 3.19 & Addi$onal Registrar Opera$on Specifica$on Privacy/Proxy Registra;on Program Sec$on 3.4.1.5 and Specifica$on on Privacy and Proxy Registra$ons Domain Not in DNS for Non- response to Whois inquiry Whois Accuracy Program Specifica$on No;fy ICANN of Bankruptcy, Convic;on or Security Breach Sec$on 3.20 12 Back to Top

New Registry Agreement Efforts Applicant Guidebook Timeline! Contrac+ng Compliance Check Sunrise Processes DRPs Other New Registry Complaints Sunrise Claims Services General Registra+ons Delegated TLD Outreach Claims Processes Legacy Complaints 13 Link to ICANN.org: " http://www.icann.org/en/resources/compliance/registries "

Compliance Scope! + The Registry Agreement and applicable Consensus Policies! + The Dispute Resolution Procedures! - Public Interest Commitments! - Community Registration Restrictions! - Trademark Post-Delegation! - Uniform Rapid Suspension! + The Sunrise Processes! + The Claims Services Processes! + The Audit is limited to the representations and warranties in Article 1, and the covenants in Article 2! 14

15 Registry Related Complaint Types! Completed! + Data Escrow! + Monthly Reports! + SLA! + Reserved Names! + Registry Fees! + Sunrise Processes & Procedures! + Centralized Zone File Access! + Name Collision SLDs Blocked! + Post-delegation Procedures! + Public Interest Commitments,! + Registry Restrictions! + Trademark Post-Delegation! + Rights Protection Mechanism! - Uniform Rapid Suspension! Work in Progress! + Wildcard Prohibition! + Abuse Contact Data! + Registry Operator Code of Conduct! + Trademark Claims Notice! + Continued Operations Instrument! + Failure to Notify ICANN! - Officer/Board Member Conviction! - Bankruptcy!! Link to ICANN.ORG: hsp://www.icann.org/en/resources/compliance/registries

Outreach Activities Summary! Ø New Registry Agreement outreach with the gtlds delegated in 2013" 16 Back to Top

Self Internal Audit Exercise! + Conducted an Internal audit in July 2013 to assess compliance with the process and procedures" + 45 total controls in scope " + 8 findings were identified " + Exceptions noted were system software issue and procedural " + Compliance team has corrected procedural items in Aug 2013 " + Software updates to deploy in Dec 2014" + Plan to conduct 2 nd internal audit May 2014" 17 "

Year-2 Audit Program Timeline! 2012-2015 Audit Process Flow Planning Phase Week 1 to Week 12 Week 13 to Week 15 Week 16 to Week 28 Week 29 to Week 31 Start Create Audit Scope Build Audit Schedule-(2 Wks) Organizing Phase Develop Metrics Goals Establish Roles Assign Resources (1 Wk) Pre-Audit Notification Phase Send 2 Weeks Notification to Rg/Ry Audit Phase 1) Request sent for Information-RFI (1-2-3 Process) 2) Collect and Collate Data (3 Weeks) 3) Conduct Audit (6-8 Weeks)- Q&A (2 Weeks)-by CC Reporting Phase Reporting -Results -Statistics Remediation Phase Remediation -Work w/ Rg/Ry Stop Planning *Planning: 13 Aug. 2012 to 30 Aug. 2012 *Organizing: Pre- Audit No+fica+on 30 Aug. 2012 to 30 Oct. 2012 *Organizing (resources): *RFI: 26 Nov. 2012 to 4 Jan. 2012 *Report Results: 5 Nov. 2012 to 9 Nov. 2012 *Audit (includes collection): 7 Jan. 2013 to 29 Mar. 2013 Approximately 15 April 2013 to 19 April 2013 Request for Info (RFI) Audit Phase Repor+ng Phase *Pre-Audit Notice: *Questions/Answers: 1 April 2013 to 12 April 2013 Remediation Remedia+on Efforts: 22 April 2013 to 12 Nov. 2012 to 23 Nov. 2012 * TBD (to be determined) 1 st No;ce 2 nd No;ce 3 rd No;ce Begin End Begin End 18 Sep 11 Oct 2013 1- Oct- 13 14- Oct- 13 4- Nov- 13 11- Nov- 13 2- Dec- 13 7- Mar- 13 10- Mar- 14 24- Mar- 14 25 Mar 5 May 2014 18

Year-2 Audit Program Sample" 19 Registrars! #! Total Selected Registrars" Total Y1 Rollovers" 317" 5" Registires! #! Total Selected Registrars" US" Ireland" Switzerland" 6" 4" 1" 1" Country! Registrars! United States" 185" India" 24" Canada" 11" United Kingdom" 10" Germany" 8" China" 7" Korea (South)" 6" Japan" 5" Spain" 5" Australia" 4" Italy" 4" France" 4" Mexico" 3" Brazil" 3" Sweden" 3" Netherlands" 2" Belgium" 2" Lithuania" 2" Russian 2" Federation" Israel" 2" Back to Top Country! Registrars! Thailand" 1" Finland" 1" Czech Republic" 1" Cayman 1" Islands" Austria" 1" Taiwan" 1" Ghana" 1" Hong Kong" 1" Ireland" 1" Argentina" 1" Singapore" 1" Viet Nam" 1" Kuwait" 1" Latvia" 1" Liechtenstein" 1" Malaysia" 1" Panama" 1" Philippines" 1" Indonesia" 1"

Whois Inaccuracy Improvements! Business Days 60 40 20 0 Started consistent Compliance Process Sep 2012" Sep- 12 Oct- 12 169 45 51 44 34 41 31 31 28 30 34 41 Nov- 12 Dec- 12 Jan- 13 Feb- 13 52 15 Mar- 13 27 5 Apr- 13 17 9 2 2 9 2 9 10 1 10 2 1 May- 13 Jun- 13 Jul- 13 Whois Inaccuracy system & process automation deployed mid-march 2013" Aug- 13 Sep- 13 Oct- 13 Avg TAT Received- Open Avg TAT Received- Closed Average in Business Days of the Turn Around Time: " From received to submitted to Registrar" From received to closed " 20

Pulse Survey Results July Oct 2013! Overall, how do you rate the complaint experience?! 0%" 10%" 20%" 30%" 40%" 50%" 60%" 70%" 80%" 90%" 100%" Registrar" 53%" 37%" 7%" 3%" Reporter" 61%" 28%" 10%" 1%" Very Easy" Moderately Easy" Not at all Easy" Not Applicable" Pulse Survey URL link included in all Closure notification emails to Reporters and Registrars" 21

Web Hits on Compliance Page July Oct 2013" 6,000 5,000 4,000 3,000 2,000 1,000 0 3,843.0 ICANN.ORG FAQs 3,278.0 3,733.0 Sample shows 80% of users are unique month to month 4,820.0 Jul-13 Aug-13 Sep-13 Oct-13 1000 500 336 myicann.org Compliance Metrics 588 424 446 0 Jul-13 Aug-13 Sep-13 Oct-13 22

Complaints per Domain Volume! July October 2013! N. America 100.9M 2,851.003% 754 284 37.7% Europe 23.1M 868.004% 162 106 65.4% Asia/A/P 23.9M 2,732.011% 165 113 68.5% Latin America 1.3M 107.009% 24 16 66.7% Africa 8,325 4.048% 7 1 14.3% LEGEND July 2013 Domain Volume/Million # registrars per region # registrar w/ Complaints # Complaints % Complaints per Domain Volume % registrars with complaints per region Note: # registrars per region data may contain some obsolete registrars but is retained for repor$ng history 23

Registrars Complaint Trend July October 2013" Hundreds 8 6 4 2 0 Hundreds 2 1 0 North America Latin America Thousands 3 2.5 2 1.5 1 Hundreds 5 4 3 2 1 0 Jul- 13 Sep- 13 Europe Aug- 13 Oct- 13 Africa 4 complaints in Oct Hundreds 15 10 Global Complaint Count Trend 1.8 2.0 5 0 Asia/ Australia/ Pacific 1.5 1.8 Jul-13 Aug-13 Sep-13 Oct-13 24

Compliance Operations Scorecard Running Balance: July-Oct 2013! Avg TAT 1st Notice" Registrar TAT" Notice" Avg TAT 2nd Notice" Avg TAT 3rd July-Oct 2013" 11.3" 6.4" 7.6" Avg TAT Open-1st Notice" CC Staff TAT" Avg TAT 2nd WIP" Avg TAT 3rd WIP" Avg TAT Received- Closed" July-Oct 2013" 1.5" 2.5" 6.7" 9.3" Total New Complaints Received!! 7064! Total Prior Months Carryover!! 2262! Total Complaints Received!! 9326! Volume Closed Before 1st Notice" 2816" " Volume Closed Before 2nd Notice" 2971" " Volume Closed Before 3rd Notice" 667" " Volume Closed Before Enforcement 71" WIP" " Volume Closed After Enforcement" 35" " Total Closed!! 6560! Carryover! Volume Open Before 1st Notice Sent" 611" " Volume Open in 1st Notice Sent" 1758" " Volume Open in 2nd Notice Sent" 255" " Volume Open in 3rd Notice Sent" 119" " Volume Open After Enforcement All" 24" " Total Remaining Open (Carryover)!! 2766! Carryover- at end of period! 773 773! Enforcements! Volume Breach! 11! " Volume Suspension" 2" " Volume Termination" 2" " 25

Closure Rate of Complaints KPI July 2013 Oct 2013! 0.8 0.7 0.6 Closure Rate 72% 69% 73% 67% Jul-13 Aug-13 Sep-13 Oct-13 Ø Closure Rate is one of the Key Performance Indicators" Ø KPI is used by compliance to monitor and analyze overall processing performance" Ø Compliance target for FY14 is 55%" Ø Target includes several factors such as:" Complaint volume" Number of staff processing complaints" Turnaround time (Registrar & compliance Staff)" 26

Compliance Performance Measurement! + Improve complaint closure rate by 10% + Improve internal audit performance on the 45 control objectives by 20% + Complete Year-2 Audit Program per schedule + Compliance Readiness for 2013 RAA + Compliance Readiness for new Registry Agreement 27

Addi+onal Resources Learn more about ICANN Compliance" http://www.icann.org/en/resources/compliance " Monthly Updates in 6 UN languages http://www.icann.org/en/resources/compliance/ reports " Compliance Metrics on MyICANN " FAQ and complaint submission page " http://www.icann.org/en/resources/compliance/ complaints " 28 Back to Top

Thank You!!! Any Questions?!

Supporting Slides!

Bulk Whois Inaccuracy Differences! Old Bulk Separate system New Bulk Integrated within consolidated system 2 Automa;c No;ces Within Compliance process and review Data file valida;on Addi;onal valida;on at ;cket crea;on at submission only Data file valida;on Ac;ve domain status Non- duplicate complaint check (45 days) Valid gtld Outside of ;cket process No review of ;cket quality No Terms of Use No abuse penal;es Unlimited ;cket submission One user Bulk ;ckets within same process and queue as single submission Whois inaccuracy complaints (bulk tag for iden;fica;on and metrics) Rejec;on of invalid ;ckets Periodic review/audit of ;ckets Outreach to submisers to improve ;cket quality Mandatory Terms of Use Abuse penal;es include suspension and revoca;on of access - Gradual rollout - Limited to 100 submissions per user per week to ensure quality and scalability - Submission limit will be revisited based upon performance and impact to contracted par;es and ICANN Access applica;on, training & agreeing to Terms of Use. Limited number of users. 31

TERMS OF USE OF ICANN CONTRACTUAL COMPLIANCE BULK WHOIS INACCURACY COMPLAINT TOOL! AGREEMENT BETWEEN USER AND ICANN The ICANN Contractual Compliance Bulk Whois Complaint Submission Tool ( Bulk Tool ) is offered to you condi;oned on your acceptance without modifica;on of the terms and condi;ons herein. Please read the following terms of use and disclaimers carefully before using the Bulk Tool. By accessing or using the Bulk Tool, you agree to the terms and condi;ons, and all applicable laws. If you do not agree to these terms, you will not be allowed to use the Bulk Tool. TERMS AND CONDITIONS 1. The Bulk Tool is subject to ICANN s modifica;on and enhancements, without no;ce as deemed necessary. 2. The Bulk Tool may be suspended by ICANN at any ;me if in its discre;on ICANN deems it necessary. 3. Login informa;on for the Bulk Tool is personal to you, and must not be shared with others. 32

TERMS OF USE OF ICANN CONTRACTUAL COMPLIANCE BULK WHOIS INACCURACY COMPLAINT TOOL! (Continued)! 4. Each user is limited to submilng no more than 100 Whois inaccuracy complaints through the Bulk Tool per calendar week. A calendar week starts on Sunday at 00:00 UTC. Addi;onal submissions beyond 100 per week will be rejected. ICANN in its sole discre;on may modify the submission limit with advance no;ce to the users and registrars. 5. Bulk submissions shall use current Whois data and may only be submised in the data format specified by ICANN. 6. Bulk submissions shall not be used to harass ICANN, any ICANN- accredited registrar, or any domain name registrant or contact. 7. ICANN will review Bulk Tool submissions for validity, and improper ;ckets will be rejected by ICANN. Bulk Tool submissions must contain sufficient informa;on to allow ICANN to validate each complaint independently. Factors to determine validity include, but are not limited to, complaint data quality and contactability (ability to reach Whois contacts). 33

TERMS OF USE OF ICANN CONTRACTUAL COMPLIANCE BULK WHOIS INACCURACY COMPLAINT TOOL! (Continued)! 8. ICANN will conduct periodic reviews or audits of user's Bulk Tool submissions to: (i) determine compliance with these terms and condi;ons; and (ii) improve ;cket validity levels. Users that do not demonstrate improvement for iden;fied issues may have their Bulk Tool user access suspended or revoked. 9. ICANN may suspend or revoke Bulk Tool user access (either permanently or temporarily) for viola;ons of these terms and condi;ons. Any suspension or revoca;on of Bulk Tool user access shall apply to single and mul;ple ( Submit another ) Whois inaccuracy submissions. 10. Bulk Tool users must collaborate with ICANN to submit test data through a test Bulk Tool that conforms to these Terms of Use before being allowed to submit to produc;on Bulk Tool. 11. Any and all informa;on submised to the Bulk Tool can be submised to an ICANN- accredited Registrar or any other party that ICANN may need to no;fy related to a Bulk Tool submission. ICANN will not consider or treat any informa;on submised through the Bulk Tool as confiden;al 12. ICANN retains that right to revise these terms and condi;ons at any ;me without no;ce. 34