Lata.travel valuation and analysis

Lata.travel has global traffic rank of 2,737,023. Lata.travel has an estimated worth of US$ 6,214, based on its estimated Ads revenue. Lata.travel receives approximately 1,135 unique visitors each day. Its web server is located in London, England, United Kingdom, with IP address 139.59.162.67. According to SiteAdvisor, lata.travel is safe to visit.

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sat, 14 Dec 2019 09:43:28 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: https://lata.travel/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sat, 14 Dec 2019 09:43:29 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Pragma: no-cache
Expires: Sat, 14 Dec 2019 09:58:11 GMT
Cache-Control: max-age=3600
X-Redirect-By: WordPress
Location: https://www.lata.travel/
Fastcgi-Cache: HIT

HTTP/1.1 200 OK
Server: nginx
Date: Sat, 14 Dec 2019 09:43:32 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: integral-mailchimp-cookie=4cdd49eef436b628d4dc2c8cf2125284; expires=Sat, 14-Dec-2019 21:43:31 GMT; Max-Age=43200; path=/
Set-Cookie: PHPSESSID=q98jl55g0ku9r37pe03cca7b52; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Link: <https://www.lata.travel/wp-json/>; rel="https://api.w.org/"
Link: <https://www.lata.travel/>; rel=shortlink
X-TEC-API-VERSION: v1
X-TEC-API-ROOT: https://www.lata.travel/wp-json/tribe/events/v1/
X-TEC-API-ORIGIN: https://www.lata.travel
Fastcgi-Cache: MISS

Domain Name: lata.travel
Registry Domain ID: D1349528-TRAVEL
Registrar WHOIS Server:
Registrar URL: www.crazydomains.com
Updated Date: 2019-01-09T00:33:42Z
Creation Date: 2017-01-31T22:27:10Z
Registry Expiry Date: 2021-01-30T23:59:59Z
Registrar: Dreamscape Networks International Pte Ltd
Registrar IANA ID: 1291
Registrar Abuse Contact Email: registry@crazydomains.com
Registrar Abuse Contact Phone: +61.282089995
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name:
Registrant Organization: Private Registry Authority
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: London (City of)
Registrant Postal Code:
Registrant Country: GB
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns3.digitalocean.com
Name Server: ns1.digitalocean.com
Name Server: ns2.digitalocean.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

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