Yingkey.net - Ying Key


updated on

www.yingkey.net website info


Webserver

Signature: nginx
Response status code: 400
Response speed: 2505 milliseconds

HTTP headers

  • Connection: keep-alive
  • Content-Type: text/html; charset=utf-8
  • Date: Wed, 16 Jun 2021 02:20:40 GMT
  • Transfer-Encoding: chunked
updated on

WHOIS yingkey.net

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

Creation date: Monday, June 14, 2021
Expiration date: Tuesday, June 14, 2022
Record last update: Monday, June 14, 2021
Domain ID: 2619501866_DOMAIN_NET-VRSN
Registrar: PSI-USA, Inc. dba Domain Robot
Registrar IANA ID: 151
Domain status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Nameservers: NS1.GNAME-DNS.COM and NS2.GNAME-DNS.COM
WHOIS server: whois.psi-usa.info

Similar domains

updated on

DNS data

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

Apex

SOA

TTL: 598
Serial number: 1623681552
Retry: 3600
Negative caching time: 1800
Primary master: ns1.gname.net.
Zone admin: admin.gname.net.
Refresh: 7200
Expire: 1209600

NS

TTL: 86400
Servers: ns1.gname.net and ns2.gname.net

A

TTL: 600
Canonical name: yingkey.net.
Address: 154.195.194.236


www.yingkey.net

A

TTL: 600
Canonical name: www.yingkey.net.
Address: 154.195.194.236


yingkey.net live DNS

Check live dns records for yingkey.net on dnstoolkit.net

Timeline of events

  • 6/15/21: registered on ns1.gname-dns.com. and ns2.gname-dns.com.
  • 5/8/21: expired (was on expired1.namebrightdns.com. and expired2.namebrightdns.com.)
  • 3/28/21: transferred from ns1.domains-hold.com. and ns2.domains-hold.com. to expired1.namebrightdns.com. and expired2.namebrightdns.com.
  • 11/4/20: transferred from jm1.dns.com. and jm2.dns.com. to ns1.domains-hold.com. and ns2.domains-hold.com.
  • 8/29/20: transferred from f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net. to jm1.dns.com. and jm2.dns.com.
  • 1/13/19: transferred from v1.juming-xz.com. and v1.xz-juming.com. to ns1.maff.com. and ns2.maff.com.
  • 1/11/19: registered on v1.juming-xz.com. and v1.xz-juming.com.
  • 12/5/18: expired (was on ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.)
  • 11/2/18: transferred from ns1.dnsfang.com. and ns2.dnsfang.com. to ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.
  • 4/28/18: transferred from ns1.dnsv1.com. and ns2.dnsv1.com. to ns1.dnsfang.com. and ns2.dnsfang.com.
  • 4/17/18: transferred from ns1.server-hold.com. and ns2.server-hold.com. to ns1.dnsv1.com. and ns2.dnsv1.com.
  • 1/13/18: transferred from f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net. to ns1.server-hold.com. and ns2.server-hold.com.
  • 11/6/17: transferred from ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net. to f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net.
  • 11/2/17: transferred from f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net. to ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.
  • 10/29/17: transferred from f1g1ns1.dnspod and f1g1ns2.dnspod to f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net.