`linkedkeeper.com`

DNSSEC	⚠️ Not signed
A	203.107.60.192^{🇨🇳 Alibaba-Cloud}
NS	`vip1.alidns.com` ⭐
		A	2408:4009:500::1^{🇨🇳 Alibaba-Cloud}
		A	8.212.93.1^{🇭🇰 Alibaba_Cloud_SEC}
		A	140.205.1.1^{🇨🇳 Alibaba-Cloud}
		A	170.33.32.208^{🇸🇬 Alibaba_Cloud_SEC}
		A	170.33.73.24^{🇸🇬 Alibaba_Cloud_SEC}
		A	170.33.80.8^{🇸🇬 Alibaba_Cloud_SEC}
NS	`vip2.alidns.com`
		A	2408:4009:500::2^{🇨🇳 Alibaba-Cloud}
		A	8.212.93.2^{🇭🇰 Alibaba_Cloud_SEC}
		A	140.205.1.2^{🇨🇳 Alibaba-Cloud}
		A	170.33.32.209^{🇸🇬 Alibaba_Cloud_SEC}
		A	170.33.73.25^{🇸🇬 Alibaba_Cloud_SEC}
		A	170.33.80.9^{🇸🇬 Alibaba_Cloud_SEC}
SOA	`vip1.alidns.com`hostmaster@hichina.com 2025-12-10 #11

`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

linkedkeeper.com

DNS History

8 records (3 active, 5 former)

○NSdns10.hichina.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 17:16:40
○ 2018-01-15 18:31:16
○ 2026-02-21 07:55:04

○NSdns9.hichina.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 17:16:40
○ 2018-01-15 18:31:16
○ 2026-02-21 07:55:04

●NSvip1.alidns.com2018-01-15 → 2026-02-21 · 3 obs

○ 2016-12-15 17:16:40
● 2018-01-15 18:31:16
● 2026-02-21 07:55:04

●NSvip2.alidns.com2018-01-15 → 2026-02-21 · 3 obs

○ 2016-12-15 17:16:40
● 2018-01-15 18:31:16
● 2026-02-21 07:55:04

●A203.107.60.1922026-02-21 → 2026-02-21 · 3 obs

○ 2018-01-15 18:31:16
● 2026-02-21 07:55:02
● 2026-02-21 07:55:04

○A220.181.105.2252016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 17:16:40
○ 2018-01-15 18:31:16
○ 2026-02-21 07:55:04

○CNAME1119715872211027.cn-beijing.fc.aliyuncs.com2026-02-21 → 2026-02-21 · 2 obs

○ 2026-02-21 07:55:02
○ 2026-02-21 07:55:04

○CNAMElinkedkeeper.com.w.kunlunno.com2016-12-15 → 2018-01-15 · 4 obs

● 2016-12-15 17:16:40
● 2018-01-15 18:31:16
○ 2026-02-21 07:55:02
○ 2026-02-21 07:55:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
linkedkeeper.com	vip1.alidns.com, vip2.alidns.com	20 records

✅ Authoritative Response

Server: 121.40.6.162

NS records: vip1.alidns.com, vip2.alidns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedkeeper.com (unsigned zone)

⏱️ Timing

Total: 479ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`203.107.60.192`
NS	2	`vip1.alidns.com, vip2.alidns.com`
SOA	1	`vip1.alidns.com hostmaster.hichina.com`

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (vip1.alidns.com, vip1.alidns.com, vip1.alidns.com...)

AI analysis

linkedkeeper.com points to an IP address: 203.107.60.192.

other host names include lanstar.net, weile.com, www.wgine.com, www.dangbei.net and miaovps.com; they share IP numbers with linkedkeeper.com.

Two name servers vip1.alidns.com and vip2.alidns.com handle the delegation for linkedkeeper.com.

linkedkeeper.com shares the same name server setup as other domains, for instance edu8.com.cn, yutangkeji.com, 2012jh.com, insnail.com and gtm-a1b5.com.

linkedkeeper.com at least partially shares name servers with other domains, for instance dian.so, pzhccb.com, aduer.com, jinchutou.com and kuangdacn.com.

These name servers are commonly used with vip3.alidns.com and vip4.alidns.com.

Six IP addresses per host:

vip1.alidns.com points to 2408:4009:500::1, 8.212.93.1, 140.205.1.1, 170.33.32.208, 170.33.73.24 and 170.33.80.8; vip2.alidns.com points to 2408:4009:500::2, 8.212.93.2, 140.205.1.2, 170.33.32.209, 170.33.73.25 and 170.33.80.9

linkedkeeper.com - robtex.com