Skip to main content

RegisterFly update: March 10, 2007

ICANN spoke yesterday with Kevin Medina and Mark Klein of RegisterFly.

ICANN asked for greater clarity from RegisterFly about auth-info codes and draw attention to this link to the auth-info codes retrieval process.

RegisterFly indicated that auth-info codes are being distributed to customers via and customer service channels and they claimed that the site is functioning as it should to allow names to be unlocked. ICANN told RegisterFly it will run a test so we can verify that these systems are indeed functioning as advised.

RegisterFly said they would have a developer research and correct the problem registrars and other users are experiencing with port 43 and web-based Whois services. Presently, the RegisterFly Whois server provides no registrant, administrative contact, technical contact, or other registrar-level Whois data, but instead reports only registry-level data. ICANN has told RegisterFly to correct this problem and report back. The failure by RegisterFly to provide Whois service effectively prohibits all registrants of .com and .net names from transferring out, so this needs to be RegisterFly’s highest priority in order to protect the interests of registrants. This must be corrected immediately.

Regarding names registered as a reseller for eNom, RegisterFly confirmed that an exchange of information will take place this Monday, 12 March that will result in access to eNom systems, and enable “automatic” transfer of eNom names.

ICANN insisted upon daily reports indicating the number of transfers. We intend to publish these.

Finally ICANN said it would be referring and monitoring the performance of RegisterFly on handling complaints referred to it and to ICANN about RegisterFly.

It was made clear that it is absolutely imperative that the causes of complaints regarding transfers and auth-codes have to cease immediately. If they do not they will be the subject of further breach notices.


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