Skip to main content
Resources

Contractual Compliance Monthly Update | January 2013

This page is available in:

Table of Contents 1

Presentations and Annual Report Published

Contractual Compliance Participation at the Europe Regional Registry/Registrar Meeting

Two team members presented ICANN's Contractual Compliance Program at the Newcomers session and provided an update on operations and the audit program. Please refer to this link for additional details and the presentations: http://www.icann.org/en/resources/compliance/outreach.

2012 Contractual Compliance Annual Report Is Published

Please refer to this link http://www.icann.org/en/resources/compliance/reports to access the report.

Audit Program Update

The Request for Information (RFI) phase closed on 7 January 2013 for 317 Registrars and six Registry Operators. Ten breach notices were issued to registrars who failed to respond by the deadline. One Registry Operator declined to participate.

ICANN followed up with a "RFI - Audit Program Year 1 Continuous Improvement Survey" to the participants. The objective of the survey is to seek feedback, to measure the satisfaction level, and to determine specific areas for improvement for future RFI phases.

The ICANN Contractual Compliance Audit Program is now in the Audit phase. During this phase, ICANN will review about 20,000 uploaded documents and will issue an Audit Report to each contracted party. A "No Deficiencies" audit report will require no further action. An audit report with deficiencies will require the contracted party to take action; either to cure or to provide a remediation plan. This phase will follow the 1-2-3 notification process.

Year-1 Audit Program Milestone Dates
Request for Info Audit Phase Reporting Phase Remediation
1st
Notice		 2nd
Notice		 3rd
Notice		 Begin End Begin End  
26 Nov. 2012 17 Dec. 2012 28 Dec. 2012 7 Jan. 2013 12 Apr. 2013 15 April 2013 19 April 2013 22 April 2013

Please refer to http://www.icann.org/en/resources/compliance/audits to learn more about this program.

Complaints Handling and Enforcement Summary

Complaints per Cycle January 2013

 

Compliance Performance Results January 2013

 

ENFORCEMENT ACTIVITY for JANUARY 2013
SENT DATE DUE DATE REGISTRAR NOTICE TYPE STATUS FAILURE NOTICE BASIS
11-Jan 1-Feb Power Brand Center Corp. Breach Cured Respond to audits (RAA 3.14)
Cured Maintain and provide communication records (RAA 3.4.2/3)
  Pay accreditation fees (RAA 3.9)
11-Jan 1-Feb Homestead Limited d/b/a Namevault.com Breach   Maintain and provide communication records (RAA 3.4.2/3)
11-Jan 1-Feb Lime Labs LLC Breach   Respond to audits (RAA 3.14)
  Maintain and provide communication records (RAA 3.4.2/3)
11-Jan 1-Feb Central Registrar, Inc. d/b/a Domainmonger.com Breach   Respond to audits (RAA 3.14)
  Maintain and provide communication records (RAA 3.4.2/3)
  Pay accreditation fees (RAA 3.9)
11-Jan 1-Feb Cheapies.com Inc. Breach   Respond to audits (RAA 3.14)
  Maintain and provide communication records (RAA 3.4.2/3)
  Pay accreditation fees (RAA 3.9)
11-Jan 1-Feb Internet NAYANA Inc Breach Cured Maintain and provide communication records (RAA 3.4.2/3)
11-Jan 1-Feb USA Webhost, Inc. Breach Cured Respond to audits (RAA 3.14)
Cured Maintain and provide communication records (RAA 3.4.2/3)
11-Jan 1-Feb R. Lee Chambers Company LLC d/b/a DomainsToBeSeen.com Breach   Respond to audits (RAA 3.14)
11-Jan 1-Feb Mat Bao Trading & Service Company Limited d/b/a Mat Bao Breach Cured Respond to audits (RAA 3.14)
Cured Maintain and provide communication records (RAA 3.4.2/3)
11-Jan 1-Feb Korea Electronic Certification Authority, Inc. Breach Cured Respond to audits (RAA 3.14)
Cured Maintain and provide communication records (RAA 3.4.2/3)
18-Jan 8-Feb Cheapies.com Inc. Breach   Provide communication records (RAA 3.4.3)
  Provide a reasonable opportunity to unlock the domain name
(IRTP 3)
  Provide AuthInfo code (IRTP 5)

Please refer to http://www.icann.org/en/resources/compliance/newsletter for up-to-date information.

1 This update is provided for information purposes only. Please do not rely on the information contained within this update to make conclusions or business decisions.

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."