ip126.com - dns.ninja

ip126.com

DNSSEC⚠️ Not signed
NSns1.julydns.com
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.julydns.com
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1782755556

Same first word

ip126.com

Similar names

261pi.com
16pi2.com
ip216.com
pi126.com

DNS History

20 records (2 active, 18 former)

200920112013201520172019202120232025NSns1.julydns.comns2.julydns.comns1.dns.com.cnns1.myhostadmin.netns2.dns.com.cnns2.myhostadmin.netns3.myhostadmin.netns4.myhostadmin.netns5.myhostadmin.netns6.myhostadmin.netMXmail.ip126.comA121.201.3.181125.88.190.28125.88.190.59222.83.136.3561.160.224.20361.160.224.212CNAME878bc968a0b2de0fd0cb70b591b29387.dnspao.comip126.gotoip3.comweb.m174.vhostgo.com
○NSns1.dns.com.cn2008-03-18 → 2008-03-18 · 3 obs
● 2008-03-18 21:36:46
○ 2015-06-22 08:01:08
○ 2026-06-29 18:06:28
●NSns1.julydns.com2026-02-23 → 2026-06-29 · 3 obs
○ 2018-09-14 18:43:14
● 2026-02-23 12:34:30
● 2026-06-29 18:06:28
○NSns1.myhostadmin.net2015-06-22 → 2018-09-14 · 5 obs
○ 2008-03-18 21:36:46
● 2015-06-22 08:01:08
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○NSns2.dns.com.cn2008-03-18 → 2008-03-18 · 3 obs
● 2008-03-18 21:36:46
○ 2015-06-22 08:01:08
○ 2026-06-29 18:06:28
●NSns2.julydns.com2026-02-23 → 2026-06-29 · 3 obs
○ 2018-09-14 18:43:14
● 2026-02-23 12:34:30
● 2026-06-29 18:06:28
○NSns2.myhostadmin.net2015-10-30 → 2018-09-14 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○NSns3.myhostadmin.net2015-10-30 → 2018-09-14 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○NSns4.myhostadmin.net2015-10-30 → 2018-09-14 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○NSns5.myhostadmin.net2015-10-30 → 2018-09-14 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○NSns6.myhostadmin.net2015-10-30 → 2018-09-14 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○MXmail.ip126.com2008-03-18 → 2008-03-18 · 3 obs
● 2008-03-18 21:36:46
○ 2015-06-22 08:01:08
○ 2026-06-29 18:06:28
○A121.201.3.1812017-01-24 → 2017-01-24 · 4 obs
○ 2016-04-15 21:48:52
● 2017-01-24 23:41:38
○ 2018-09-14 18:43:14
○ 2026-06-29 18:06:28
○A125.88.190.282015-10-30 → 2015-10-30 · 4 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
○ 2016-01-14 08:12:14
○ 2026-06-29 18:06:28
○A125.88.190.592015-06-22 → 2015-06-22 · 4 obs
○ 2008-03-18 21:36:46
● 2015-06-22 08:01:08
○ 2018-09-14 18:43:14
○ 2026-06-29 18:06:28
○A222.83.136.352008-03-18 → 2008-03-18 · 3 obs
● 2008-03-18 21:36:46
○ 2015-06-22 08:01:08
○ 2026-06-29 18:06:28
○A61.160.224.2032016-01-14 → 2016-01-14 · 4 obs
○ 2015-10-30 06:46:10
● 2016-01-14 08:12:14
○ 2016-04-15 21:48:52
○ 2026-06-29 18:06:28
○A61.160.224.2122016-04-15 → 2016-04-15 · 4 obs
○ 2016-01-14 08:12:14
● 2016-04-15 21:48:52
○ 2017-01-24 23:41:38
○ 2026-06-29 18:06:28
○CNAME878bc968a0b2de0fd0cb70b591b29387.dnspao.com2015-10-30 → 2016-04-15 · 5 obs
○ 2015-06-22 08:01:08
● 2015-10-30 06:46:10
● 2016-04-15 21:48:52
○ 2017-01-24 23:41:38
○ 2026-06-29 18:06:28
○CNAMEip126.gotoip3.com2015-06-22 → 2018-09-14 · 5 obs
○ 2008-03-18 21:36:46
● 2015-06-22 08:01:08
● 2018-09-14 18:43:14
○ 2026-02-23 12:34:30
○ 2026-06-29 18:06:28
○CNAMEweb.m174.vhostgo.com2017-01-24 → 2017-01-24 · 4 obs
○ 2016-04-15 21:48:52
● 2017-01-24 23:41:38
○ 2018-09-14 18:43:14
○ 2026-06-29 18:06:28

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net...-
ip126.comns1.julydns.com, ns2.julydns.com2 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 ip126.com (unsigned zone)

⏱️ Timing

Total: 350ms | Queries: -

📄 Records

TypeCountSample Data
NS2ns1.julydns.com, ns2.julydns.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)

Analysis

Name Servers

ip126.com uses two name servers for its delegation: ns1.julydns.com and ns2.julydns.com.

The name server configuration of ip126.com is shared with other domains, for instance aksdgc.com, 7ncc.com, hjsj9999.com and two others.

At least some of ip126.com's name servers are shared with other domains, for example itecgroup.cn, mioqb.com, 916q.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 resolves to 162.159.48.223; ns2.julydns.com resolves to the same IP address, 162.159.48.223.

Both ns1.julydns.com and ns2.julydns.com resolve to 162.159.48.223 IP addresses each.