Changes

Jump to navigation Jump to search
442 bytes added ,  8 years ago
no edit summary
Line 16: Line 16:  
[[Category:TLDs with Registry Agreements|tel]]
 
[[Category:TLDs with Registry Agreements|tel]]
   −
 
+
'''.TEL''' was launched in 2005 by the registry operator [[TelNic]].<ref>http://telnic.tel/</ref> .TEL was envisioned as a worldwide contact directory. For instance, if you had the TEL domain of a person or company, you could always look up their current email address or phone number. <ref>http://telnic.org/aboutus.html</ref>
'''.TEL''' tld was launched in 2005 by the registry operator [[Telnic]].<ref>http://telnic.tel/</ref> .TEL was envisioned as a worldwide contact directory. For instance, if you had the TEL domain of a person or company, you could always look up their current email address or phone number. <ref>http://telnic.org/aboutus.html</ref>
      
==Name Servers & Telhost==
 
==Name Servers & Telhost==
Line 25: Line 24:  
Instead .TEL domains had to be pointed to the Telhost server provided by the registry operator. The Telhost server displayed the contact information for the registrant. The Telhost server had a password protected web based interface for registrants to input and update their contact information.
 
Instead .TEL domains had to be pointed to the Telhost server provided by the registry operator. The Telhost server displayed the contact information for the registrant. The Telhost server had a password protected web based interface for registrants to input and update their contact information.
   −
[include http://telnic.tel domain screenshot here]
+
Telhost returned contact information in a well-defined format, so that an individual’s address book could automatically retrieve the latest contact information for someone based on their TEL domain. In theory you could call someone just by entering their TEL domain name instead of their phone number. In practice no major phone manufacturers supported TEL domain dialing. <ref>[https://teltalkorg.wordpress.com/2012/12/13/the-key-to-success-for-tel/], The key to success for .tel</ref>
 
  −
Telhost returned contact information in a well-defined format, so that an individual’s address book could automatically retrieve the latest contact information for someone based on their TEL domain. In practice no major address book provider integrated with the Telhost server.
      
==Reception by Domain Investors==
 
==Reception by Domain Investors==
   −
Domain investors provide an aftermarket and informal sales force for TLDs. They also drive much of the initial launch volume. For the most part, domain investors did not buy .TEL domains. At the time, domain parking monetization was in full swing, and not being able to park a TEL domain was a major disadvantage for domain investors.
+
Domain investors provide an aftermarket and informal sales force for TLDs. They also drive much of the initial launch volume. For the most part, domain investors did not buy .TEL domains. At the time, domain parking monetization was in full swing, and not being able to park a TEL domain was a major disadvantage for domain investors.<ref>[http://domaingang.com/domain-news/telnic-adds-insult-to-injury-launching-idn-tel-domains/], Telnic adds insult to injury: Launching IDN .tel domains</ref>
   −
Reception by Domain Registrars
+
==Reception by Domain Registrars==
    
Registrars that wanted to launch TEL domains were required to modify their control panels so that .TEL domains could not have their name servers set. Furthermore, supporting Telhost required that registrars integrate with the Telhost API. The Telhost API automated the creation of Telhost accounts for registrants.
 
Registrars that wanted to launch TEL domains were required to modify their control panels so that .TEL domains could not have their name servers set. Furthermore, supporting Telhost required that registrars integrate with the Telhost API. The Telhost API automated the creation of Telhost accounts for registrants.
   −
Many registrars, most notably Godaddy, decided the additional integration costs to support .TEL was not worth the potential revenue.
+
Many registrars, most notably Godaddy, decided the additional integration costs to support .TEL was not worth the potential revenue.<ref>[http://domainnamewire.com/2009/02/03/tel-landrush-what-you-need-to-know/], .Tel "Landrush": What You Need to Know.</ref>
    
==TLD Zone==
 
==TLD Zone==
staff
8,858

edits

Navigation menu