Skip to main content

Complaints Report

ICANN Complaints Office: In-Scope Complaint Submissions

Complaints Office Semi-Annual Report for 15 March 2017 – 31 December 2017
Click Here to Download

(updated as of 09 March 2018)

Complaint Number Date Received Status Status Date Sender Sender Organization Brief Description Complaint Response
C-2017-00001 10-May-2017 Closed 2-Jun-2017 Redacted at Request of Complainant Hest Wind Power Limited Request for the ICANN org to remove the 60-day lock required by ICANN Transfer Policy C-2017-00001 - Complaint - Hest Wind Power Limited [PDF, 708 KB] C-2017-00001 - ICANN Response - Hest Wind Limited [PDF, 180 KB]
C-2017-00002 24-May-2017 Closed 4-Aug-2017 Spencer James LifeJourney Church Request regarding the enforcement of email and software systems to recognize new gTLDs (Universal Acceptance) C-2017-00002 - Complaint - LifeJourney Church [PDF, 29 KB] C-2017-00002 - ICANN Response - LifeJourney Church [PDF, 130 KB]
C-2017-00003 24-May-2017 Closed 16-Aug-2017 James Danforth None provided Request to consider modifying Domain Name System architecture to address concerns regarding domain name visisiblity in search engines C-2017-00003 - Complaint - James Danforth [PDF, 83 KB] C-2017-00003 - ICANN Response - James Danforth [PDF, 95 KB]
C-2017-00004 19-May-2017 Closed 24-May-2017 Ali Ahmad Jabbar None provided Unable to submit application for NextGen program C-2017-00004 - Complaint - Ali Ahmad Jabbar [PDF, 25 KB] C-2017-00004 - ICANN Response - Ali Ahmad Jabbar [PDF, 25 KB]
C-2017-00005 16-May-2017 Closed 9-Jun-2017 John Poole None provided Request for outstanding response to submitted questions C-2017-00005 Complaint - John Poole [PDF, 46 KB] C-2017-00005 - ICANN Response - John Poole [PDF, 88 KB]
C-2017-00006 30-May-2017 Respond 27-Sep-2017 John Poole None provided Unable to submit comments to an open Public Comment Forum C-2017-00006 - Complaint - John Poole [PDF, 24 KB]

C-2017-00006 - John Poole - Initial Response [PDF, 87 KB]

C-2017-00006 - ICANN Response - John Poole [PDF, 135 KB]

C-2017-00007 5-Jun-2017 Closed 6-Sep-2017 Graeme Bunton Registrar Stakeholder Group The ICANN org missed its processing deadline for registrars to review a Registry-Registrar Agreement amendment C-2017-00007 - Complaint - Graeme Bunton [PDF, 1.09 MB] C-2017-00007 - ICANN Response - Graeme Bunton [PDF, 158 KB]
C-2017-00008 27-Jun-2017 Closed 20-Sep-2017 Martin Calder None provided Domain name suspension related to Whois Accuracy Reporting System results C-2017-00008 - Complaint - Martin Calder [PDF, 42 KB] C-2017-00008 - ICANN Response - Martin Calder [PDF, 484 KB]
C-2017-00009 26-Jun-2017 Closed 15-Aug-2017 Jason Wood None provided Domain name suspension when Whois contact information has not been verified C-2017-00009 - Complaint - Wood [PDF, 693 KB] C-2017-00009 - ICANN Response - Wood [PDF, 128 KB]
C-2017-00010 10-Jul-2017 Closed 14-Sep-2017 Alberto Urra None provided Request to remove profile from website C-2017-00010 - Complaint - Alberto Urra [PDF, 304 KB] C-2017-00010 - ICANN Response - Alberto Urra [PDF, 91 KB]
C-2017-00011 10-Jul-2017 Closed 22-Sep-2017 Sophia Echavarria None provided Unable to submit job application via C-2017-00011 - Complaint - Sophia Echavarria [PDF, 20 KB] C-2017-00011 - ICANN Response - Sophia Echavarria [PDF, 94 KB]
C-2017-00012 13-Jul-2017 Closed 1-Sep-2017 Kinfe Michael Yilma None provided Request to remove Curriculum Vitae from C-2017-00012 - Complaint - Kinfe Michael Yilma [PDF, 20 KB] C-2017-00012 - ICANN Response - Kinfe Michael Yilma [PDF, 97 KB]
C-2017-00013 4-Jul-2017 Closed 2-Oct-2017 Steven Klock None provided Request for ICANN to take action against registrar practices C-2017-00013 - Complaint - Steven Klock [PDF, 24 KB] C-2017-00013 - ICANN Response - Steven Klock [PDF, 131 KB]
C-2017-00014 15-Jul-2017 Closed 20-Nov-2017 Tarun Mehta None provided Request for ICANN to compel registrar to renew or reinstate a domain name C-2017-00014 - Complaint - Tarun Mehta [PDF, 22 KB] C-2017-00014 - ICANN Response - Tarun Mehta [PDF, 132 KB]
C-2017-00015 28-Aug-2017 Closed 2-Oct-2017 John Poole None provided Request for ICANN to publish content from ICANN59 C-2017-00015 - Complaint - John Poole [PDF, 23 KB] C-2017-00015 - ICANN Response - John Poole [PDF, 93 KB]
C-2017-00016 4-Aug-2017 Respond 25-Oct-2017 Ashley Roberts Valideus Ongoing issues regarding contracted party invoices C-2017-00016 - Complaint - Valideus [PDF, 2.32 MB]

