Revision as of 18:04, 18 January 2017 (view source) WikiAdmin (Talk | contribs) (updated to reflect new policy changes as of Dec 2016 (removal of some requirements)) ← Older edit		Latest revision as of 13:45, 30 August 2021 (view source) WikiAdmin (Talk | contribs)
(16 intermediate revisions by 2 users not shown)
Line 5:		Line 5:
	| tld type = Generic		| tld type = Generic
	| category = Hospitality/Travel		| category = Hospitality/Travel
−	| registry = Tralliance	+	| registry = Donuts
	| idn capable = No		| idn capable = No
	| webpage = [https://www.hexonet.net/domain-name/travel Register .TRAVEL]		| webpage = [https://www.hexonet.net/domain-name/travel Register .TRAVEL]
	}}		}}
−	{{#repositoryinfo:  TRAVEL-LIVE-1API | travel }}	+	{{#repositoryinfo:  DONUTS-LIVE-1API | travel }}
	{{Sidebar}}		{{Sidebar}}
	<div style="font-size: 250%;">'''.TRAVEL'''</div><br/>		<div style="font-size: 250%;">'''.TRAVEL'''</div><br/>
Line 85:		Line 85:
	nameserver1 = (NAMESERVER)		nameserver1 = (NAMESERVER)
	x-travel-uin = <TRAVEL UIN>		x-travel-uin = <TRAVEL UIN>
		+	x-travel-industry = 1
	</pre>		</pre>
Line 101:		Line 102:
	auth = <TEXT> | <NULL>		auth = <TEXT> | <NULL>
	action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER		action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
−	x-travel-uin = <TRAVEL UIN>
	</pre>		</pre>
Line 134:		Line 134:
	=== Ownerchange ===		=== Ownerchange ===
	{{#var:TRADESENTENCE}}		{{#var:TRADESENTENCE}}
−	<span class="label label-important">REQUIRED</span>
−	<pre>
−	X-TRAVEL-UIN = <TRAVEL UIN>
−	</pre>
	= TLD specific =		= TLD specific =
	=== Registration ===		=== Registration ===
−	In order to register .TRAVEL domains, the registrant has to provide a UIN "Unique Identification Number". The UIN may be obtained by the registrant immediately by providing them with the following link: http://www.travel.travel/obtain-uin/.	+
		+	In order to register .TRAVEL domains, use the flag X-TRAVEL-INDUSTRY with the value 1, which means that the registrant acknowledges a relationship to the travel industry. By proceeding with their registration, the registrant acknowledges that they are engaged in or plan to engage in activities related to travel.
	<pre>		<pre>
−	X-TRAVEL-UIN = <TRAVEL UIN>	+	X-TRAVEL-INDUSTRY = 1
	</pre>		</pre>
		+
		+	'''Please note that UINs will be deprecated in September 2018. You are encouraged to begin using the X-TRAVEL-INDUSTRY flag instead.'''
	=== Domain Limitations and Requirements ===		=== Domain Limitations and Requirements ===
−	<br>	+	.TRAVEL domain names are available to everyone who provides or plans to provide services, products, or content related to travel. New travel startups are welcome, and that includes every new travel content provider.
−	{{warnbox | .TRAVEL domain names are available to everyone who provides or plans to provide services, products or content in or to the travel industry. New travel startups are welcome, and that includes every new travel content provider.	+
−	The following list, which is non-exhaustive and provided solely for illustrative purposes, contains sectors that are identified to be within the travel industry and which are eligible for registration:	+	The following list, which is ''non-exhaustive'' and provided solely for illustrative purposes, contains example areas where a .TRAVEL domain would help you stand out:
	* Airlines		* Airlines
Line 169:		Line 167:
	* Tour Operators		* Tour Operators
	* Travel Agents		* Travel Agents
		+	* Travel Bloggers
	* Travel Media		* Travel Media
	* Travel-Consumer and Market Research Organizations		* Travel-Consumer and Market Research Organizations
Line 177:		Line 176:
	* Travel technology providers		* Travel technology providers
	* Travel media providers		* Travel media providers
−	}}	+
	= Addons =		= Addons =

---

Latest revision as of 13:45, 30 August 2021

.TRAVEL is considered a sponsored Top-Level Domain for operators of the travel and tourism industry.

Introduced	2005
TLD Type	Generic
Category	Hospitality/Travel
Registry	Donuts
IDN Capable	No
Webpage	Register .TRAVEL

Contents 1 Registry 2 Periods 3 API 3.1 Domain Registration 3.2 Domain Transfer 3.3 Delete Domain 3.4 Restore Domain 3.5 Ownerchange 4 TLD specific 4.1 Registration 4.2 Domain Limitations and Requirements 5 Addons 6 RegistrarOC 6.1 ICANN Whois Data Reminder Policy (WDRP) 6.2 ICANN Registrar Data Escrow Program (RDE) 6.3 Restore Process

[edit] Registry

TLD	.travel
Registry	Donuts Inc.
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.donuts.co
WHOIS-Update	Real-Time
Min. Characters	1
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 0 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	Yes
Restore capable	Real-Time
Handle Updates	Supported
Registration System	Real-Time
Allowed number of NS	0 to 13
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer Pending Period	5 days
Transfer Expire Action	ACK
Transfer ACK by	Registrar
Transfer NACK by	Registrar
Transfer Lock	Yes
Owner Change by	ICANN-TRADE

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-5 days
Finalization Period	1 day
Failure Period	44 days
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	5 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

[edit] API

[edit] Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
x-travel-uin = <TRAVEL UIN>
x-travel-industry = 1

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

[edit] Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

Please note that HEXONET is acting in compliance with ICANN Transfer Guidelines. The respective policies can be viewed under http://www.icann.org/transfers/ :

As soon as you have submitted a transfer request, the HEXONET system start the transfer through the official registry and the losing registrar will receive the transfer request. The losing registrar will then send an email to the domain registrant/administrative contact, allowing them to deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

auth = <TEXT> | <NULL>
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

OPTIONAL

order = CREATE | REPLACE | UPDATE
subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

[edit] Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

OPTIONAL

domainalerttriggercode = <TEXT> | <NULL>
repository = <TEXT> | <NULL>

[edit] Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>

[edit] Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>

[edit] TLD specific

[edit] Registration

In order to register .TRAVEL domains, use the flag X-TRAVEL-INDUSTRY with the value 1, which means that the registrant acknowledges a relationship to the travel industry. By proceeding with their registration, the registrant acknowledges that they are engaged in or plan to engage in activities related to travel.

X-TRAVEL-INDUSTRY = 1

Please note that UINs will be deprecated in September 2018. You are encouraged to begin using the X-TRAVEL-INDUSTRY flag instead.

[edit] Domain Limitations and Requirements

.TRAVEL domain names are available to everyone who provides or plans to provide services, products, or content related to travel. New travel startups are welcome, and that includes every new travel content provider.

The following list, which is non-exhaustive and provided solely for illustrative purposes, contains example areas where a .TRAVEL domain would help you stand out:

• Airlines
• Attractions/Theme Parks
• Bed & Breakfast Houses
• Bus/Taxi/Limousine Operators
• Camp Facility Operators
• Vehicle Rental Companies/Airport Specialty Car Park Companies
• Computer Reservation/Travel Technology Provider
• Convention & Visitor's Bureaus
• Cruise Lines
• Ferries
• Hotels/Resorts/Casinos
• National Tourism Offices
• Passenger Rail Lines
• Restaurants
• Tour Operators
• Travel Agents
• Travel Bloggers
• Travel Media
• Travel-Consumer and Market Research Organizations
• Travel related Insurance
• Education
• Travel Associations and their members
• Travel search sites and applications, including any such site or application for use with the Internet or as an “app” for any mobile telephone or other communication device
• Travel technology providers
• Travel media providers

[edit] Addons

[edit] RegistrarOC

ICANN Whois Data Reminder Policy (WDRP)

At least annually, a registrar must present to the registrant the current Whois information, and remind the registrant that provision of false Whois information can be grounds for cancellation of his domain name registration. Registrants must review their Whois data, and make any corrections.

ICANN Registrar Data Escrow Program (RDE)

Under the data escrow provision of the Registrar Accreditation Agreement (RAA), all ICANN-accredited registrars must regularly deposit a backup copy of their gTLD registration data with ICANN through ICANN's arrangement with Iron Mountain or they may elect to use a Third Party Provider of RDE services that has been approved by ICANN.

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

{{{Possible Extensions}}}