Skip to main content

Welcome to the new! Learn more, and send us your feedback. Dismiss


Monthly Registry Reports

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

For contractual reasons, registry Report monthly reports are withheld until three months after the end of the month to which the report relates.

Commencing with the January 2009 reports, the Report monthly report is posted as a PDF and the registrar trans-csv report as a CSV, XLS or PDF as provided by the Registry.


  1. On 5 May 2010, VeriSign informed ICANN there was an issue in the numbers for some of the sections in the monthly reports for October 2008 through December 2009 for .name and requested ICANN publish restated versions of the reports. Sections affected by the issue were: Section 2, Service Level Agreement Performance, specifically Check Domain Average and Add Domain Average numbers; Section 6, Total Number of Transactions by Subcategory by Month; and Section 7, Daily Transaction Range. At no time did any of the Service Level Agreement (SLA) performance metrics exceed their SLA requirements. In addition, the per registrar activity reports were not impacted so there are no financial implications as a result of these revisions.
  2. On 20 August 2010, Employ Media informed ICANN about issues in seven of the .jobs per registrar activity reports provided to ICANN during the period April 2009 and May 2010. The issues were in the following three areas: incorrect IANA ID number, Employ Media listed as a registrar, and the transposition of figures reported for the domains-deleted-grace and domains-deleted-nograce columns. Any financial implications (e.g., fees paid by registrars to ICANN) that might have resulted from the issues have been rectified by Employ Media.
  3. On 24 December 2012, ICANN was notified by the registry operator about an error in the June, July, August and September 2012 .pro reports. All four reports incorrectly showed registrar Meshdigital with id 1626, when it should have been 1390.
  4. On 28 January 2013, the registry operator of .post provided updated reports for August and September 2012.
  5. On 7 October 2013, the registry operator of .com, and .net provided updated reports for June 2013.
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."