crewconnect.com - dns.ninja

`crewconnect.com`

DNSSEC	⚠️ Not signed
A	20.186.53.42^{🇺🇸 Microsoft20.184.0.0/13 MICROSOFT}
NS	`ns1.fleetcor.com` ⭐
		A	15.197.238.118^{🇺🇸 Amazon15.197.224.0/20}
			PTR	`a3816b6219b5252d1.awsglobalaccelerator.com`
NS	`ns2.fleetcor.com`
		A	15.197.158.105^{🇺🇸 Amazon15.197.144.0/20}
			PTR	`a38bbbfadb12223f2.awsglobalaccelerator.com`
NS	`ns3.fleetcor.com`
		A	15.197.158.105^{🇺🇸 Amazon15.197.144.0/20}
			PTR	`a38bbbfadb12223f2.awsglobalaccelerator.com`
MX	`mx1.hc2524-96.iphmx.com` ⭐
		A	68.232.130.131^{🇺🇸 CISCO-168.232.130.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	216.71.146.39^{🇺🇸 CISCO-1216.71.146.0/24 170 West Tasman Drive San Jose CA 95134 United States}
MX	`mx2.hc2524-96.iphmx.com` ⭐
		A	68.232.130.131^{🇺🇸 CISCO-168.232.130.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	216.71.146.39^{🇺🇸 CISCO-1216.71.146.0/24 170 West Tasman Drive San Jose CA 95134 United States}
TXT	`v=spf1 exists:%{i}._i.%{d}._d.espf.agari-dns.net include:%{d}.97.spf-protect....`
TXT	`_72mqii7slgm9g4c1hnz81sgkryji848`
TXT	`ppe-7020443c88a0bd909f8c`
TXT	`mqhrwl248y2qrly4vsm4f3nqjqcjkmlt`
TXT	`MS=ms21523265`
SOA	`ns1.fleetcor.com`root@localhost 2026-07-08 #0

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

Subdomains

crewrezqa1.crewconnect.com

dashboard1.crewconnect.com

Same first word

crewconnect.me

crewconnect.net

crewconnect.de

crewconnect.com

crewconnect.org

crewconnect.aero

Similar names

connectcrew.com

DNS History

22 records (6 active, 16 former)

●NSns1.fleetcor.com2026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:02
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

○NSns10.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns11.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns1172.dns.dyn.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns12.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns13.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns14.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns15.dnsmadeeasy.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

●NSns2.fleetcor.com2026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:02
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

○NSns2179.dns.dyn.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

●NSns3.fleetcor.com2026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:02
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

○NSns3195.dns.dyn.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns4145.dns.dyn.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○NSns95.worldnic.com2007-10-24 → 2007-10-24 · 3 obs

● 2007-10-24 07:01:02
○ 2015-06-09 06:52:20
○ 2026-08-13 16:29:14

○NSns96.worldnic.com2007-10-24 → 2007-10-24 · 3 obs

● 2007-10-24 07:01:02
○ 2015-06-09 06:52:20
○ 2026-08-13 16:29:14

○MXcluster1.us.messagelabs.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○MXcluster1a.us.messagelabs.com2015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:02
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

●MXmx1.hc2524-96.iphmx.com2026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:02
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

●MXmx2.hc2524-96.iphmx.com2026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:02
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

●A20.186.53.422026-02-24 → 2026-08-13 · 3 obs

○ 2017-09-06 20:55:12
● 2026-02-24 15:04:06
● 2026-08-13 16:29:14

○A209.235.27.1342015-06-09 → 2017-09-06 · 5 obs

○ 2007-10-24 07:01:02
● 2015-06-09 06:52:20
● 2017-09-06 20:55:12
○ 2026-02-24 15:04:06
○ 2026-08-13 16:29:14

○A209.62.20.1862007-10-24 → 2007-10-24 · 3 obs

● 2007-10-24 07:01:02
○ 2015-06-09 06:52:20
○ 2026-08-13 16:29:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
crewconnect.com	ns1.fleetcor.com, ns2.fleetcor.com, ns3.fleetcor.com	3 records

✅ Authoritative Response

Server:15.197.238.118

NS records: ns1.fleetcor.com, ns2.fleetcor.com, ns3.fleetcor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crewconnect.com (unsigned zone)

⏱️ Timing

Total: 3047ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`45.60.17.233, 45.60.11.233`
NS	3	`ns1.fleetcor.com, ns3.fleetcor.com...`
MX	2	`mx1.hc2524-96.iphmx.com (pri: 10), mx2.hc2524-96.iphmx.com (pri: 10)`
TXT	5	`_72mqii7slgm9g4c1hnz81sgkryji848, ppe-7020443c88a0bd909f8c...`
SOA	1	`ns1.fleetcor.com root.localhost`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.fleetcor.com, ns2.fleetcor.com, ns3.fleetcor.com)

Analysis

Hierarchy

The parent domain of crewrezqa1.crewconnect.com and dashboard1.crewconnect.com is crewconnect.com.

IP Addresses

crewconnect.com directs to one IP number, which is 20.186.53.42.

Name Servers

DNS for crewconnect.com is handled by three authoritative name servers: ns1.fleetcor.com, ns2.fleetcor.com and ns3.fleetcor.com.

There is at least partial name server overlap between crewconnect.com and other domains — pacpride.com, cambridgefx.com, fleetcor.org and two more among them.

Three hosts, each with one IP address: ns1.fleetcor.com → 15.197.238.118; ns2.fleetcor.com → 15.197.158.105; ns3.fleetcor.com → 15.197.158.105.

Host names pointing to 15.197.158.105 IP addresses: ns2.fleetcor.com and ns3.fleetcor.com.

Mail Servers

The MX records for crewconnect.com point to two mail servers: mx1.hc2524-96.iphmx.com and mx2.hc2524-96.iphmx.com.

crewconnect.com has the same mail server arrangement as a number of other domains, for example corplodg.com, cfnnet.com, taconnections.com and two more.

crewconnect.com and a number of other domains — pacpride.com, epedagio.com.br, gpsfx.com and afex.com among them — share at least some of the same mail servers.

mx1.hc2524-96.iphmx.com resolves to 68.232.130.131 and 216.71.146.39; mx2.hc2524-96.iphmx.com resolves to the same two IP addresses: 68.232.130.131 and 216.71.146.39.

Host names pointing to 68.232.130.131 IP addresses: mx1.hc2524-96.iphmx.com and mx2.hc2524-96.iphmx.com.

Host names pointing to 216.71.146.39 IP addresses: mx1.hc2524-96.iphmx.com and mx2.hc2524-96.iphmx.com.