`telegram-kk.com.cn`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:1a39^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:a839^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.26.57^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.168.57^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chan.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a52^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c052^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2052^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chan.ns.cloudflare.com`
		A	108.162.192.82^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	172.64.32.82^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	173.245.58.82^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
NS	`dilbert.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b9b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dilbert.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c19b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`dilbert.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:219b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`dilbert.ns.cloudflare.com`
		A	108.162.193.155^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dilbert.ns.cloudflare.com`
		A	172.64.33.155^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dilbert.ns.cloudflare.com`
		A	173.245.59.155^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dilbert.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.26.57, 172.67.168.57
		IPv6 hints	2606:4700:3031::6815:1a39, 2606:4700:3037::ac43:a839
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=80, name=cloudflare-ech.com
SOA	`chan.ns.cloudflare.com`dns@cloudflare.com serial=2402532883

`com.cn`

	DNSSEC	⚠️ Not signed
	NS	`a.dns.cn` ⭐ ⚠️ Not in parent delegation
	NS	`b.dns.cn` ⚠️ Not in parent delegation
	NS	`c.dns.cn` ⚠️ Not in parent delegation
	NS	`cns.cernet.net` ⚠️ Not in parent delegation
	NS	`d.dns.cn` ⚠️ Not in parent delegation
	NS	`e.dns.cn` ⚠️ Not in parent delegation
	SOA	`a.dns.cn`root@cnnic.cn serial=2030558712

⚠️ On DNS blocklist: tif
WOT: NOT_SAFE (20/100)

Same first word

telegram-kk.com.cn

DNS History

6 records (6 active, 0 former)

●NSchan.ns.cloudflare.com2026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

●NSdilbert.ns.cloudflare.com2026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

●A104.21.26.572026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

●A172.67.168.572026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

●A2606:4700:3031::6815:1a392026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

●A2606:4700:3037::ac43:a8392026-04-17 → 2026-05-09 · 2 obs

● 2026-04-17 00:29:36
● 2026-05-09 20:35:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cn	e.dns.cn, a.dns.cn, c.dns.cn, d.dns.cn...	-
telegram-kk.com.cn	chan.ns.cloudflare.com, dilbert.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.59.155

NS records: chan.ns.cloudflare.com, dilbert.ns.cloudflare.com

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at telegram-kk.com.cn: Error: DNS query timeout: 203.119.29.1 for DS telegram-kk.com.cn

⏱️ Timing

Total: 3747ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.26.57, 172.67.168.57`
AAAA	2	`2606:4700:3037::ac43:a839, 2606:4700:3031::6815:1a39`
NS	2	`chan.ns.cloudflare.com, dilbert.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`chan.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

telegram-kk.com.cn points to four IP numbers: 2606:4700:3031::6815:1a39, 2606:4700:3037::ac43:a839, 104.21.26.57 and 172.67.168.57.

Other host names, for instance fate.windada.com, cantonchiro.com, surrey.co.uk, www.lamyamerica.com and z999.info share IP numbers with telegram-kk.com.cn.

Name Servers

telegram-kk.com.cn is delegated to two name servers: chan.ns.cloudflare.com and dilbert.ns.cloudflare.com.

telegram-kk.com.cn uses the same name server setup as other domains, for instance nakhly.info, datasoftperu.com, lezgetreal.com, yifanyi-kk.com.cn and yifanyi1.com.cn.

telegram-kk.com.cn shares name servers with other domains at least partially, for instance operno.com, ssyanan.com, immutableazopt-ai.net, absolutechiropracticmassage.com and iraqtechno.com.

these name servers are often used with doug.ns.cloudflare.com, theo.ns.cloudflare.com and merlin.ns.cloudflare.com.

Host names with six IP numbers: chan.ns.cloudflare.com points to 2606:4700:50::adf5:3a52, 2803:f800:50::6ca2:c052, 2a06:98c1:50::ac40:2052, 108.162.192.82, 172.64.32.82 and 173.245.58.82; dilbert.ns.cloudflare.com points to 2606:4700:58::adf5:3b9b, 2803:f800:50::6ca2:c19b, 2a06:98c1:50::ac40:219b, 108.162.193.155, 172.64.33.155 and 173.245.59.155.

telegram-kk.com.cn - robtex.com