Lavisa.net Reviews

Lavisa.net has a total of 8 DNS records. In the server records, it appears to be registered with the IP address 64.29.145.9 in Canada, Ontario, Waterloo, America/Toronto with the information belonging to Internet Names For Business Inc. 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 lavisa.net is safe.

Location :
Waterloo, Canada 🇨🇦
Last Checked: December 27, 2024
Server Status :
Offline
Last Checked: N/A
Server :
Internet Names For Business Inc.
Last Checked: December 27, 2024
Lavisa.net 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 lavisa.net
Host IP 64.29.145.9 🇨🇦
Location Waterloo, Canada

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company Internet Names For Business Inc.
Registrar N/A
IPs 64.29.145.9
DNS
  • dns.alestra.net.mx
  • mail2.alestra.net.mx
  • mail1.alestra.net.mx

DNS Records

Host Type TTL Data
lavisa.net A 3600 IP/Target: 64.29.145.9
lavisa.net NS 86400 Target: dns.alestra.net.mx
lavisa.net NS 86400 Target: mail2.alestra.net.mx
lavisa.net NS 86400 Target: mail1.alestra.net.mx
lavisa.net SOA 3600 MNAME: dns.alestra.net.mx
RNAME: soporteip.axtel.com.mx
Serial: 754255117
Refresh: 10800
Retry: 3600
Expire: 1209600
Minimum TTL: 3600
lavisa.net MX 3600 IP/Target: lavisa-net.mail.protection.outlook.com
lavisa.net TXT 0 TXT: MS=ms69340089
lavisa.net TXT 0 TXT: v=spf1 include:spf.ipzmarketing.com include:spf.protection.outlook.com -all

HTTP Headers

                                                    0: HTTP/1.1 403 Forbidden
Date: Fri, 27 Dec 2024 09:17:05 GMT
Content-Type: text/html
Content-Length: 150
Connection: close
                                                

Lavisa.net Whois Information

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