Sha256: 4534f0527ff37e1808ebaff326f34a9eb1be44e79ea443f68bdc7ccb1ebe262d

Contents?: true

Size: 1.54 KB

Versions: 43

Compression:

Stored size: 1.54 KB

Contents

Not found: u34jedzcq.travel

>>>> Whois database was last updated on: Fri Dec 25 21:27:34 GMT 2009 <<<<

Tralliance, Inc., the Registry Operator for .travel, has collected this information
for the WHOIS database through an ICANN-Accredited Registrar.  This information
is provided to you for informational purposes only and is designed to assist
persons in determining contents of a domain name registration record in the
Tralliance registry database.  Tralliance makes this information available to you
"as is" and does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that, under no
circumstances will you use this data: (1) to allow, enable, or otherwise
support the transmission of mass unsolicited, commercial advertising or
solicitations via direct mail, electronic mail, or by telephone; (2) in
contravention of any applicable data and privacy protection acts; or (3) to
enable high volume, automated, electronic processes that apply to the registry
(or its systems).  Compilation, repackaging, dissemination, or other use of the
WHOIS database in its entirety, or of a substantial portion thereof, is not
allowed without Tralliance's prior written permission.  Tralliance reserves the
right to modify or change these conditions at any time without prior or
subsequent notification of any kind.  By executing this query, in any manner
whatsoever, you agree to abide by these terms.

NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE
OF THE AVAILABILITY OF A DOMAIN NAME.

Version data entries

43 entries across 43 versions & 1 rubygems

Version Path
whois-2.6.3 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.6.2 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.6.1 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.6.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.5.1 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.5.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.4.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.3.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.2.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.1.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.7 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.6 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.5 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.4 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.3 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.2 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.1 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-2.0.0 spec/fixtures/responses/whois.nic.travel/status_available.txt
whois-1.2.2 test/testcases/responses/whois.nic.travel/available.txt
whois-1.2.1 test/testcases/responses/whois.nic.travel/available.txt