Samurai-energy.com has a total of 9 DNS records. In the server records, it appears to be registered with the IP address 162.43.120.161 in Japan, Tokyo, Chiyoda, Asia/Tokyo with the information belonging to XSERVER 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 samurai-energy.com is safe.
Robot | Path | Permission |
---|---|---|
Google Bot | / | |
Bing Bot | / | |
Baudi Spider | / | |
Yandex Bot | / |
Title | サムライエナジー|メイド・イン・ジャパン・エナジードリンク |
Description | 負けられないその瞬間。全力で。高品質なメイド・イン・ジャパン エナジードリンクとして、様々な商品とのコラボレーションによる豊富なラインナップ、商品開発を手がける株式会社ハイブリッドドリンクの新会社「ジャパンエナジー株式会社」です。 |
Keywords | N/A |
Website | samurai-energy.com |
Host IP | 162.43.120.161 🇯🇵 |
Location | Chiyoda, Japan |
Created | N/A |
Expires | N/A |
Owner | N/A |
Hosting Company | XSERVER Inc. |
Registrar | N/A |
IPs | 162.43.120.161 |
DNS |
|
Host | Type | TTL | Data |
---|---|---|---|
samurai-energy.com | A | 3600 | IP/Target: 162.43.120.161 |
samurai-energy.com | NS | 3600 | Target: ns5.xserver.jp |
samurai-energy.com | NS | 3600 | Target: ns2.xserver.jp |
samurai-energy.com | NS | 3600 | Target: ns4.xserver.jp |
samurai-energy.com | NS | 3600 | Target: ns3.xserver.jp |
samurai-energy.com | NS | 3600 | Target: ns1.xserver.jp |
samurai-energy.com | SOA | 3600 |
MNAME: ns1.xserver.jp RNAME: root.xserver.jp Serial: 0 Refresh: 10800 Retry: 3600 Expire: 604800 Minimum TTL: 3600 |
samurai-energy.com | MX | 3600 | IP/Target: samurai-energy.com |
samurai-energy.com | TXT | 3600 | TXT: google-site-verification=SFGnEbmESQmgjMypnAXMPbGb0By0sHinQe3qftY9gkw v=spf1 +a:sv14160.xserver.jp +a:samurai-energy.com +mx include:spf.sender.xserver.jp ~all |
0: HTTP/1.1 200 OK Server: nginx Date: Sun, 08 Dec 2024 03:28:07 GMT Content-Type: text/html Content-Length: 64236 Connection: close Vary: Accept-Encoding Last-Modified: Wed, 09 Oct 2024 07:27:03 GMT ETag: "faec-624062e2e9731" Accept-Ranges: bytes |
Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date. |