jinledunfz.com - robtex.com
jinledunfz.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 202.162.101.23🇰🇭 CTGSERVERLIMITED-AS-AP202.162.101.0/24 RACKIP CONSULTANCY PTE. LTD. No. 3, Pemimpin Drive, 07-04 Lip Hing, Industrial Building, | ||||||
| NS | ns1.julydns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns1.onclouddns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.onclouddns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1779086459 | ||||||
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=1784968042 | ||||||
Previously NS for
jinledunfz.com |
Same first word
jinledunfz.com |
DNS History
20 records (5 active, 15 former)
○NSjinledunfz.com2015-07-20 → 2015-07-20 · 3 obs
○ 2016-02-23 02:02:02
○ 2026-07-25 08:41:18
○NSns.nagor.cn2016-02-23 → 2016-02-23 · 4 obs
● 2016-02-23 02:02:02
○ 2016-05-11 09:06:10
○ 2026-07-25 08:41:18
○NSns.nagor.com.cn2016-02-23 → 2016-02-23 · 4 obs
● 2016-02-23 02:02:02
○ 2016-05-11 09:06:10
○ 2026-07-25 08:41:18
○NSns1.dnsnw.com2016-02-23 → 2017-02-17 · 6 obs
● 2016-02-23 02:02:02
○ 2016-05-11 09:06:10
● 2017-02-17 16:33:26
○ 2020-01-07 21:33:40
○ 2026-07-25 08:41:18
○NSns1.judns.com2026-04-14 → 2026-05-22 · 5 obs
● 2026-04-14 23:52:32
● 2026-05-22 03:47:42
○ 2026-06-04 12:55:24
○ 2026-07-25 08:41:18
●NSns1.julydns.com2026-04-14 → 2026-07-25 · 3 obs
● 2026-04-14 23:52:32
● 2026-07-25 08:41:18
○NSns1.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
●NSns1.onclouddns.com2026-06-04 → 2026-07-25 · 3 obs
● 2026-06-04 12:55:24
● 2026-07-25 08:41:18
○NSns2.dnsnw.com2016-02-23 → 2016-02-23 · 4 obs
● 2016-02-23 02:02:02
○ 2016-05-11 09:06:10
○ 2026-07-25 08:41:18
○NSns2.judns.com2026-04-14 → 2026-05-22 · 5 obs
● 2026-04-14 23:52:32
● 2026-05-22 03:47:42
○ 2026-06-04 12:55:24
○ 2026-07-25 08:41:18
●NSns2.julydns.com2026-04-14 → 2026-07-25 · 3 obs
● 2026-04-14 23:52:32
● 2026-07-25 08:41:18
○NSns2.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
●NSns2.onclouddns.com2026-06-04 → 2026-07-25 · 3 obs
● 2026-06-04 12:55:24
● 2026-07-25 08:41:18
○NSns3.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
○NSns4.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
○NSns5.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
○NSns6.myhostadmin.net2020-01-07 → 2020-01-07 · 4 obs
● 2020-01-07 21:33:40
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
●A202.162.101.232026-04-14 → 2026-07-25 · 3 obs
● 2026-04-14 23:52:32
● 2026-07-25 08:41:18
○A59.188.19.2102015-07-20 → 2016-02-23 · 4 obs
● 2016-02-23 02:02:02
○ 2016-05-11 09:06:10
○ 2026-07-25 08:41:18
○CNAMElihepet.gotoip4.com2020-01-07 → 2020-01-07 · 3 obs
○ 2026-04-14 23:52:32
○ 2026-07-25 08:41:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| jinledunfz.com | ns1.onclouddns.com, ns2.onclouddns.com | 2 records |
✅ Authoritative Response
Server:162.159.27.251
NS records: ns1.onclouddns.com, ns2.onclouddns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for jinledunfz.com (unsigned zone)
⏱️ Timing
Total: 297ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 202.162.101.23 |
| 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.onclouddns.com, ns2.onclouddns.com)
Analysis
IP Addresses
jinledunfz.com points to a single IP number: 202.162.101.23.
Additional host names — including llxyljt.com and cdmeitian.com — share IP numbers with jinledunfz.com.
Name Servers
jinledunfz.com has four authoritative name servers: ns1.julydns.com, ns2.julydns.com, ns1.onclouddns.com and ns2.onclouddns.com.
jinledunfz.com has at least partial name server overlap with other domains, such as szyltwl.com, tkgoodale.com, ux7lva.cn and two others.
It is common to see these name servers used together with name servers ns1.judns.com and ns2.judns.com.
ns1.julydns.com and ns2.julydns.com each resolve to 162.159.48.223, while ns1.onclouddns.com and ns2.onclouddns.com each resolve to 162.159.27.251.
ns1.julydns.com and ns2.julydns.com each have 162.159.48.223 IP addresses.
ns1.onclouddns.com and ns2.onclouddns.com each have 162.159.27.251 IP addresses.