• Documents
•  

Editorial note: Although Dotster responded in less than three days to ICANN's original request for answers to its list of questions sent out on 18 January 2005, the registrar requested an opportunity to slightly modify its response before publicly posting it on the ICANN website. The date of this document reflects the subsequent modified response and should not in any way suggest that Dotster was slow in responding to ICANN's original query. No substantive changes were made to the original response.

Date: Thursday, January 27, 2005
From: Ravi Puri
To: Tim Cole
Subject: RE: ICANN Follow-up on PANIX.COM Hijacking

Dear Tim,

We have updated our answers below with more clarification.

We would approve the answers below to be posted with the official ICANN response.

We hope that helps!

Sincerely,

Ravi Puri

1. Under the Registrar Accreditation Agreement and the new ICANN transfer policy, registrars are obligated to keep copies of records relating to transfers:

a) Please provide ICANN with the copy of the Whois data for PANIX.COM that Dotster maintained prior to the initiation of the transfer.

Ownership Information
Panix Hostmaster
Public Access Networks Corp.
15 West 18th Street, 5th floor
New York NY 10011
US
212-741-4400 212-741-5311
hostmaster@panix.com

Admin Contact Information
Panix Hostmaster
Public Access Networks Corp.
15 West 18th Street, 5th floor
New York NY 10011
US
212-741-4400 212-741-5311
hostmaster@panix.com

Billing Contact Information
Panix Hostmaster
Public Access Networks Corp.
15 West 18th Street, 5th floor
New York NY 10011
US
212-741-4400 212-741-5311
hostmaster@panix.com

Tech Contact Information
Panix Hostmaster
Public Access Networks Corp.
15 West 18th Street, 5th floor
New York NY 10011
US
212-741-4400 212-741-5311
hostmaster@panix.com

b) Were there any changes to the Whois data for this name in the 30 days preceding the transfer? If so, please provide details.

- No

c) Was PANIX.COM under registrar-lock at any time prior to the transfer request? If so, when was it unlocked?

- No

2. Under the transfer policy, registries are obligated to provide notification to the registrar of record upon receipt of a transfer request.

a) Did Dotster receive notice of the transfer request?

- Yes

b) If so, when was the notice of the transfer provided to Dotster?

- 01/08/2005 05:40 PM PST

3. The transfer policy provides that the "Registrar of Record can choose independently to confirm the intent of the Registered Name Holder when a notice of a pending transfer is received from the Registry."

a) Did Dotster communicate with the registrant (or administrative contact) in an attempt to confirm the registrant's intent to transfer the name to Melbourne IT?

- No, in accordance with ICANN's new policy, we relied on the approval given to the gaining registrar being valid.

b) If so, when and how was the communication sent? Please provide a copy of the request for confirmation.

- NA

c) If Dotster did send notice of the transfer to the registrant, did the registrant reply? Please provide a copy of any reply received.

- NA

4. The transfer policy provides for a period of five calendar days for the registrar of record to respond to a notification from the registry regarding a transfer request. Did Dotster allow the name to transfer by taking no action during the transfer pending period, or did Dotster affirmatively approve the transfer request prior to the conclusion of the transfer pending period? If so, when?

- An Auto-Acknowledgement Transfer took place with Dotster taking no action during the transfer pending period.