`cruisecommander.com`

DNSSEC	⚠️ Not signed
A	52.6.180.49^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
		PTR	`ec2-52-6-180-49.compute-1.amazonaws.com`
NS	`cruisecommander.com` ⭐
		A	52.6.180.49^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-6-180-49.compute-1.amazonaws.com`
NS	`dns1.cruisesystem.com`
		A	96.46.243.10^{🇺🇸 Flexential96.46.240.0/21}
NS	`dns2.cruisesystem.com` ⚠️ Not in zone NS records
		A	96.46.243.11^{🇺🇸 Flexential96.46.240.0/21}
NS	`dns3.cruisesystem.com` ⚠️ Not in parent delegation
		A	100.28.163.95^{🇺🇸 Amazon100.24.0.0/13 EC2 IAD prefix}
			PTR	`ec2-100-28-163-95.compute-1.amazonaws.com`
MX	`mx1.cruisesystem.com` ⭐
		A	96.46.243.18^{🇺🇸 Flexential96.46.240.0/21}
			PTR	`mx1.cruisesystem.com`
MX	`mx2.cruisesystem.com`⁽²⁰⁾
		A	96.46.243.23^{🇺🇸 Flexential96.46.240.0/21}
TXT	`v=spf1 include:spf.cruisesystem.com ~all`
SOA	`cruisecommander.com`support@cruisesystem.com 2012-05-22 #1

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

NS for

cruisecommander.com

Same first word

cruisecommander.com

DNS History

8 records (7 active, 1 former)

●NScruisecommander.com2015-05-21 → 2026-03-28 · 2 obs

● 2015-05-21 12:24:44
● 2026-03-28 07:22:30

●NSdns1.cruisesystem.com2015-05-21 → 2026-03-28 · 2 obs

● 2015-05-21 12:24:44
● 2026-03-28 07:22:30

●NSdns2.cruisesystem.com2015-05-21 → 2026-03-28 · 2 obs

● 2015-05-21 12:24:44
● 2026-03-28 07:22:30

●NSdns3.cruisesystem.com2026-03-23 → 2026-03-28 · 3 obs

○ 2015-05-21 12:24:44
● 2026-03-23 10:23:36
● 2026-03-28 07:22:30

●MXmx1.cruisesystem.com2015-05-21 → 2026-03-28 · 2 obs

● 2015-05-21 12:24:44
● 2026-03-28 07:22:30

●MXmx2.cruisesystem.com2015-05-21 → 2026-03-28 · 2 obs

● 2015-05-21 12:24:44
● 2026-03-28 07:22:30

●A52.6.180.492026-03-23 → 2026-03-28 · 3 obs

○ 2017-07-10 15:03:16
● 2026-03-23 10:23:36
● 2026-03-28 07:22:30

○A64.135.36.1952015-05-21 → 2017-07-10 · 4 obs

● 2015-05-21 12:24:44
● 2017-07-10 15:03:16
○ 2026-03-23 10:23:36
○ 2026-03-28 07:22:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net, d.gtld-servers.net...	-
cruisecommander.com	dns1.cruisesystem.com, dns2.cruisesystem.com	2 records

✅ Authoritative Response

Server:96.46.243.10

NS records: dns1.cruisesystem.com, dns2.cruisesystem.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cruisecommander.com (unsigned zone)

⏱️ Timing

Total: 399ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.6.180.49`
NS	2	`dns1.cruisesystem.com, dns3.cruisesystem.com`
MX	2	`mx1.cruisesystem.com (pri: 10), mx2.cruisesystem.com (pri: 20)`
TXT	1	`v=spf1 include:spf.cruisesystem.com ~all`
SOA	1	`cruisecommander.com support.cruisesystem`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns1.cruisesystem.com, dns2.cruisesystem.com)

Analysis

Name Server Role

cruisecommander.com serves as the name server for cruisecommander.com.

Common name servers include dns1.cruisesystem.com, dns3.cruisesystem.com and dns2.cruisesystem.com, used together with cruisecommander.com.

IP Addresses

cruisecommander.com resolves to a single IP: 52.6.180.49.

Other host names, for instance shinyvoyage.com, ramosfuntravel.com, cruisegarden.com, seealltravel.com and bouratravel.com share IP numbers with cruisecommander.com.

Name Servers

cruisecommander.com is delegated to four name servers: cruisecommander.com, dns1.cruisesystem.com, dns2.cruisesystem.com and dns3.cruisesystem.com.

cruisecommander.com shares some name servers with other domains, for example bookacruisetoday.com, adorethejourney.com, palmtravelplanners.com, worldwidecruisesandtravel.com and carriescustomcruises.com.

Host names with a single IP

cruisecommander.com resolves to 52.6.180.49

dns1.cruisesystem.com resolves to 96.46.243.10

dns2.cruisesystem.com resolves to 96.46.243.11

dns3.cruisesystem.com resolves to 100.28.163.95

Mail Servers

cruisecommander.com is served by two mail servers: mx1.cruisesystem.com and mx2.cruisesystem.com.

cruisecommander.com shares the mail server setup with other domains, for example titanvacations.com, detourdestinationsllc.com, isleseattravel.com, coralwesttravel.com and largestcruiseevent.com.

cruisecommander.com shares at least some mail servers with other domains, for example embarknation.com.

Host names with a single IP:

mx1.cruisesystem.com points to 96.46.243.18

mx2.cruisesystem.com points to 96.46.243.23

cruisecommander.com - robtex.com