`travelchamnel.com`

DNSSEC	⚠️ Not signed
A	100.103.200.40
NS	`ns1.nexcess.net` ⭐
		A	2607:f7c0:8001::a^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.188^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns2.nexcess.net` ⚠️ Not in parent delegation
		A	2607:f7c0:8002::a^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.166^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns3.nexcess.net`
		A	2607:f7c0:8001::b^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.144^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns4.nexcess.net` ⚠️ Not in parent delegation
		A	2607:f7c0:8002::b^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.122^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
SOA	`ns1.nexcess.net`hostmaster@travelchamnel.com serial=1750428709

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

⚠️ On DNS blocklist: tif

Same first word

travelchamnel.com

DNS History

5 records (5 active, 0 former)

●NSns1.nexcess.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 16:57:06
● 2026-04-14 14:43:42

●NSns2.nexcess.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 16:57:06
● 2026-04-14 14:43:42

●NSns3.nexcess.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 16:57:06
● 2026-04-14 14:43:42

●NSns4.nexcess.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 16:57:06
● 2026-04-14 14:43:42

●A100.103.200.402026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 16:57:06
● 2026-04-14 14:43:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net...	-
travelchamnel.com	ns1.nexcess.net, ns3.nexcess.net	-

✅ Authoritative Response

Server:192.240.188.144

NS records: ns1.nexcess.net, ns3.nexcess.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for travelchamnel.com (unsigned zone)

⏱️ Timing

Total: 199ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`100.103.200.40`
NS	4	`ns1.nexcess.net, ns4.nexcess.net...`
SOA	1	`ns1.nexcess.net hostmaster.travelchamnel`

Analysis

IP Addresses

travelchamnel.com points to a single IP number: 100.103.200.40.

other host names for instance hickorycabinets.org, trueservicespro.com, weddingbandsbuy.com, themortgageadvisorguy.com and worldofpoppers.com share IP numbers with travelchamnel.com.

Name Servers

travelchamnel.com is delegated to four name servers: ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net and ns4.nexcess.net.

travelchamnel.com at least partially shares name servers with other domains, for instance discovervaldezalaska.org, callsummitservices.com, patriotguard.org, ollz.com and 123telephones.com.

These name servers are commonly used with ns5.nexcess.net, ns6.nexcess.net, ns7.nexcess.net and ns8.nexcess.net.

Host names with two IP numbers:

Host name ns1.nexcess.net points to: 2607:f7c0:8001::a and 192.240.188.188.

Host name ns2.nexcess.net points to: 2607:f7c0:8002::a and 192.240.188.166.

Host name ns3.nexcess.net points to: 2607:f7c0:8001::b and 192.240.188.144.

Host name ns4.nexcess.net points to: 2607:f7c0:8002::b and 192.240.188.122.

travelchamnel.com - robtex.com