`vipchanel.com`

DNSSEC	⚠️ Not signed
NS	`ali.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a3b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ali.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c03b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ali.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:203b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ali.ns.cloudflare.com`
		A	108.162.192.59^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ali.ns.cloudflare.com`
		A	172.64.32.59^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ali.ns.cloudflare.com`
		A	173.245.58.59^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ali.ns.cloudflare.com`
NS	`newt.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bd4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1d4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`newt.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21d4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`newt.ns.cloudflare.com`
		A	108.162.193.212^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	172.64.33.212^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	173.245.59.212^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽²⁴⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁹⁷⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`ali.ns.cloudflare.com`dns@cloudflare.com serial=2399826643

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

WOT: SUSPICIOUS (1/100)

Subdomains

cf3.vipchanel.com

Same first word

vipchanel.com

Similar names

vipchanle.club

DNS History

9 records (5 active, 4 former)

●NSali.ns.cloudflare.com2026-03-25 → 2026-03-27 · 3 obs

○ 2017-09-21 22:37:02
● 2026-03-25 08:39:26
● 2026-03-27 20:45:40

○NSdns1.idp365.net2015-07-17 → 2017-09-21 · 4 obs

● 2015-07-17 19:22:16
● 2017-09-21 22:37:02
○ 2026-03-25 08:39:26
○ 2026-03-27 20:45:40

○NSdns2.idp365.net2015-07-17 → 2017-09-21 · 4 obs

● 2015-07-17 19:22:16
● 2017-09-21 22:37:02
○ 2026-03-25 08:39:26
○ 2026-03-27 20:45:40

○NSdns3.idp365.net2015-07-17 → 2017-09-21 · 4 obs

● 2015-07-17 19:22:16
● 2017-09-21 22:37:02
○ 2026-03-25 08:39:26
○ 2026-03-27 20:45:40

●NSnewt.ns.cloudflare.com2026-03-25 → 2026-03-27 · 3 obs

○ 2017-09-21 22:37:02
● 2026-03-25 08:39:26
● 2026-03-27 20:45:40

●MXroute1.mx.cloudflare.net2026-03-25 → 2026-03-27 · 2 obs

● 2026-03-25 08:39:26
● 2026-03-27 20:45:40

●MXroute2.mx.cloudflare.net2026-03-25 → 2026-03-27 · 2 obs

● 2026-03-25 08:39:26
● 2026-03-27 20:45:40

●MXroute3.mx.cloudflare.net2026-03-25 → 2026-03-27 · 2 obs

● 2026-03-25 08:39:26
● 2026-03-27 20:45:40

○A31.3.65.302015-07-17 → 2017-09-21 · 4 obs

● 2015-07-17 19:22:16
● 2017-09-21 22:37:02
○ 2026-03-25 08:39:26
○ 2026-03-27 20:45:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
vipchanel.com	ali.ns.cloudflare.com, newt.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.59

NS records: ali.ns.cloudflare.com, newt.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vipchanel.com (unsigned zone)

⏱️ Timing

Total: 174ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ali.ns.cloudflare.com, newt.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 14), route1.mx.cloudflare.net (pri: 24)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`ali.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

Hierarchy

vipchanel.com is the parent of cf3.vipchanel.com.

Name Servers

vipchanel.com is delegated to two name servers ali.ns.cloudflare.com and newt.ns.cloudflare.com.

vipchanel.com shares the same name server setup as other domains, for instance zonwo.com, woo.pe, jtfgov.com, bostonleather.com and ioniamarketing.com.

vipchanel.com at least partially shares name servers with other domains, for instance trustradio.com.ng, morad-edwar.com, fernandaramosstore.com.br, edge.org and conexionchubb.com.

These name servers are commonly used with matteo.ns.cloudflare.com, earl.ns.cloudflare.com and alina.ns.cloudflare.com.

Host names with six IP numbers:

Host name ali.ns.cloudflare.com points to: 2606:4700:50::adf5:3a3b, 2803:f800:50::6ca2:c03b, 2a06:98c1:50::ac40:203b, 108.162.192.59, 172.64.32.59 and 173.245.58.59.

Host name newt.ns.cloudflare.com points to: 2606:4700:58::adf5:3bd4, 2803:f800:50::6ca2:c1d4, 2a06:98c1:50::ac40:21d4, 108.162.193.212, 172.64.33.212 and 173.245.59.212.

Mail Servers

vipchanel.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

vipchanel.com shares some mail servers with other domains, at least partially, for instance hoopties.com, adverttracker.top, tiedcuffed.com, sa-mp.co.id and legitbabes.com.

Host names with six IP numbers:

Host name route1.mx.cloudflare.net points to: 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

Host name route2.mx.cloudflare.net points to: 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

Host name route3.mx.cloudflare.net points to: 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

vipchanel.com - robtex.com

vipchanel.com

com

Subdomains

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Hierarchy

Name Servers

Mail Servers

`vipchanel.com`

`com`