`vpn-telegram.click`

DNSSEC	⚠️ Not signed
A	148.135.207.163^{🇺🇸 DeluxHost148.135.207.0/24}
		PTR	`static.148.135.207.163.deluxhost.net`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@vpn-telegram.click 2026-02-11 #1

`click`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1776169119

Same first word

vpn-telegram.club

vpn-telegram.click

vpn-telegram.com

Similar names

telegram-vpn.com

telegram-vpn.top

telegram-vpn.fun

telegram-vpn.space

DNS History

3 records (3 active, 0 former)

●NSns1.dyna-ns.net2026-03-08 → 2026-04-14 · 2 obs

● 2026-03-08 01:41:08
● 2026-04-14 12:48:06

●NSns2.dyna-ns.net2026-03-08 → 2026-04-14 · 2 obs

● 2026-03-08 01:41:08
● 2026-04-14 12:48:06

●A148.135.207.1632026-03-08 → 2026-04-14 · 2 obs

● 2026-03-08 01:41:08
● 2026-04-14 12:48:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
click	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
vpn-telegram.click	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.25.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vpn-telegram.click (unsigned zone)

⏱️ Timing

Total: 326ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`148.135.207.163`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.vpn-telegram.`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)

Analysis

IP Addresses

vpn-telegram.click resolves to one IP number: 148.135.207.163.

Name Servers

vpn-telegram.click is delegated to two name servers ns1.dyna-ns.net and ns2.dyna-ns.net.

vpn-telegram.click shares the same name server setup as other domains, for instance cirqueros.com, startslow.com, desiserials.co, landingpage.net and shainajoy.com.

Host names with four IP numbers: ns1.dyna-ns.net points to 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158; ns2.dyna-ns.net points to 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.

vpn-telegram.click - robtex.com