Steve and BC members, We have more data ron abuse complaints addressed under RAA 3.18 that we thought might be of interest: From January 2014 to September 2019, ICANN Compliance received 3,704 abuse report handling complaints. This number includes complaints concerning the registrar’s alleged failure to investigate and respond to an abuse report, to display abuse contact data, complaints that did not fall within ICANN’s contractual scope (e.g. involving ccTLD domain names, requesting ICANN to directly suspend a domain name or remove content from a website, or complaints about a third party over which ICANN had no contractual authority), and complaints deemed invalid because they were duplicates of ongoing cases or for which the complainant failed to provide evidence to ICANN confirming that an abuse report was ever submitted to the relevant registrar. From January 2014 to September 2019, ICANN Compliance sent 1,257 first, 339 second and 63 third notices/inquires to the relevant registrars on registrar abuse report handling complaints. These numbers do not include follow-up communications that ICANN Compliance sent in between notices/inquires requesting clarification or additional evidence following a response from the relevant registrar. Of the notices above, the following seven formal notices of breach were issued, with one escalating to termination of the registrar’s accreditation with ICANN: 1 October 2014: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-matuzich-01oct...> (Homestead Limited dba Namevault.com<http://namevault.com/>) 10 October 2014: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-cao-10oct14-en...> (Todaynic.com<http://todaynic.com/>, Inc.) 14 November 2014: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-lam-14nov14-en...> (IP Mirror Pte Ltd dba IP MIRROR) 9 January 2015: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-jaiswal-09jan1...> (Netlynx Inc.) 22 January 2015: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-warmuz-22jan15...> (Above.com<http://above.com/> Pty Ltd.) 22 January 2015: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/en/system/files/correspondence/serad-to-golding-22jan1...> (Astutium Limited) 13 December 2016: ICANN Sends Notice of Breach to Registrar<https://www.icann.org/uploads/compliance_notice/attachment/891/serad-to-hans...> (Nanjing Imperiosus Technology Co. Ltd.) Escalated to termination of the registrar’s accreditation with ICANN. Of those cases that did not result in breaches (the vast majority across all complaint types), approximately 34% of the cases resulted in the registrar suspending the domain name(s) involved in the report, in accordance with the registrar’s own abuse policies. In other cases, the registrar took other measures in accordance with its own abuse policies (e.g. providing web-hosting information to the complainant for reporting the abusive content to the entity hosting the allegedly abusive content or terminating the agreement between the registrar and registrant by allowing the transfer to a different registrar.) In the cases of complaints that were not forwarded to the registrar, ICANN Compliance educated complainants on ICANN’s scope and provided alternatives including help identifying a more appropriate entity to contact. ICANN Compliance also requested the reporter to contact ICANN again if additional assistance was needed after contacting the registrar, where applicable. For those that did not reply confirming that assistance was still needed, the complaints were closed. ICANN has a dedicated public page for Contractual Compliance reporting<https://features.icann.org/compliance>. This page provides three types of data to the ICANN Community. The first section, referred to as “Metrics and Dashboards<https://features.icann.org/compliance/dashboard/report-list>”, provides monthly, quarterly and annual data. The second section, referred to as “Contractual Compliance Metrics for a rolling 13-month period”, provides ten different types of reports for the prior 13-month period. The third section, referred to as “Additional Contractual Compliance related data”, provides links to the metrics and data specifically requested by different working groups or review teams. Additionally, all formal enforcement notices and status are published athttps://www.icann.org/compliance/notices Hope this information is helpful. Please let me know if you have any questions. Thanks. Best, Jamie On Nov 7, 2019, at 09:56, Steve DelBianco <sdelbianco@netchoice.org> wrote: This week in Montreal, we met with ICANN Compliance chief Jamie Hedlund (copied here). On Tuesday, Jamie shared the 2 breach notices issued for violations of Public Interest Commitments in Spec 11 in the Registry Agreement, pertaining to the transparency requirement in 3c. Yesterday, I asked Jamie to share breach notices based on 3.18.1 of the Registrar Accreditation Agreement (RAA): 3.18 Registrar's Abuse Contact and Duty to Investigate Reports of Abuse. 3.18.1 Registrar shall maintain an abuse contact to receive reports of abuse involving Registered Names sponsored by Registrar, including reports of Illegal Activity. Registrar shall publish an email address to receive such reports on the home page of Registrar's website (or in another standardized place that may be designated by ICANN from time to time). Registrar shall take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse. Below is Jamie’s quick response (Thanks, Jamie). ICANN Compliance issued a notice of breach [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> and was subsequently escalated to termination [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> of the registrar’s accreditation for failure to demonstrate compliance in response to a notice involving the registrar’s handling of an abuse report. There was a second breach based on Section 3.18 for failure to investigate and respond to abuse reports: https://www.icann.org/en/system/files/correspondence/serad-to-golding-22jan1... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...> ICANN Compliance has issued several notices that included violations of the obligation to display abuse contact information under Section 3.18 of the RAA; a few examples below (their status, including whether they were cured, or escalated to suspension or termination is listed in the Compliance enforcement page at https://www.icann.org/compliance/notices [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_complianc...>) https://www.icann.org/uploads/compliance_notice/attachment/981/serad-to-677-... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/923/serad-to-nico... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/901/serad-to-orza... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1125/hedlund-to-b... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1033/serad-to-loi... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1107/serad-to-zho... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1055/serad-to-pel... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1047/serad-to-wan... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1037/serad-to-zho... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1035/serad-to-del... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/1021/serad-to-kan... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/979/serad-to-240-... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/953/serad-to-lope... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/945/serad-to-boom... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/931/serad-to-venk... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/923/serad-to-nico... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/913/serad-to-wess... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/907/serad-to-vill... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> https://www.icann.org/uploads/compliance_notice/attachment/903/serad-to-gray... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_c...> The above does not reflect the number of abuse complaints processed by ICANN Compliance that did not result in breaches (the vast majority across all complaint types). In these cases, the registrar demonstrated having taken reasonable and prompt steps to investigate and respond appropriately to the abuse report in accordance with the registrar’s own abuse policies by, for example, suspending the domain name; contacting the registrant of the domain name(s) subject to the abuse report and asking for and obtaining evidence (e.g. licenses for pharmaceutical-related abuse reports); providing web-hosting information about the subject domain name(s) to the complainant for reporting the abusive content to the entity hosting the allegedly abusive content or terminating the agreement between the registrar and registrant by allowing the transfer to a different registrar. Hope this is helpful. Thanks. Best, Jamie