`oldbeijing.com`

DNSSEC	⚠️ Not signed
NS	`ns1.ename.net` ⭐
		A	2001:df2:f080:1::8^{🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	61.158.128.31^{🇨🇳 CHINA169-Backbone61.158.128.0/17 CNC Group CHINA169 Henan Province Network}
			PTR	`31.128.158.61.ha.cnc`
		A	218.98.111.173^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
			PTR	`ip-218-98-111-173.defastlink.net`
NS	`ns2.ename.net`
		A	240e:97d:10:1402:0:1:0:1005^{🇨🇳 CHINANET-Guangdong-DongGuan-IDC240e:97d::/36 DongGuan IDC Network}
		A	1.193.216.198^{🇨🇳 CHINANET-Henan-Luoyang-IDC1.193.216.0/24 Chinatelecom HeNan Province Network}
			PTR	`ip-1-193-216-198.defastlink.net`
		A	183.253.57.199^{🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route)}
			PTR	`ip-183-253-57-199.defastlink.net`
		A	211.99.99.52^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
			PTR	`ip-211-99-99-52.defastlink.net`
SOA	`ns1.ename.net`admin@ename.net serial=1751342668

`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.net`nstld@verisign-grs.com serial=1771291435

Same first word

oldbeijing.net

oldbeijing.com

oldbeijing.am

DNS History

18 records (2 active, 16 former)

○NSdns1.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○NSdns2.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○NSdns3.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○NSdns4.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○NSdns5.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○NSdns6.iidns.com2015-07-04 → 2017-01-24 · 4 obs

● 2015-07-04 11:13:00
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

●NSns1.ename.net2026-03-11 → 2026-03-23 · 3 obs

○ 2018-08-17 10:39:02
● 2026-03-11 05:09:10
● 2026-03-23 22:45:48

●NSns2.ename.net2026-03-11 → 2026-03-23 · 3 obs

○ 2018-08-17 10:39:02
● 2026-03-11 05:09:10
● 2026-03-23 22:45:48

○NSns3.dns.com2018-08-17 → 2018-08-17 · 4 obs

○ 2017-01-24 11:54:54
● 2018-08-17 10:39:02
○ 2026-03-11 05:09:10
○ 2026-03-23 22:45:48

○NSns4.dns.com2018-08-17 → 2018-08-17 · 4 obs

○ 2017-01-24 11:54:54
● 2018-08-17 10:39:02
○ 2026-03-11 05:09:10
○ 2026-03-23 22:45:48

○A104.160.182.1322017-01-24 → 2017-01-24 · 4 obs

○ 2016-02-10 01:53:08
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○A104.160.182.1352017-01-24 → 2017-01-24 · 4 obs

○ 2016-02-10 01:53:08
● 2017-01-24 11:54:54
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○A198.148.92.532015-07-04 → 2015-07-04 · 3 obs

● 2015-07-04 11:13:00
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○A198.148.92.562015-07-04 → 2016-02-10 · 4 obs

● 2015-07-04 11:13:00
● 2016-02-10 01:53:08
○ 2017-01-24 11:54:54
○ 2026-03-23 22:45:48

○A198.148.92.572016-02-10 → 2016-02-10 · 4 obs

○ 2015-07-04 11:13:00
● 2016-02-10 01:53:08
○ 2017-01-24 11:54:54
○ 2026-03-23 22:45:48

○A198.148.92.582015-07-04 → 2016-02-10 · 4 obs

● 2015-07-04 11:13:00
● 2016-02-10 01:53:08
○ 2017-01-24 11:54:54
○ 2026-03-23 22:45:48

○A198.148.92.622015-07-04 → 2015-07-04 · 3 obs

● 2015-07-04 11:13:00
○ 2018-08-17 10:39:02
○ 2026-03-23 22:45:48

○CNAMEfw.ename.net2015-07-04 → 2018-08-17 · 7 obs

● 2015-07-04 11:13:00
● 2016-02-10 01:53:08
○ 2016-05-05 05:10:20
● 2017-01-24 11:54:54
● 2018-08-17 10:39:02
○ 2026-03-11 05:09:10
○ 2026-03-23 22:45:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
oldbeijing.com	ns1.ename.net, ns2.ename.net	-

✅ Authoritative Response

Server:218.98.111.173

NS records: ns1.ename.net, ns2.ename.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for oldbeijing.com (unsigned zone)

⏱️ Timing

Total: 1221ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.ename.net, ns2.ename.net`
SOA	1	`ns1.ename.net admin.ename.net`

Analysis

Name Servers

Two name servers ns1.ename.net and ns2.ename.net handle delegation for oldbeijing.com.

oldbeijing.com uses the same name server setup as other domains, for example ttwl.com, kpap.cn, 532222.com, shianbao.com and whhfcy.com.

oldbeijing.com partially shares name servers with other domains; examples include icool.cn, ncu.com.cn, 12385.com, djrq.com.cn and cxyy.cn.

These name servers are often used with the name servers ns3.dns.com and ns4.dns.com.

Host names with four IP numbers: ns2.ename.net points to 240e:97d:10:1402:0:1:0:1005, 1.193.216.198, 183.253.57.199 and 211.99.99.52.

Host names with three IP numbers: ns1.ename.net points to 2001:df2:f080:1::8, 61.158.128.31 and 218.98.111.173.

oldbeijing.com - robtex.com

oldbeijing.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Name Servers

`oldbeijing.com`

`com`