Sanmu15.com Reviews

Sanmu15.com has a total of 6 DNS records. In the server records, it appears to be registered with the IP address 157.7.44.243 in Japan, Tokyo, Chiyoda, Asia/Tokyo with the information belonging to GMO Internet, 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 sanmu15.com is safe.

Location :
Chiyoda, Japan 🇯🇵
Last Checked: January 25, 2025
Server Status :
Online
Last Checked: January 25, 2025
Server :
GMO Internet, Inc.
Last Checked: January 25, 2025
Sanmu15.com Screenshot

Robot.txt Information

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

Meta Tags

Title 関東最大級の苺狩りエリア千葉県山武市成東 | 山武市成東観光苺組合
Description 苺狩りなら都心から近い千葉県山武市成東へ。国道126号ストロベリーロードを中心に20軒の苺園が集まっています。苺狩りは40分食べ放題。苺組合全体で20品種以上の苺を栽培しています。苺の直売も行なっていますので、お土産にどうぞ。
Keywords N/A

Server Information

Website sanmu15.com
Host IP 157.7.44.243 🇯🇵
Location Chiyoda, Japan

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company GMO Internet, Inc.
Registrar N/A
IPs 157.7.44.243
DNS
  • dns0.heteml.jp
  • dns1.heteml.jp

DNS Records

Host Type TTL Data
sanmu15.com A 1800 IP/Target: 157.7.44.243
sanmu15.com NS 86400 Target: dns0.heteml.jp
sanmu15.com NS 86400 Target: dns1.heteml.jp
sanmu15.com SOA 2560 MNAME: dns0.heteml.jp
RNAME: hostmaster.sanmu15.com
Serial: 1737803777
Refresh: 16384
Retry: 2048
Expire: 1048576
Minimum TTL: 2560
sanmu15.com MX 3600 IP/Target: mx.hetemail.jp
sanmu15.com TXT 3600 TXT: v=spf1 include:_spf.heteml.jp ~all

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Date: Sat, 25 Jan 2025 11:43:08 GMT
Content-Type: text/html
Content-Length: 84068
Connection: close
Server: Apache
Last-Modified: Sun, 19 Jan 2025 03:26:44 GMT
Accept-Ranges: none
Vary: Range,Accept-Encoding
                                                

Sanmu15.com Whois Information

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