TRAVEL

From TLDinfo
Jump to: navigation, search



Flag travel.png



RRPproxy is the Reseller Portal for ISPs, Registrars & Domain Investors. Domains, Hosting & More ...


Overview
IDN capable: No
Handle Updates: Yes
Registration Period: 1 year
Autorenew Grace Period: 35 days
Deletion Timeframe: 35 days after expiration date
Registration System: Realtime
WHOIS-Server: whois.nic.travel
WHOIS-Update: 15 min.
WHOIS-Privacy:
Registry: Registry
Dispute Policy: Policy
DNSSEC: No


Contents

Zone Info

.TRAVEL is a so-called generic Top-Level-Domain (gTLD).

Zone Use

The .TRAVEL TLD will be the online community for operators of the travel and tourism industry.

Characters

  • Minimum: 3
  • Maximum: 63
  • Letters and numbers
  • Hyphens ("-"), however not at the beginning or directly in front of the TLD

Domain Registration

.TRAVEL domains can be registered online through webinterface or API, however some special parameters have to be given.

[COMMAND]
(required)                
command         = AddDomain
domain          = yourdomain.travel
ownercontact0   = [owner handle]
admincontact0   = [admin contact]
techcontact0    = [tech contact]
billingcontact0 = [billing contact]
nameserver0     = [nameserver1]
nameserver1     = [nameserver2]
                
EOF
  • X-TRAVEL-UIN
    • In order to register .TRAVEL domains the registrant has to provide a UIN "Unique Identification Number". The UIN can be obtained directly at the registry: http://www.travel.travel/obtain-uin/

Approval permits the holder of a UIN to apply to register a .TRAVEL domain name, subject to restrictions on name selection and reserved names.


Would you like to have instant access to RRPproxy and more than 300 domain extensions? Sign-up here for free ...


Domain Modification

Trade

Registrant changes for .TRAVEL domains can be done online via api or webinterface. Necessary for this action is the new X-TRAVEL-UIN of the new owner. After a successful trade of the domain the domains exp. date will be extended by one year.

[COMMAND]
(required)              
command       = TradeDomain
domain        = yourdomain.travel
ownercontact0 = [new Owner handle]
X-TRAVEL-UIN  = [new TRAVEL-UIN]
              
EOF


Please Note:
The new X-TRAVEL-UIN will be checked against the .TRAVEL registry.

Domain Renewal

.TRAVEL domains can be renewed through the webinterface or with the corresponding API command.

[COMMAND]
(required)           
command    = RenewDomain
domain     = yourdomain.travel
period     = [renew period]
expiration = [current year of expiration]
           
EOF

Deletion Process

.TRAVEL Domains can be deleted online through the DeleteDomain Command.

[COMMAND]
(required)        
command = DeleteDomain
domain  = yourdomain.travel
        
EOF

Restrictions

Name registration is limited to names to which the travel organization holds rights to, or uses in their business. In the following some examples:

  • Incorporation (legal) Name/Partnership Name/Individual Name
  • Doing Business As; Trade Name; or Business Name
  • Domain Name as used in a URL
  • Trade Mark
  • Service Mark
  • Product Name
  • Club or Association Name
  • Transport Vessel Name
  • Competition/Event Name
  • Division Name
  • Subsidiary Name
  • Acronyms (must be only the first letter of the primary words of the name)

Eligibility is verified by the .travel Registry reviewing information provided by the applicant to determine that the applicant is primarily carrying on business or operations in the travel industry. .TRAVEL can be registered if your entity belongs to one of the following Travel Sectors:

  • 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 Media
  • Travel-Consumer and Market Research Organizations

Transfers

.TRAVEL Transfers are possible. Upon successfully transfering a domain, it is automatically renewed for one year. The registration period is extended by one year.

Transfer procedure

  • .TRAVEL Transfers can either be done through the RRPproxy WebInterface or API.
[COMMAND]
(required)        
command = TransferDomain
domain  = domain.travel
action  = request
auth    = [Auth]:[.travel UIN]
        
EOF
  • After the transfer has been requested, our backend system sends a confirmation email to the Owner/Admin-C according to the WHOIS of the respective domain. In order to initiate the transfer successfully it is important, that this email is confirmed.
  • After confirmation the transfer is initiated through the official registry and the losing registrar will receive the transfer request.
  • The losing registrar will also send an email to the Owner/Admin-C. allowing him/her to deny the transfer. If you do not respond to the email of the losing registrar, then the transfer will get processed successfully after 5 days.
Attention.png If the Email-Address in the WHOIS is invalid, then the transfer cannot be processed.If this is the case, then kindly contact your current registrar and ask him to update the WHOIS information accordingly.


Transfer notes

  • A .TRAVEL Domain Transfer must be initiated with a so-called Authorisation Code, which can be obtained from the current registrar through the owner or Admin-C of the domain.
  • Ensure that your respective domain does not have a lock-status (REGISTRAR-LOCK or HOLD). This can be seen in the WHOIS.
    If the domain is locked, then the owner can demand that the domain will be unlocked.
  • Please note that we are only allowed to initiate a gTLD transfer after confirmation of the "ICANN Form of Authorization" by the current registrant. The policies can be viewed under http://www.icann.org/transfers/
  • Please ensure that the domain is older than 60 days otherwise the transfer will be denied.

Authorization Codes

  1. The following validation rules will be applied for the authInfo element when a new domain is being added or when the authInfo for an existing domain is being updated.
  2. The authInfo will need to have at least eight characters consisting of one number, one alphabet and one special character.

Please see below for allowed characters

Numbers 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 0
Upper Case Alphabets A , B , C , D , E , F , G , H , I , J , K , L , M , N , O , P , Q , R , S , T , U , V , W , X , Y , Z
Lower Case Alphabets a , b , c , d , e , f , g , h , i , j , k , l , m , n , o , p , q , r , s , t , u , v , w , x , y , z
Special Characters ! , " , # , $ , % , & , ' , ( , ) , * , + , , , - , . , / , : , ; , < , = , > , ? , @ , [ , \ , ] , ^ , _ , ` , { , | , } , ~


Restores

Restores are possible within 30 days upon deletion. A restore can be requested via API command or via webinterface.

[COMMAND]
(required)        
command = restoredomain
domain  = yourdomain.travel
        
EOF

Please note: The restore request will be manually processed by our support team. You will be notified by email.


Personal tools
Namespaces

Variants
Actions
Resources
new gTLDs
Products
New Users
General
Tools