Status: Proposed
country: International
Type: Community gTLD, Generic
Category: Industry

More information:

.insurance is a proposed new generic top level domain name (gTLD) to ICANN's New gTLD Program.

Current Applicants[edit | edit source]

  1. fTLD Registry Services LLC a partnership with BITS, the technology policy arm of Financial Services Roundtable, and the American Bankers Association (ABA) [1]
  2. Radix (DotFresh Inc.), a subsidiary of Directi Group that has applied for for 31 domains.[2]
  3. Progressive Casualty Insurance Co.[3]
  4. Donuts (Auburn Park, LLC) one of 307 TLDs the company has applied for.

ABA & BITS Bid (fTLD Registry Services)[edit | edit source]

ABA and BITS confirmed their application for the .insurance and .bank TLDs in a press statement released on May 31, 2012. Craig Schwartz, head of operations for Financial TLD Initiative, said that the partnership aims to "provide the highest security for the millions of customers conducting banking and insurance activities online and to ensure the safety and soundness of the industry." ABA & BITS applications for both domain name strings are supported by a number of financial services organizations including the Australian Bankers’ Association, American Bankers Insurance Association, British Bankers’ Association, European Banking Federation, Independent Community Bankers of America and the the International Banking Federation.[4] The partnership formed the fTLD Registry Services, LLC to manage and operate .insurance and .bank domain name space.[5]

Radix Bid[edit | edit source]

Radix, a newly created subsidiary business of Directi Group also confirmed its application for the .insurance TLD. The .insurance string is one of the 31 gTLDs being applied for by the company with an allocated budget of $30 million. [6] Bhavin Turakhia, CEO of Radix is prepared to face a string contention and an auction for the string. He also expressed that he is open to establish partnerships with other applicants. [7] ARI Registry Services was chosen by Radix to serve as its back-end registry services provider.[8]

References[edit | edit source]