Return to New TLD Agreements Forum - Message Thread - FAQ

Username: EasyTech2
Date/Time: Fri, March 1, 2002 at 10:33 PM GMT
Browser: Microsoft Internet Explorer V6.0 using Windows 98
Score: 5
Subject: reply


""        "If ICANN would be really so dump and would introduce another .shop version it wouldn't be that bad for Think of the additional exposore for the .shop TLD. .shop domain owners would get ca. 15-20% of the traffic of the ICANN .shop Domain... and if you have good ones... As a result this would drive more traffic to New.nets .shop domain than present."

Except now isn't supposedly getting 100 percent of the .shop traffic?""
--> 100% traffic of low traffic
with a dublicate .shop TLD by ICANN 15-20% of higher traffic
To date is the registry and the only registrar of its domains. Now imagine if ICANN would introduce its own .shopm and VeriSign with its reseller forces would offer this new .shop TLD. --> more marketing, more exposure, more registrations, more sites with content --> increased traffic under the .shop TLD. this 15-20% would be more than the actual 100%

""Thanks for the reply.  You would appear to suggest that a strongly-rooted alternate TLD would be off-limits to ICANN.  Dot-biz showed that wasn't so, although I can't attest to its original 'strength'.""
--> ARNIs Dot-biz runs in alternate roots. runs within the "ICANN Root" under the .net TLD and runs above the ICANN Root. Again: That what you type in your browser bar would be altered by the Plug-In before a DNS query is started. Completely different to ARNI.
But one is evident: If Microsoft only would they could introduce every TLD they want (with instant 90% visibility through IE). Until now their only "TLDs" are Realnames Keywords (forget keywords).

""If what you are saying is true, then ARNI should be experiencing a 15-20 percent increase in traffic, what with the increased ICANN .biz visibility and all.""
--> I wrote an e-mail to the registrant of the domain from ARNI to ask him this question but he never replied.


Message Thread:

Privacy Policy | Terms of Service | Cookies Policy