Jinjin.biz - Jin Jin


updated on

www.jinjin.biz website info

Homepage

Title: 黒ガジェットで統一したい!! – Just another WordPress site
URL: http://jinjin.biz/

Other meta

  • generator: WordPress 5.2.3
  • viewport: width=device-width, initial-scale=1

Webserver

Signature: nginx
Response status code: 200
Response speed: 6232 milliseconds

HTTP headers

  • Connection: keep-alive
  • Content-Encoding: gzip
  • Content-Type: text/html; charset=UTF-8
  • Date: Tue, 10 Sep 2019 10:39:47 GMT
  • Link: <http://jinjin.biz/wp-json/>; rel="https://api.w.org/"
  • Transfer-Encoding: chunked
  • Vary: Accept-Encoding
updated on

WHOIS jinjin.biz

The « WhoIs » is a publicly available database that stores the registration information on a domain name.

Creation date: Thursday, August 22, 2019
Expiration date: Saturday, August 22, 2020
Record last update: Sunday, September 8, 2019
Domain ID: DBB60C19021CE43C6A8372D5BDF52239E-NSR
Registrar: GMO Internet, Inc. d/b/a Onamae.com
Registrar IANA ID: 49
Domain status: ok https://icann.org/epp#ok
Nameservers: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, and ns5.xserver.jp
WHOIS server: whois.discount-domain.com

Similar domains

updated on

DNS data

« DNS » (Domain Name System) is the phone book for the Internet. It converts human readable names like "jinjin.biz" to a phone number so computers can call each other. Well, actually Internet uses IP Addresses, not phone numbers.

Apex

SOA

TTL: 3600
Serial number: 0
Retry: 3600
Negative caching time: 3600
Primary master: ns1.xserver.jp.
Zone admin: root.xserver.jp.
Refresh: 10800
Expire: 604800

NS

TTL: 3600
Servers: ns5.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, and ns1.xserver.jp

MX

TTL: 3600
Server:

  • jinjin.biz - 0

A

TTL: 3600
Canonical name: jinjin.biz.
Address: 183.181.84.69


www.jinjin.biz

A

TTL: 3600
Canonical name: www.jinjin.biz.
Address: 183.181.84.69


jinjin.biz live DNS

Check live dns records for jinjin.biz on dnstoolkit.net

Timeline of events

  • 9/9/19: registered on ns1.xserver.jp., ns2.xserver.jp., ns3.xserver.jp., ns4.xserver.jp., and ns5.xserver.jp.
  • 9/6/19: expired (was on ns1.xserver.jp., ns2.xserver.jp., ns3.xserver.jp., ns4.xserver.jp., and ns5.xserver.jp.)
  • 8/24/19: transferred from ns1.xsever.jp., ns2.xsever.jp., ns3.xsever.jp., ns4.xsever.jp., and ns5.xsever.jp. to ns1.xserver.jp., ns2.xserver.jp., ns3.xserver.jp., ns4.xserver.jp., and ns5.xserver.jp.
  • 8/23/19: registered on ns1.xsever.jp., ns2.xsever.jp., ns3.xsever.jp., ns4.xsever.jp., and ns5.xsever.jp.
  • 6/5/19: expired (was on expirens3.hichina.com. and expirens4.hichina.com.)
  • 5/6/19: transferred from dns31.hichina.com. and dns32.hichina.com. to expirens3.hichina.com. and expirens4.hichina.com.
  • 5/5/18: registered on dns31.hichina.com. and dns32.hichina.com.
  • 3/29/18: expired (was on nsexp1.value-domain.com. and nsexp2.value-domain.com.)
  • 3/20/18: transferred from ns3.expirationwarning.net. and ns7.expirationwarning.net. to nsexp1.value-domain.com. and nsexp2.value-domain.com.
  • 7/12/17: transferred from ns3.expirationwarning.net. and ns7.expirationwarning.net. to ns3.expirationwarning.net. and ns7.expirationwarning.net.