`telegram-layeron.top`

DNSSEC	⚠️ Not signed
A	85.137.55.21
		PTR	`dedicated.vsys.host`
NS	`ns1.dnsowl.com` ⭐
		A	2400:cb00:2049:1::a29f:1a88^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1bad^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.136^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.173^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1a31^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b82^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.49^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.130^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns3.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1aea^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b62^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.234^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.98^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.dnsowl.com`hostmaster@dnsowl.com serial=1775938427

`top`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.zdnscloud.com` ⭐
	NS	`a.zdnscloud.cn`
	NS	`b.zdnscloud.cn`
	NS	`c.zdnscloud.com`
	NS	`d.zdnscloud.com`
	NS	`e.zdnscloud.cn`
	NS	`f.zdnscloud.cn`
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-05-14_13:05:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1395807828

⚠️ On DNS blocklist: tif

Subdomains

www.telegram-layeron.top

Same first word

telegram-layeron.top

DNS History

4 records (4 active, 0 former)

●NSns1.dnsowl.com2026-04-14 → 2026-05-14 · 2 obs

● 2026-04-14 19:23:22
● 2026-05-14 05:13:40

●NSns2.dnsowl.com2026-04-14 → 2026-05-14 · 2 obs

● 2026-04-14 19:23:22
● 2026-05-14 05:13:40

●NSns3.dnsowl.com2026-04-14 → 2026-05-14 · 2 obs

● 2026-04-14 19:23:22
● 2026-05-14 05:13:40

●A85.137.55.212026-04-14 → 2026-05-14 · 2 obs

● 2026-04-14 19:23:22
● 2026-05-14 05:13:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com...	-
telegram-layeron.top	ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com	-

✅ Authoritative Response

Server:162.159.26.136

NS records: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for telegram-layeron.top (unsigned zone)

⏱️ Timing

Total: 528ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`85.137.55.21`
NS	3	`ns1.dnsowl.com, ns2.dnsowl.com...`
SOA	1	`ns1.dnsowl.com hostmaster.dnsowl.com`

Analysis

Hierarchy

www.telegram-layeron.top is a child of telegram-layeron.top.

IP Addresses

telegram-layeron.top resolves to one IP number: 85.137.55.21.

Other host names, for example www.telegram-layeron.top, share IP numbers with telegram-layeron.top.

Name Servers

telegram-layeron.top is delegated to three name servers: ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

telegram-layeron.top at least partially shares name servers with other domains, including gzhuaji.com, samuithailand.com, pcgnews.com, dingding22.org and aboutcasinogambling.com.

Host names with four IP numbers:

ns1.dnsowl.com points to 2400:cb00:2049:1::a29f:1a88, 2400:cb00:2049:1::a29f:1bad, 162.159.26.136 and 162.159.27.173.

ns2.dnsowl.com points to 2400:cb00:2049:1::a29f:1a31, 2400:cb00:2049:1::a29f:1b82, 162.159.26.49 and 162.159.27.130.

ns3.dnsowl.com points to 2400:cb00:2049:1::a29f:1aea, 2400:cb00:2049:1::a29f:1b62, 162.159.26.234 and 162.159.27.98.

telegram-layeron.top - robtex.com