freightcommand.com - dns.ninja
freightcommand.com
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.netnstld@verisign-grs.com serial=1788029555 | ||||||
Same first word
freightcommand.com |
Similar names
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns73.domaincontrol.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●NSns74.domaincontrol.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●MXalt1.aspmx.l.google.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●MXalt2.aspmx.l.google.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●MXaspmx.l.google.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●MXaspmx2.googlemail.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●MXaspmx3.googlemail.com2015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
●A65.52.24.442015-05-31 → 2026-08-29 · 2 obs
● 2026-08-29 18:54:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| freightcommand.com | ns73.domaincontrol.com, ns74.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.47
NS records: ns73.domaincontrol.com, ns74.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for freightcommand.com (unsigned zone)
⏱️ Timing
Total: 206ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.52.24.44 |
| NS | 2 | ns73.domaincontrol.com, ns74.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| TXT | 1 | google-site-verification=KwqubPB7k57jiii |
| SOA | 1 | ns73.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns73.domaincontrol.com, ns73.domaincontrol.com, ns74.domaincontrol.com...)
Analysis
IP Addresses
freightcommand.com directs to one IP number, which is 65.52.24.44.
Name Servers
freightcommand.com is served by two delegated name servers, ns73.domaincontrol.com and ns74.domaincontrol.com.
freightcommand.com has the same name server delegation as a number of other domains, such as dmaarchitectes.ca, grandrivermgmt.com, asisalesincentives.com and two more.
Each of the two host names carries two IP addresses: ns73.domaincontrol.com points to 97.74.106.47 and 2603:5:21a4::2f, and ns74.domaincontrol.com points to 173.201.74.47 and 2603:5:22a4::2f.
Mail Servers
freightcommand.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
freightcommand.com shares at least some of its mail servers with other domains — for example resurgenceenergy.com, atualcargas.com.br, hrdr.eu and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 172.253.63.27 and 2607:f8b0:4004:c2d::1a.
alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1b.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 192.178.234.27 IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.27 IP addresses.