C-2017-00016 - ICANN Initial Response - Valideus [PDF, 89.4 KB]

C-2017-00016 - ICANN Response - Valideus [PDF, 480 KB]

C-2017-00017 28-Jul-2017 Closed 14-Nov-2017 Lorenzo Muscoso None provided Request for ICANN to assist with domain name renewal C-2017-00017 - Complaint - Lorenzo Muscoso [PDF, 65 KB] C-2017-00017 - ICANN Response - Lorenzo Muscoso [PDF, 628 KB]
C-2017-00018 15-Sep-2017 Closed 4-Dec-2017 John Poole None provided Unable to access ICANN webinar recordings C-2017-00018 - Complaint - John Poole [PDF, 68 KB] C-2017-00018 - ICANN Response - John Poole [PDF, 67 KB]
C-2017-00019 2-Oct-2017 Respond 18-Oct-2017 Crystal Ondo Donuts Inc Lack of communication between ICANN org and registry operators and textual issues regarding Naming Services Portal Terms of Use C-2017-00019 - Complaint - Crystal Ondo [PDF, 22 KB]  
C-2017-00020 31-Oct-2017 Respond 28-Nov-2017 John Poole None provided Unable to access ICANN60 webinar recordings C-2017-00020 - Complaint - John Poole [PDF, 64 KB]  
C-2017-00021 11-Dec-2017 Evaluate & Consider 13-Dec-2017 Redacted None provided Level of service received from ICANN's Global Support Center C-2017-00021 - Explanatory Memorandum [PDF, 112 KB]  
C-2017-00022 20-Dec-2017 Evaluate & Consider 8-Jan-2018 Redacted None provided Level of service received from ICANN's Global Support Center C-2017-00022 - Explanatory Memorandum [PDF, 68 KB] Not applicable
C-2018-00001 24-Jan-2018 Evaluate & Consider 26-Jan-2018 Gary Cornell None provided Issue with handling of Contractual Compliance ticket C-2018-00001 - Complaint - Gary Cornell [PDF, 19.5 KB]  
C-2018-00002 17-Feb-2018 Evaluate & Consider 1-Mar-2018 Alan Anderson None provided Request for the ICANN org to remove the 60-day lock required by ICANN Transfer Policy C-2018-00002 - Complaint - Alan Anderson [PDF, 46 KB]  
C-2018-00003 22-Feb-2018 Evaluate & Consider 28-Feb-2018 John Poole None provided Request for answers to outstanding ICANN Form 990 questions C-2018-00003 - Complaint - John Poole [PDF, 53 KB]  

ICANN Complaints Office: Other Submissions

(updated as of 28 February 2018)

In addition to in-scope complaints, the Complaints Office received other submissions. Other submissions fall under three primary categories. Below is a list of categories, how they are handled by the Complaints Office, and the number received/by month for each type.

  1. Other Complaints Process: The submission belongs to another complaints process such as Contractual Compliance or Accountability Mechanisms. These submissions are provided with guidance and referred to the appropriate complaints mechanism;
  2. Inquiry: The submission is an inquiry regarding the complaints process. These submissions receive guidance regarding the complaints process and are cataloged for reference should a complaint be submitted.
  3. Blank: The submission was blank. These submissions receive a request to submit a complete complaint.
Type Quantity
Other Complaints Process:          
- Accountability Mechanisms 2 - -   0
- ccTLD 35 6 12   18
- Compliance 410 48 40   88
- Correspondence 3 - -   0
- Global Support Center
(CYTD-2017 only
includes CM11 & CM12)
31 26 13   39
- Legal 1 - -   0
- Out of ICANN's Scope 307 74 66   140
- Inquiry re: Complaints Process 13 1 1   2
- Blank Complaint Submission 34 5 8   13
Totals: 836 160 140   300
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"""" is not an IDN."