.travel: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = TrallianceLogo.gif | |logo = TrallianceLogo.gif | ||
|status = Active | |||
|manager = [[Tralliance]] | |manager = [[Tralliance]] | ||
|country = | |country = Internatonal | ||
|stringcontention = | |stringcontention = | ||
|registryprovider = Tralliance | |registryprovider = Tralliance | ||
| Line 22: | Line 23: | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[category: TLD]] | |||
[[Category:TLDs with Registry Agreements|travel]] | |||
Latest revision as of 21:30, 10 October 2013
 | |
| Status: | Active |
| country: | Internatonal |
| Manager: | Tralliance |
| Registry Provider: | Tralliance |
| Date Implemented: | May 5, 2005 |
| Type: | sTLD |
More information: 
| |
.travel is an sTLD meant exclusively for usage by organizations in the travel and tourism industries. It is managed by Tralliance.[1]
ICANN signed a contract with Tralliance on May 5, 2005 to operate .travel. The operating procedures and policies for .travel are different from those of all other current TLDs.[2]
Requirements
Tralliance requires that, when a .travel domain name is registered, a website with relevant content must be put up within one year of registration.
Registrants must be verified participants in the travel industry. This can include anything from airlines, to public attractions, to ferries, restaurants, bed & breakfast houses, and more.[3]