en

Bulk Transfer of DNGLOBE Domains to Paknic

1 March 2010

ICANN has authorized a bulk transfer of DNGLOBE LLC's gTLD domain names to Paknic (Private) Limited, due to a compliance action taken by ICANN that resulted in the de-accreditation of registrar DNGLOBE.

The affected gTLD registries have taken steps to effect the bulk transfers. Former registrant-customers of DNGLOBE should soon receive notices of the transfer from Paknic. Customer questions about the transfer should be directed to Paknic, using the contact details provided below. Additional information about this bulk transfer of DNGLOBE's domain names is also provided below.

FAQs

Q. Why was this transfer authorized by ICANN?

A. DNGLOBE's Registrar Accreditation Agreement (RAA) was terminated by ICANN because of DNGLOBE's failure to comply with the requirements of the RAA. (The notice of termination is posted at http://www.icann.org/correspondence/pritz-to-smirnoff-05feb10-en.pdf [PDF, 1.85 MB]). As a result, DNGLOBE is no longer permitted to register or manage gTLD registrations.

Q. How was the gaining registrar selected?

A. In accordance with ICANN's De-Accredited Registrar Transition Procedure (see http://www.icann.org/en/processes/registrars/de-accredited-registrar-transition-procedure-01oct08.pdf [PDF, 119 KB]), ICANN initiated a Request for Expressions of Interest to identify a new ICANN-accredited registrar to manage the registrations formerly managed by DNGLOBE. ICANN received 18 expressions of interest from registrars in response to the RFI. Through the procedure, ICANN selected Paknic (Private) Limited to receive the bulk transfer from DNGLOBE.

Q. Will Paknic attempt to contact the affected registrants? What should current/former DNGLOBE customers do?

A. Former customers of DNGLOBE should receive a notice of the transfer and instructions for continued management of their names from Paknic. Affected customers who do not receive notices from Paknic should check the web page prepared by Paknic for this bulk transfer: http://www.paknic.com/dnglobe/ or, contact Paknic directly, at:

Telephone:

+1-800-786-5171 (Toll Free)
+1-732-658-5636
+1-732-297-8908
Fax:
+1-732-297-8906 (fax)
Email:  support@paknic.com




Web: http://www.paknic.com/dnglobe/

Q. Do registrants have to pay a fee for the bulk transfer?

A. No, there is no cost to registrants for the bulk transfer. Unlike a normal inter-registrar transfer, the registration terms will not be extended by a year. Accordingly, it is important to contact Paknic if your registration will expire soon in order to maintain your registration.

Q. Why do former DNGLOBE customers need to contact Paknic?

A. DNGLOBE did not forward billing information to Paknic. Accordingly, all registrants must provide updated billing information or transfer their names to other registrars.

Q. What if former DNGLOBE customers want to use a different registrar?

A. Registrants will continue to be able to transfer their registrations to other registrars under the Inter-Registrar Transfer Policy (see http://www.icann.org/en/transfers/). Note that Paknic may deny transfers for the first 60 days following the bulk transfer, at its discretion. This 60-day period is permissible under the Inter-Registrar Transfer Policy, and is intended to help protect registrants. The registrant should renew names that will expire during the first 60 days following the transfer to Packnic by contacting Paknic at:

Telephone:

+1-800-786-5171 (Toll Free)
+1-732-658-5636
+1-732-297-8908
Fax:
+1-732-297-8906 (fax)
Email:  support@paknic.com




Web: http://www.paknic.com/dnglobe/

Q. How will DNGLOBE customers know if a message purportedly from Paknic is legitimate?

A. The message from Paknic should direct you to their website hosted at paknic.com or refer you to other contact information provided above. If you believe a message purportedly from Paknic is not legitimate, you should navigate to their web page directly, at http://www.paknic.com/dnglobe/. For general advice about avoiding phishing email messages, you may also wish to refer to the materials prepared by the Anti-Phishing Working Group (see http://www.antiphishing.org/consumer_recs.html).