`telegram-assistant.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:3ba^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:8318^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.3.186^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.131.24^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ainsley.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26d3^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2d3^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ainsley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22d3^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ainsley.ns.cloudflare.com`
		A	108.162.194.211^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	162.159.38.211^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	172.64.34.211^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
NS	`zahir.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c91^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zahir.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c391^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`zahir.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2391^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`zahir.ns.cloudflare.com`
		A	108.162.195.145^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zahir.ns.cloudflare.com`
		A	162.159.44.145^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zahir.ns.cloudflare.com`
		A	172.64.35.145^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zahir.ns.cloudflare.com`
MX	`mx1.qiye.aliyun.com` ⭐
		A	47.246.137.47^{🇺🇸 Alibaba-Cloud47.246.136.0/22 Alibaba CLoud}
MX	`mx2.qiye.aliyun.com`⁽¹⁰⁾
		A	47.246.136.231^{🇺🇸 Alibaba-Cloud47.246.136.0/22 Alibaba CLoud}
			PTR	`cz-clare.com`
			PTR	`reachsmartdwell.com`
			PTR	`wevolt.tech`
MX	`mx3.qiye.aliyun.com`⁽¹⁵⁾
		A	47.246.136.231^{🇺🇸 Alibaba-Cloud47.246.136.0/22 Alibaba CLoud}
			PTR	`cz-clare.com`
			PTR	`reachsmartdwell.com`
			PTR	`wevolt.tech`
		A	47.246.137.47^{🇺🇸 Alibaba-Cloud47.246.136.0/22 Alibaba CLoud}
TXT	`v=spf1 include:spf.qiye.aliyun.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.3.186, 172.67.131.24
		IPv6 hints	2606:4700:3035::6815:3ba, 2606:4700:3037::ac43:8318
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=252, name=cloudflare-ech.com
SOA	`ainsley.ns.cloudflare.com`dns@cloudflare.com serial=2410608829

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

⚠️ On DNS blocklist: tif

Same first word

telegram-assistant.com

telegram-assistant.site

Similar names

assistant-telegram.com

assistant-telegram.online

assistant-telegram.ru

DNS History

9 records (9 active, 0 former)

●NSainsley.ns.cloudflare.com2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●NSzahir.ns.cloudflare.com2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●MXmx1.qiye.aliyun.com2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●MXmx2.qiye.aliyun.com2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●MXmx3.qiye.aliyun.com2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●A104.21.3.1862026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●A172.67.131.242026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●A2606:4700:3035::6815:3ba2026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

●A2606:4700:3037::ac43:83182026-07-27 → 2026-07-28 · 2 obs

● 2026-07-27 13:01:00
● 2026-07-28 00:57:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net...	-
telegram-assistant.com	ainsley.ns.cloudflare.com, zahir.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.145

NS records: ainsley.ns.cloudflare.com, zahir.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 1358ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.131.24, 104.21.3.186`
AAAA	2	`2606:4700:3035::6815:3ba, 2606:4700:3037::ac43:8318`
NS	2	`ainsley.ns.cloudflare.com, zahir.ns.cloudflare.com`
MX	3	`mx2.qiye.aliyun.com (pri: 10), mx3.qiye.aliyun.com (pri: 15)...`
TXT	1	`v=spf1 include:spf.qiye.aliyun.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ainsley.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

telegram-assistant.com points to the four IP addresses 104.21.3.186, 172.67.131.24, 2606:4700:3035::6815:3ba and 2606:4700:3037::ac43:8318.

rainniel.com, sso.291235.xyz, monstermegs.com and two other host names share IP numbers with telegram-assistant.com.

Name Servers

Two name servers handle the delegation for telegram-assistant.com: ainsley.ns.cloudflare.com and zahir.ns.cloudflare.com.

telegram-assistant.com uses the same name servers as several other domains — among them logisticus.com.br, mariana-noreply-sp1100879.pages.dev, exel-int.com and two more.

The name servers of telegram-assistant.com overlap at least partially with those of other domains — among them casino-action-day-nz.com, cinemaflix.org, 963144.com and two more.

These name servers commonly co-occur with the name servers alfred.ns.cloudflare.com, nelci.ns.cloudflare.com, liz.ns.cloudflare.com and henry.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

ainsley.ns.cloudflare.com resolves to 108.162.194.211, 162.159.38.211 and 172.64.34.211 among others, with 3 other IP addresses in total.

zahir.ns.cloudflare.com resolves to 108.162.195.145, 162.159.44.145 and 172.64.35.145 among others, with 3 other IP addresses in total.

Mail Servers

Mail for telegram-assistant.com is routed through three mail servers — mx1.qiye.aliyun.com, mx2.qiye.aliyun.com and mx3.qiye.aliyun.com.

telegram-assistant.com has at least partial mail server overlap with other domains such as unibrom.cn, passfab.jp, sciscanpub.com and two more.

The mail servers mxn.mxhichina.com and mxw.mxhichina.com are commonly paired with these mail servers.

Hostnames that resolve to two IP addresses:

mx3.qiye.aliyun.com resolves to two addresses: 47.246.136.231 and 47.246.137.47.

Hosts with just one IP address:

The hostname mx1.qiye.aliyun.com resolves to 47.246.137.47.

The hostname mx2.qiye.aliyun.com resolves to 47.246.136.231.

mx3.qiye.aliyun.com along with mx2.qiye.aliyun.com each resolve to 47.246.136.231 IP addresses.

mx3.qiye.aliyun.com along with mx1.qiye.aliyun.com each resolve to 47.246.137.47 IP addresses.