`telegram-bitryx.top`

DNSSEC	⚠️ Not signed
A	85.137.54.69
		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=1775937646

`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-30_16:55:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1396606415

Subdomains

www.telegram-bitryx.top

Same first word

telegram-bitryx.top

DNS History

4 records (4 active, 0 former)

●NSns1.dnsowl.com2026-04-15 → 2026-07-30 · 2 obs

● 2026-04-15 09:31:28
● 2026-07-30 09:00:14

●NSns2.dnsowl.com2026-04-15 → 2026-07-30 · 2 obs

● 2026-04-15 09:31:28
● 2026-07-30 09:00:14

●NSns3.dnsowl.com2026-04-15 → 2026-07-30 · 2 obs

● 2026-04-15 09:31:28
● 2026-07-30 09:00:14

●A85.137.54.692026-04-15 → 2026-07-30 · 2 obs

● 2026-04-15 09:31:28
● 2026-07-30 09:00:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	b.zdnscloud.cn, d.zdnscloud.com, j.zdnscloud.com, f.zdnscloud.cn...	-
telegram-bitryx.top	ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com	-

✅ Authoritative Response

Server:162.159.27.98

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 349ms | Queries: -

📄 Records

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

Analysis

Hierarchy

www.telegram-bitryx.top is a subdomain of telegram-bitryx.top.

IP Addresses

telegram-bitryx.top has exactly one IP address — 85.137.54.69.

www.telegram-bitryx.top is an example of another host name that shares IP numbers with telegram-bitryx.top.

Name Servers

telegram-bitryx.top has three name servers — ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

The name servers of telegram-bitryx.top overlap at least partially with those of other domains — among them fakup.com, office707.com, wallet-coinbase.net and two more.

The hosts ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com each resolve to four IP addresses. ns1.dnsowl.com points to 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad. ns2.dnsowl.com points to 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82. ns3.dnsowl.com points to 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.

telegram-bitryx.top - robtex.com