Lyftbikes.com Reviews

Lyftbikes.com has a total of 11 DNS records. In the server records, it appears to be registered with the IP address N/A in France, Île-de-France, Paris, Europe/Paris with the information belonging to OVH ISP The domain was registered on N/A, and the expiration date appears to be on N/A. When checked on , the website is still online. According to Siteadvisor, visiting lyftbikes.com is safe.

Location :
Paris, France
Last Checked: December 29, 2024
Server Status :
Offline
Last Checked: N/A
Server :
OVH ISP
Last Checked: December 29, 2024
Lyftbikes.com Screenshot

Robot.txt Information

Robot Path Permission
Google Bot /
Bing Bot /
Baudi Spider /
Yandex Bot /

Meta Tags

Title N/A
Description N/A
Keywords N/A

Server Information

Website lyftbikes.com
Host IP N/A
Location Paris, France

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company OVH ISP
Registrar N/A
IPs N/A
DNS
  • ns-915.awsdns-50.net
  • ns-1178.awsdns-19.org
  • ns-1616.awsdns-10.co.uk
  • ns-78.awsdns-09.com

DNS Records

Host Type TTL Data
lyftbikes.com NS 86400 Target: ns-915.awsdns-50.net
lyftbikes.com NS 86400 Target: ns-1178.awsdns-19.org
lyftbikes.com NS 86400 Target: ns-1616.awsdns-10.co.uk
lyftbikes.com NS 86400 Target: ns-78.awsdns-09.com
lyftbikes.com SOA 900 MNAME: ns-915.awsdns-50.net
RNAME: awsdns-hostmaster.amazon.com
Serial: 1
Refresh: 7200
Retry: 900
Expire: 1209600
Minimum TTL: 86400
lyftbikes.com MX 300 IP/Target: alt4.aspmx.l.google.com
lyftbikes.com MX 300 IP/Target: alt1.aspmx.l.google.com
lyftbikes.com MX 300 IP/Target: alt2.aspmx.l.google.com
lyftbikes.com MX 300 IP/Target: aspmx.l.google.com
lyftbikes.com MX 300 IP/Target: alt3.aspmx.l.google.com
lyftbikes.com TXT 300 TXT: google-site-verification=iJMMXdC5EtHrwxa09hCETOxBMelikdNkbhebJyu00C4

HTTP Headers

                                                    N/A                                                

Lyftbikes.com Whois Information

                                                    Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date.