`telegram-tracking.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:8e5a^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:574b^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.87.75^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.142.90^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`eoin.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c56^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eoin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c356^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`eoin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2356^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`eoin.ns.cloudflare.com`
		A	108.162.195.86^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eoin.ns.cloudflare.com`
		A	162.159.44.86^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eoin.ns.cloudflare.com`
		A	172.64.35.86^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eoin.ns.cloudflare.com`
NS	`tegan.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ae2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0e2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`tegan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20e2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`tegan.ns.cloudflare.com`
		A	108.162.192.226^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	172.64.32.226^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	173.245.58.226^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.87.75, 172.67.142.90
		IPv6 hints	2606:4700:3031::ac43:8e5a, 2606:4700:3036::6815:574b
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=127, name=cloudflare-ech.com
SOA	`eoin.ns.cloudflare.com`dns@cloudflare.com serial=2401687071

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

Same first word

telegram-tracking.com

DNS History

6 records (6 active, 0 former)

●NSeoin.ns.cloudflare.com2026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

●NStegan.ns.cloudflare.com2026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

●A104.21.87.752026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

●A172.67.142.902026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

●A2606:4700:3031::ac43:8e5a2026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

●A2606:4700:3036::6815:574b2026-04-03 → 2026-04-14 · 2 obs

● 2026-04-03 14:32:24
● 2026-04-14 21:54:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net...	-
telegram-tracking.com	tegan.ns.cloudflare.com, eoin.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.86

NS records: tegan.ns.cloudflare.com, eoin.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 141ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.87.75, 172.67.142.90`
AAAA	2	`2606:4700:3031::ac43:8e5a, 2606:4700:3036::6815:574b`
NS	2	`eoin.ns.cloudflare.com, tegan.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`eoin.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

telegram-tracking.com points to four IP numbers: 2606:4700:3031::ac43:8e5a, 2606:4700:3036::6815:574b, 104.21.87.75 and 172.67.142.90.

Other host names including mx.xchangefinance.uk, bobancecore.digital, w0tsflfs.sn1rlbucket.ru, hanyiyu.com and w963.com share IP numbers with telegram-tracking.com.

Name Servers

telegram-tracking.com's delegation uses two name servers, eoin.ns.cloudflare.com and tegan.ns.cloudflare.com.

telegram-tracking.com shares the same name server setup as other domains, for example briks.si, ikey.co, gmslotszerkalo.com, swisshousemuine.com and 0594666.com.

telegram-tracking.com at least partially shares name servers with other domains, including blanco-bt.com.ua, wegif.com, dobsongoldberg.com, revealcheating.com and nzra.cn.

these name servers are commonly used with liberty.ns.cloudflare.com, summer.ns.cloudflare.com, malavika.ns.cloudflare.com and arushi.ns.cloudflare.com.

Host names with six IP numbers:

eoin.ns.cloudflare.com points to: 2606:4700:58::a29f:2c56, 2803:f800:50::6ca2:c356, 2a06:98c1:50::ac40:2356, 108.162.195.86, 162.159.44.86 and 172.64.35.86.

tegan.ns.cloudflare.com points to: 2606:4700:50::adf5:3ae2, 2803:f800:50::6ca2:c0e2, 2a06:98c1:50::ac40:20e2, 108.162.192.226, 172.64.32.226 and 173.245.58.226.

telegram-tracking.com - robtex.com