`telegram-tran.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::ac43:bb4a^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::6815:50dd^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.80.221^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.187.74^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
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`
NS	`naya.ns.cloudflare.com`
		A	2606:4700:50::a29f:26f2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`naya.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2f2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`naya.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22f2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`naya.ns.cloudflare.com`
		A	108.162.194.242^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`naya.ns.cloudflare.com`
		A	162.159.38.242^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`naya.ns.cloudflare.com`
		A	172.64.34.242^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`naya.ns.cloudflare.com`
TXT	`google-site-verification=TewqsdLZmzFKjEpE6LJB3zAfcF56aw0kVDJ8NHe3prU`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.80.221, 172.67.187.74
		IPv6	2606:4700:3032::ac43:bb4a, 2606:4700:3035::6815:50dd
SOA	`dilbert.ns.cloudflare.com`dns@cloudflare.com serial=2396817875

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1775081112

⚠️ On DNS blocklist: tif

Same first word

telegram-tran.com

DNS History

6 records (6 active, 0 former)

●NSdilbert.ns.cloudflare.com2026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

●NSnaya.ns.cloudflare.com2026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

●A104.21.80.2212026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

●A172.67.187.742026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

●A2606:4700:3032::ac43:bb4a2026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

●A2606:4700:3035::6815:50dd2026-03-22 → 2026-04-01 · 2 obs

● 2026-03-22 06:18:08
● 2026-04-01 22:07:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
telegram-tran.com	dilbert.ns.cloudflare.com, naya.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.242

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for telegram-tran.com (unsigned zone)

⏱️ Timing

Total: 106ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.80.221, 172.67.187.74`
AAAA	2	`2606:4700:3035::6815:50dd, 2606:4700:3032::ac43:bb4a`
NS	2	`dilbert.ns.cloudflare.com, naya.ns.cloudflare.com`
TXT	1	`google-site-verification=TewqsdLZmzFKjEp`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`dilbert.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (dilbert.ns.cloudflare.com, dilbert.ns.cloudflare.com, dilbert.ns.cloudflare.com...)

Analysis

IP Addresses

telegram-tran.com resolves to four IPs: 2606:4700:3032::ac43:bb4a, 2606:4700:3035::6815:50dd, 104.21.80.221 and 172.67.187.74.

Other host names, for instance 775430.xyz, pandagardenexpress.com, 3656best.cc, lativ36resources.click and saluempire.com share IP numbers with telegram-tran.com.

Name Servers

telegram-tran.com has two name servers: dilbert.ns.cloudflare.com and naya.ns.cloudflare.com.

telegram-tran.com shares the same name server setup as other domains, for example nycrgb.org, cdns-free.com, phim(0x736578)moi.net, vl(0x786e7878).net and shuk.li.

telegram-tran.com shares some name servers with other domains, for example vitoagd.pl, expend.com.tw, hsdsolution.com, szjoywing.com and pgame.nl.

These name servers are commonly used with the name servers ashton.ns.cloudflare.com.

Host names with six IP numbers: 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; naya.ns.cloudflare.com points to: 2606:4700:50::a29f:26f2, 2803:f800:50::6ca2:c2f2, 2a06:98c1:50::ac40:22f2, 108.162.194.242, 162.159.38.242 and 172.64.34.242.

telegram-tran.com - robtex.com