.travel: Difference between revisions
m Text replacement - "|type" to "|tld_type" Tags: Mobile edit Mobile web edit |
m Updated {{TLD}} template to latest standards [Brand gTLD Update] Tag: Reverted |
||
| Line 1: | Line 1: | ||
{{TLD | {{TLD| | ||
| | |country = | ||
|country | |||
|implemented = July 27, 2005 | |implemented = July 27, 2005 | ||
|registry | |introduced = | ||
|website | |logo = TrallianceLogo.gif | ||
|registry = Dog Beach, LLC | |||
|tld_status = Active | |||
|tld_subtype = brand | |||
|tld_type = gTLD | |||
|website = https://www.identity.digital/ | |||
}} | }} | ||
Revision as of 07:41, 10 May 2025
| gTLD | |
|---|---|
| |
| Type | gTLD |
| Subtype | dotBrand |
| Status | Active |
| Implemented | July 27, 2005 |
| Registry | Dog Beach, LLC |
| Websites | |
.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[edit | edit source]
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]