3glm.net - 3glm


updated on

www.3glm.net website info

Homepage

Title: 404 - 找不到文件或目录。
URL: http://www.3glm.net/


Webserver

Signature: Microsoft-IIS/8.5
Response status code: 404
Response speed: 2614 milliseconds

HTTP headers

  • Access-Control-Allow-Headers: *
  • Access-Control-Allow-Methods: GET, POST
  • Access-Control-Allow-Origin: *
  • Content-Length: 1163
  • Content-Type: text/html
  • Date: Sat, 14 Aug 2021 01:24:21 GMT
  • X-Powered-By: ASP.NET
updated on

WHOIS 3glm.net

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

Creation date: Sunday, August 8, 2021
Expiration date: Monday, August 8, 2022
Record last update: Sunday, August 8, 2021
Domain ID: 2632320232_DOMAIN_NET-VRSN
Registrar: Domain International Services Limited
Registrar IANA ID: 3863
Domain status: ok https://icann.org/epp#ok
Nameservers: DM1.DNS.COM and DM2.DNS.COM
WHOIS server: https://whois.domain.vip

updated on

DNS data

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

Apex

SOA

TTL: 600
Serial number: 1628408787
Retry: 3600
Negative caching time: 1800
Primary master: dm1.dns.com.
Zone admin: dnsadmin.dns.com.
Refresh: 7200
Expire: 1209600

NS

TTL: 86400
Servers: dm1.dns.com and dm2.dns.com

A

TTL: 600
Canonical name: 3glm.net.
Address: 154.85.234.7


www.3glm.net

A

TTL: 600
Canonical name: www.3glm.net.
Address: 154.85.234.7


3glm.net live DNS

Check live dns records for 3glm.net on dnstoolkit.net

Timeline of events

  • 8/12/21: registered on dm1.dns.com. and dm2.dns.com.
  • 4/10/21: expired (was on sk.s5.ans1.ns148.ztomy.com. and sk.s5.ans2.ns148.ztomy.com.)
  • 3/1/21: transferred from jm1.alidns.com. and jm2.alidns.com. to sk.s5.ans1.ns148.ztomy.com. and sk.s5.ans2.ns148.ztomy.com.
  • 1/19/19: expired (was on ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.)
  • 12/18/18: transferred from ns1.jiasule.net. and ns2.jiasule.net. to ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.
  • 10/9/18: transferred from ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., ns4.myhostadmin.net., ns5.myhostadmin.net., and ns6.myhostadmin.net. to ns1.jiasule.net. and ns2.jiasule.net.
  • 8/20/18: transferred from f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net. to ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., ns4.myhostadmin.net., ns5.myhostadmin.net., and ns6.myhostadmin.net.
  • 3/9/18: transferred from ns1-show.myhostadmin.net. and ns2-show.myhostadmin.net. to f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net.
  • 3/8/18: transferred from f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net. to ns1-show.myhostadmin.net. and ns2-show.myhostadmin.net.
  • 1/19/18: transferred from ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., and ns4.myhostadmin.net. to f1g1ns1.dnspod.net. and f1g1ns2.dnspod.net.
  • 1/18/18: transferred from ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net. to ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., and ns4.myhostadmin.net.
  • 12/17/17: transferred from ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., ns4.myhostadmin.net., ns5.myhostadmin.net., and ns6.myhostadmin.net. to ns1-domain-expired.myhostadmin.net. and ns2-domain-expired.myhostadmin.net.
  • 10/29/17: transferred from ns1.myhostadmin, ns2.myhostadmin, ns3.myhostadmin, ns4.myhostadmin, ns5.myhostadmin, and ns6.myhostadmin to ns1.myhostadmin.net., ns2.myhostadmin.net., ns3.myhostadmin.net., ns4.myhostadmin.net., ns5.myhostadmin.net., and ns6.myhostadmin.net.