freightchannel.com - dns.ninja

`freightchannel.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3036::6815:2aa2^{Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:a389^{Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.42.162^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.163.137^{Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`aspen.ns.cloudflare.com` ⭐
NS	`gordon.ns.cloudflare.com`
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`
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`
TXT	`google-site-verification=YY_NqE2RyyAKA84Lib3XGQgaOqlHicq_75KM4vmy5ns`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.42.162, 172.67.163.137
		IPv6 hints	2606:4700:3036::6815:2aa2, 2606:4700:3036::ac43:a389
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=197, name=cloudflare-ech.com
SOA	`aspen.ns.cloudflare.com`dns@cloudflare.com serial=2407370662

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

Previously MX for

freightchannel.com

Same first word

freightchannel.com

Similar names

channelfreight.co.za

fighterchannel.com

DNS History

22 records (9 active, 13 former)

●NSaspen.ns.cloudflare.com2026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

●NSgordon.ns.cloudflare.com2026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

○NSns1.atom.com2026-02-15 → 2026-02-27 · 5 obs

○ 2017-05-16 01:15:50
● 2026-02-15 03:04:58
● 2026-02-27 12:29:48
○ 2026-04-28 21:52:14
○ 2026-06-25 05:30:54

○NSns1.ifund.com2015-10-21 → 2016-03-19 · 5 obs

○ 2015-05-23 18:13:44
● 2015-10-21 15:05:48
● 2016-03-19 14:19:26
○ 2017-05-16 01:15:50
○ 2026-06-25 05:30:54

○NSns1.srv1-whm.ifund.com2015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 18:13:44
○ 2015-10-21 15:05:48
○ 2026-06-25 05:30:54

○NSns2.atom.com2026-02-15 → 2026-02-27 · 5 obs

○ 2017-05-16 01:15:50
● 2026-02-15 03:04:58
● 2026-02-27 12:29:48
○ 2026-04-28 21:52:14
○ 2026-06-25 05:30:54

○NSns2.ifund.com2015-10-21 → 2016-03-19 · 5 obs

○ 2015-05-23 18:13:44
● 2015-10-21 15:05:48
● 2016-03-19 14:19:26
○ 2017-05-16 01:15:50
○ 2026-06-25 05:30:54

○NSns2.srv1-whm.ifund.com2015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 18:13:44
○ 2015-10-21 15:05:48
○ 2026-06-25 05:30:54

○NSns5.serviceport.com2017-05-16 → 2017-05-16 · 4 obs

○ 2016-03-19 14:19:26
● 2017-05-16 01:15:50
○ 2026-02-15 03:04:58
○ 2026-06-25 05:30:54

○NSns6.serviceport.com2017-05-16 → 2017-05-16 · 4 obs

○ 2016-03-19 14:19:26
● 2017-05-16 01:15:50
○ 2026-02-15 03:04:58
○ 2026-06-25 05:30:54

○MXfreightchannel.com2015-05-23 → 2026-02-15 · 4 obs

● 2015-05-23 18:13:44
● 2026-02-15 03:04:58
○ 2026-02-18 06:00:34
○ 2026-06-25 05:30:54

●MXroute1.mx.cloudflare.net2026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-18 06:00:34
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

●MXroute2.mx.cloudflare.net2026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-18 06:00:34
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

●MXroute3.mx.cloudflare.net2026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-18 06:00:34
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

○A104.130.192.1372015-10-21 → 2016-03-19 · 5 obs

○ 2015-05-23 18:13:44
● 2015-10-21 15:05:48
● 2016-03-19 14:19:26
○ 2017-05-16 01:15:50
○ 2026-06-25 05:30:54

●A104.21.42.1622026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

●A172.67.163.1372026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

○A23.253.37.822015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 18:13:44
○ 2015-10-21 15:05:48
○ 2026-06-25 05:30:54

●A2606:4700:3036::6815:2aa22026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

●A2606:4700:3036::ac43:a3892026-04-28 → 2026-06-25 · 3 obs

○ 2026-02-27 12:29:48
● 2026-04-28 21:52:14
● 2026-06-25 05:30:54

○A52.20.84.622026-02-15 → 2026-02-27 · 5 obs

○ 2017-05-16 01:15:50
● 2026-02-15 03:04:58
● 2026-02-27 12:29:48
○ 2026-04-28 21:52:14
○ 2026-06-25 05:30:54

○A52.89.84.2452017-05-16 → 2017-05-16 · 4 obs

○ 2016-03-19 14:19:26
● 2017-05-16 01:15:50
○ 2026-02-15 03:04:58
○ 2026-06-25 05:30:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net...	-
freightchannel.com	gordon.ns.cloudflare.com, aspen.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.109

NS records: gordon.ns.cloudflare.com, aspen.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for freightchannel.com (unsigned zone)

⏱️ Timing

Total: 286ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.42.162, 172.67.163.137`
AAAA	2	`2606:4700:3036::6815:2aa2, 2606:4700:3036::ac43:a389`
NS	2	`aspen.ns.cloudflare.com, gordon.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 43), route2.mx.cloudflare.net (pri: 58)...`
TXT	2	`google-site-verification=YY_NqE2RyyAKA84, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`aspen.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

freightchannel.com has four IP addresses: 104.21.42.162, 172.67.163.137, 2606:4700:3036::6815:2aa2 and 2606:4700:3036::ac43:a389.

Name Servers

freightchannel.com uses two name servers for its delegation: aspen.ns.cloudflare.com and gordon.ns.cloudflare.com.

Mail Servers

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

Hosts with 6 IP addresses each:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.