leafyglen.com - robtex.com
leafyglen.com
| DNSSEC | β οΈ Not signed | ||||||
| A | 168.76.102.141πΏπ¦ ASLINE-AS-AP168.76.96.0/20 Proxy-registered route object | ||||||
| NS | ns1.julydns.com β | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1770191211 | ||||||
com
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gtld-servers.net β | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786727574 | ||||||
Same first word
leafyglen.com |
DNS History
13 records (3 active, 10 former)
βNSdns1.name-services.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βNSdns2.name-services.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βNSdns3.name-services.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βNSdns4.name-services.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βNSdns5.name-services.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βNSf1g1ns1.dnspod.net2017-11-07 β 2017-11-07 Β· 4 obs
β 2017-11-07 09:34:56
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βNSf1g1ns2.dnspod.net2017-11-07 β 2017-11-07 Β· 4 obs
β 2017-11-07 09:34:56
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βNSns1.julydns.com2026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βNSns2.julydns.com2026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βMXmx.hoyu-cctv.com2017-11-07 β 2017-11-07 Β· 4 obs
β 2017-11-07 09:34:56
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βMXvipmail.yiqibao.com2016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
βA168.76.102.1412026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 02:55:10
β 2026-08-14 17:31:56
βA64.214.182.1412016-12-02 β 2016-12-02 Β· 3 obs
β 2017-11-07 09:34:56
β 2026-08-14 17:31:56
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| leafyglen.com | ns1.julydns.com, ns2.julydns.com | 2 records |
β Authoritative Response
Server:162.159.48.223
NS records: ns1.julydns.com, ns2.julydns.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for leafyglen.com (unsigned zone)
β±οΈ Timing
Total: 252ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 168.76.102.141 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)
Analysis
IP Addresses
leafyglen.com resolves to one IP address: 168.76.102.141.
Other host names, among them hwqz888.com and fjjinggong.com, have IP numbers in common with leafyglen.com.
Name Servers
leafyglen.com has two authoritative name servers β ns1.julydns.com and ns2.julydns.com.
leafyglen.com uses the same name servers as several other domains β among them huijingchushiji.com, hnsmsm.com, singtu.com and two more.
At least some of leafyglen.com's name servers are shared with other domains, for example szppt.cn, yjrmm.com, cbgzn.com and two more.
These name servers are often deployed together with the name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com.
ns1.julydns.com and ns2.julydns.com each point to one IP address β 162.159.48.223.
The host names ns1.julydns.com and ns2.julydns.com both resolve to 162.159.48.223 IP addresses.