`telegram-securinx.top`

DNSSEC	⚠️ Not signed
A	85.137.54.58
		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=1775937457

`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-07-22_02:55:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1396521770

Subdomains

www.telegram-securinx.top

Same first word

telegram-securinx.top

DNS History

4 records (4 active, 0 former)

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

● 2026-04-14 21:35:24
● 2026-07-21 19:00:24

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

● 2026-04-14 21:35:24
● 2026-07-21 19:00:24

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

● 2026-04-14 21:35:24
● 2026-07-21 19:00:24

●A85.137.54.582026-04-14 → 2026-07-21 · 2 obs

● 2026-04-14 21:35:24
● 2026-07-21 19:00:24

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:162.159.26.234

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 803ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com...)

Analysis

Hierarchy

telegram-securinx.top serves as the parent of www.telegram-securinx.top.

IP Addresses

telegram-securinx.top directs to one IP number, which is 85.137.54.58.

There are other host names — www.telegram-securinx.top among them — that share IP numbers with telegram-securinx.top.

Name Servers

DNS for telegram-securinx.top is handled by three authoritative name servers: ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

telegram-securinx.top has at least partial name server overlap with other domains, such as ipv4addressbroker.com, algarr.com, 028xpj.com and two others.

Each of the hostnames ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com directs to four IP numbers. ns1.dnsowl.com has IP addresses 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad. ns2.dnsowl.com has IP addresses 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82. ns3.dnsowl.com has IP addresses 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.

telegram-securinx.top - robtex.com