Yujin-blog.com Reviews

Yujin-blog.com has a total of 7 DNS records. In the server records, it appears to be registered with the IP address 118.27.100.222 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 yujin-blog.com is safe.

Location :
Chiyoda, Japan 🇯🇵
Last Checked: January 17, 2025
Server Status :
Online
Last Checked: January 17, 2025
Server :
GMO Internet, Inc.
Last Checked: January 17, 2025
Yujin-blog.com Screenshot

Robot.txt Information

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

Meta Tags

Title ゆうじんブログ
Description 新潟の食・観る・遊ぶをお伝えしつつ、趣味や日常のことも発信しています。
Keywords 新潟,長岡,三条,グルメ,読書,

Server Information

Website yujin-blog.com
Host IP 118.27.100.222 🇯🇵
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 118.27.100.222
DNS
  • ns-a3.conoha.io
  • ns-a1.conoha.io
  • ns-a2.conoha.io

DNS Records

Host Type TTL Data
yujin-blog.com A 3600 IP/Target: 118.27.100.222
yujin-blog.com NS 3600 Target: ns-a3.conoha.io
yujin-blog.com NS 3600 Target: ns-a1.conoha.io
yujin-blog.com NS 3600 Target: ns-a2.conoha.io
yujin-blog.com SOA 3600 MNAME: ns-a1.conoha.io
RNAME: postmaster.yujin-blog.com
Serial: 1732959869
Refresh: 3600
Retry: 600
Expire: 86400
Minimum TTL: 3600
yujin-blog.com MX 3600 IP/Target: mail62.conoha.ne.jp
yujin-blog.com TXT 3600 TXT: v=spf1 include:_spf.conoha.ne.jp ~all

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Server: nginx
Date: Fri, 17 Jan 2025 10:11:08 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Vary: User-Agent
Link: ; rel="https://api.w.org/"
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Nginx-Cache: MISS
                                                

Yujin-blog.com Whois Information

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