Beyma.com Reviews

Beyma.com has a total of 8 DNS records. In the server records, it appears to be registered with the IP address 82.98.171.93 in Spain, Madrid, Madrid, Europe/Madrid with the information belonging to DinaHosting S.L. 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 beyma.com is safe.

Location :
Madrid, Spain 🇪🇸
Last Checked: December 12, 2024
Server Status :
Offline
Last Checked: N/A
Server :
DinaHosting S.L.
Last Checked: December 12, 2024
Beyma.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 beyma.com
Host IP 82.98.171.93 🇪🇸
Location Madrid, Spain

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company DinaHosting S.L.
Registrar N/A
IPs 82.98.171.93
DNS
  • alina.ns.cloudflare.com
  • piotr.ns.cloudflare.com

DNS Records

Host Type TTL Data
beyma.com A 300 IP/Target: 82.98.171.93
beyma.com NS 86400 Target: alina.ns.cloudflare.com
beyma.com NS 86400 Target: piotr.ns.cloudflare.com
beyma.com SOA 1800 MNAME: alina.ns.cloudflare.com
RNAME: dns.cloudflare.com
Serial: 2358497314
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
beyma.com MX 300 IP/Target: beyma-com.mail.protection.outlook.com
beyma.com TXT 300 TXT: google-site-verification=yrvx0M57GD7X9J7LF0j5ZaxJhJ4EqbImJpg19e9BsfQ
beyma.com TXT 300 TXT: v=spf1 include:spf.protection.outlook.com -all
beyma.com TXT 300 TXT: v=spf2.0/pra include:beyma.ip-zone.com a mx -all

HTTP Headers

                                                    0: HTTP/1.1 403 Forbidden
Date: Thu, 12 Dec 2024 23:23:03 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: close
Vary: Accept-Encoding
Age: 0
Server: HTTPd
                                                

Beyma.com Whois Information

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