ARCHIVE
ID Number: G00124889



This research is provided for historical perspective;
portions of this document may not reflect current conditions.






ICANN Domain Transfer Request Policy Puts Owners on Notice
16 November 2004
 
Lydia Leong   Rich Mogull   Ted Chamberlin  

The Internet Corporation for Assigned Names and Numbers (ICANN) has enacted new rules for domain transfer requests. Domain owners must heighten security and account accuracy or risk losing domain ownership.









Browse Topics


Other Options







Contact Gartner






Download Document:

PDF

icann_domain_tr.pdf (34.1KB)

Help with Downloads




News Analysis




Event

On 12 November 2004, ICANN enacted new rules for domain transfers. ICANN will automatically approve domain transfer requests in five days, unless the account owner explicitly denies the request. (Currently, a domain's ownership and nameservers remain unchanged if there is no response to a transfer request.)




Analysis

The new five-day turnaround policy is one of ICANN's many new policies governing inter-registrar domain transfers. The policy aims to ease the process of moving from one registrar to another and increase competition among registrars. Timely transfers benefit businesses, but the new policy also increases the risk of domain hijacking for businesses that fail to maintain accurate registration records.

Recommendations: To reduce the risk of losing ownership, domain administrators should:

  • Use a registrar that offers a "transfer lock" option, and activate the lock. A domain cannot be transferred while locked, even if the owner fails to respond to a transfer request.
  • Provide contact information through role accounts handled by a group of employees, rather than a single employee. (This protects the company against problems caused by employee departures and vacations.) Examples of role account contacts include: e-mail — a "hostmaster" address that goes to a mailing list read by multiple employees; telephone — a shared voicemail box that is checked regularly; fax — a shared fax machine that is checked regularly; and postal — addressed to the IT department.
  • Ensure that domain contact information is correct.
  • Use the strictest level of security and verification offered by the registrar, including cryptographic methods if they are offered.
  • Whenever possible, consolidate registrars and create an internal cross-domain team, with members from the IT, legal and marketing departments, to create and enforce internal domain name registration polices.

Analytical Sources: Lydia Leong, Rich Mogull and Ted Chamberlin, Gartner Research

Recommended Reading and Related Research

(You may need to sign in or be a Gartner client to access the documents referenced in this FirstTake.)









Browse Topics:
 





© 2004 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction and distribution of this publication in any form without prior written permission is forbidden. The conclusions, projections and recommendations represent Gartner's initial analysis. As a result, our positions are subject to refinements or major changes as Gartner analysts gather more information and perform further analysis. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.




Resource Id: 461432