Bet365-22.com Reviews

Bet365-22.com has a total of 4 DNS records. In the server records, it appears to be registered with the IP address 103.203.41.98 in United States, California, Los Angeles, America/Los_Angeles with the information belonging to QuickPacket, LLC 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 bet365-22.com is safe.

Location :
Los Angeles, United States 🇺🇸
Last Checked: January 17, 2025
Server Status :
Online
Last Checked: January 17, 2025
Server :
QuickPacket, LLC
Last Checked: January 17, 2025
Bet365-22.com Screenshot

Robot.txt Information

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

Meta Tags

Title Bet365亚洲官网
Description Bet365官方网站是国际最大线上运营平台,拥有真人、体育、电子、彩票、棋牌等娱乐游戏,十年信誉品牌,安全靠谱稳定,更多精彩游戏等您来体验!
Keywords Bet365,Bet365官网,Bet365开户,Bet365中文,Bet365中国备用网址,Bet365亚洲官网

Server Information

Website bet365-22.com
Host IP 103.203.41.98 🇺🇸
Location Los Angeles, United States

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company QuickPacket, LLC
Registrar N/A
IPs 103.203.41.98
DNS
  • n2.xundns.com
  • n1.xundns.com

DNS Records

Host Type TTL Data
bet365-22.com A 600 IP/Target: 103.203.41.98
bet365-22.com NS 7200 Target: n2.xundns.com
bet365-22.com NS 7200 Target: n1.xundns.com
bet365-22.com SOA 7200 MNAME: n1.xundns.com
RNAME: nsadmin.xundns.com
Serial: 437896
Refresh: 3600
Retry: 600
Expire: 86400
Minimum TTL: 600

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Server: nginx
Date: Fri, 17 Jan 2025 21:21:08 GMT
Content-Type: text/html
Content-Length: 54900
Last-Modified: Fri, 03 May 2024 02:23:06 GMT
Connection: close
Vary: Accept-Encoding
ETag: "66344a8a-d674"
Strict-Transport-Security: max-age=31536000
Accept-Ranges: bytes
                                                

Bet365-22.com Whois Information

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