`telegram-leads.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:146b^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::ac43:c059^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.20.107^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.192.89^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`johnathan.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c2c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`johnathan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c32c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`johnathan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:232c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`johnathan.ns.cloudflare.com`
		A	108.162.195.44^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`johnathan.ns.cloudflare.com`
		A	162.159.44.44^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`johnathan.ns.cloudflare.com`
		A	172.64.35.44^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`johnathan.ns.cloudflare.com`
NS	`nia.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ad2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nia.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0d2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`nia.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20d2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`nia.ns.cloudflare.com`
		A	108.162.192.210^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nia.ns.cloudflare.com`
		A	172.64.32.210^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nia.ns.cloudflare.com`
		A	173.245.58.210^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nia.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.20.107, 172.67.192.89
		IPv6 hints	2606:4700:3032::6815:146b, 2606:4700:3035::ac43:c059
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=146, name=cloudflare-ech.com
SOA	`johnathan.ns.cloudflare.com`dns@cloudflare.com serial=2400144909

`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=1775194267

⚠️ On DNS blocklist: light, multi, pro, pro.plus, tif, ultimate

Same first word

telegram-leads.com

Similar names

leads-telegram.ru

DNS History

6 records (6 active, 0 former)

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

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

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

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

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

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

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

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

●A2606:4700:3032::6815:146b2026-04-01 → 2026-04-03 · 2 obs

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

●A2606:4700:3035::ac43:c0592026-04-01 → 2026-04-03 · 2 obs

● 2026-04-01 18:57:52
● 2026-04-03 05:37:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net...	-
telegram-leads.com	nia.ns.cloudflare.com, johnathan.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.44

NS records: nia.ns.cloudflare.com, johnathan.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 116ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.192.89, 104.21.20.107`
AAAA	2	`2606:4700:3035::ac43:c059, 2606:4700:3032::6815:146b`
NS	2	`johnathan.ns.cloudflare.com, nia.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`johnathan.ns.cloudflare.com dns.cloudfla`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

telegram-leads.com maps to four IP numbers: 2606:4700:3032::6815:146b, 2606:4700:3035::ac43:c059, 104.21.20.107 and 172.67.192.89.

other host names include ezp93.com, risf.net, wsdylsb.com, esque.ca and www.anshunkang.com; they share IP numbers with telegram-leads.com.

Name Servers

Two name servers johnathan.ns.cloudflare.com and nia.ns.cloudflare.com handle the delegation for telegram-leads.com.

telegram-leads.com shares the same name server setup as other domains, for instance tellworks.com, bpcine.com, bp3.us, allahwireless.com and dayogroup.com.

telegram-leads.com at least partially shares name servers with other domains, for instance arrayrise.com, calenerium.sbs, meteopoble.com, 0791llt.com and d54.me.

These name servers are commonly used alongside emely.ns.cloudflare.com.

Six IP addresses per host:

johnathan.ns.cloudflare.com points to 2606:4700:58::a29f:2c2c, 2803:f800:50::6ca2:c32c, 2a06:98c1:50::ac40:232c, 108.162.195.44, 162.159.44.44 and 172.64.35.44; nia.ns.cloudflare.com points to 2606:4700:50::adf5:3ad2, 2803:f800:50::6ca2:c0d2, 2a06:98c1:50::ac40:20d2, 108.162.192.210, 172.64.32.210 and 173.245.58.210

telegram-leads.com - robtex.com