HTTP/1.1 200 OK Server: nginx/1.16.1 Date: Wed, 06 Nov 2019 07:28:33 GMT Content-Type: text/html Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding
| Semrush Rank | 2382798 | Rank based on keywords, cost and organic traffic |
| Keywords | 3954 | Number of keywords in top 20 Google SERP |
| Organic Traffic | 179 | Number of visitors coming from top 20 search results |
| Cost (in USD) | 22$ | How much need to spend if get same number of visitors from Google Adwords |
| Adwords Keyword | 0 | Keywords a website is buying in Google AdWords for ads that appear in paid search results. |
| Adwords Traffic | 0 | Number of visitors brought to the website via paid search results. |
| Adwords budget (in USD) | 0$ | Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results (monthly estimation). |
| Host | Type | Class | TTL | Extra |
|---|---|---|---|---|
| lemi.travel | TXT | IN | 300 | txt: google-site-verification=kp9GQNtbAhOlQQgbvIGivrkOmsFeTBQnrp1BhdaJwDs entries: Array |
| lemi.travel | MX | IN | 300 | pri: 40 target: aspmx2.googlemail.com |
| lemi.travel | MX | IN | 300 | pri: 50 target: aspmx3.googlemail.com |
| lemi.travel | MX | IN | 300 | pri: 30 target: alt2.aspmx.l.google.com |
| lemi.travel | MX | IN | 300 | pri: 20 target: alt1.aspmx.l.google.com |
| lemi.travel | MX | IN | 300 | pri: 10 target: aspmx.l.google.com |
| lemi.travel | SOA | IN | 900 | mname: ns-1750.awsdns-26.co.uk rname: awsdns-hostmaster.amazon.com serial: 1 refresh: 7200 retry: 900 expire: 1209600 minimum-ttl: 86400 |
| lemi.travel | A | IN | 300 | ip: 52.36.182.15 |
| lemi.travel | NS | IN | 3600 | target: ns-1750.awsdns-26.co.uk |
| lemi.travel | NS | IN | 3600 | target: ns-1198.awsdns-21.org |
| lemi.travel | NS | IN | 3600 | target: ns-1012.awsdns-62.net |
| lemi.travel | NS | IN | 3600 | target: ns-95.awsdns-11.com |
Domain Name: lemi.travel Registry Domain ID: DD895F2D1FFCF471BADCD4DA98E3906F1-NSR Registrar WHOIS Server: Registrar URL: www.name.com Updated Date: 2019-04-15T17:26:42Z Creation Date: 2018-05-02T21:02:15Z Registry Expiry Date: 2020-05-02T21:02:15Z Registrar: Name.com, Inc. Registrar IANA ID: 625 Registrar Abuse Contact Email: abuse@name.com Registrar Abuse Contact Phone: +1.7203101849 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: Registrant Name: Registrant Organization: Registrant Street: Registrant Street: Registrant Street: Registrant City: Registrant State/Province: Hong Kong Registrant Postal Code: Registrant Country: HK Registrant Phone: Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant 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 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: ns-1012.awsdns-62.net Name Server: ns-1750.awsdns-26.co.uk Name Server: ns-95.awsdns-11.com Name Server: ns-1198.awsdns-21.org DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2019-11-06T07:28:32Z <<< For more information on Whois status codes, please visit https://icann.org/epp The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.travel.
