incommand.com - dns.ninja
incommand.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=1782914306 | ||||||
PTR for
Previously NS for
incommand.com |
Same first word
incommand.co.uk |
incommand.net |
incommand.com.cn |
incommand.nl |
incommand.cn |
incommand.co |
incommand.com.au |
incommand.it |
incommand.com |
incommand.de |
incommand.org |
Similar names
DNS History
12 records (8 active, 4 former)
○NSincommand.com2015-05-30 → 2017-06-24 · 4 obs
● 2017-06-24 11:44:40
○ 2026-02-26 21:39:18
○ 2026-07-01 14:09:46
●NSns0.yakima.net2026-02-26 → 2026-07-01 · 5 obs
● 2026-02-26 21:39:18
○ 2026-06-29 23:38:12
● 2026-07-01 09:26:58
● 2026-07-01 14:09:46
●NSns1.incommand.com2026-02-26 → 2026-07-01 · 5 obs
● 2026-02-26 21:39:18
○ 2026-06-29 23:38:12
● 2026-07-01 09:26:58
● 2026-07-01 14:09:46
●NSns1.yakima.net2015-05-30 → 2026-07-01 · 2 obs
● 2026-07-01 14:09:46
●NSns2.yakima.net2015-05-30 → 2026-07-01 · 2 obs
● 2026-07-01 14:09:46
●NSns3.yakima.net2026-02-26 → 2026-07-01 · 3 obs
● 2026-02-26 21:39:18
● 2026-07-01 14:09:46
○MXmail.yakima.net2015-05-30 → 2017-06-24 · 4 obs
● 2017-06-24 11:44:40
○ 2026-02-26 21:39:18
○ 2026-07-01 14:09:46
●MXmx.emailarray.com2026-02-26 → 2026-07-01 · 5 obs
● 2026-02-26 21:39:18
○ 2026-06-29 23:38:12
● 2026-07-01 09:26:58
● 2026-07-01 14:09:46
●MXmx2.emailarray.com2026-02-26 → 2026-07-01 · 5 obs
● 2026-02-26 21:39:18
○ 2026-06-29 23:38:12
● 2026-07-01 09:26:58
● 2026-07-01 14:09:46
○A104.197.151.852016-08-09 → 2017-06-24 · 5 obs
● 2016-08-09 22:58:44
● 2017-06-24 11:44:40
○ 2026-02-26 21:39:18
○ 2026-07-01 14:09:46
●A104.225.217.1832026-02-26 → 2026-07-01 · 5 obs
● 2026-02-26 21:39:18
○ 2026-06-29 23:38:12
● 2026-07-01 09:26:58
● 2026-07-01 14:09:46
○A216.7.50.22015-05-30 → 2016-03-31 · 4 obs
● 2016-03-31 15:09:10
○ 2016-08-09 22:58:44
○ 2026-07-01 14:09:46
🔍 DNS Trace
Analysis
IP Addresses
incommand.com resolves to one IP address: 104.225.217.183.
www.fitico.com, fitico.com, www.kgdn.com and two other host names share IP numbers with incommand.com.
Name Servers
incommand.com has five name servers, which are ns1.incommand.com, ns0.yakima.net, ns1.yakima.net and two others.
incommand.com shares at least some of its name servers with other domains, including yakimanation.us, agappr.com, yakimanation.org and two others.
These name servers are frequently seen alongside the name servers ns2.yakima.net, ns3.yakima.net, ns1.yakimanation.us and ns1.agappr.com.
The hostnames ns1.yakima.net, ns2.yakima.net and ns3.yakima.net each resolve to a single IP: ns1.yakima.net → 104.225.217.183, ns2.yakima.net → 156.19.244.172, ns3.yakima.net → 34.68.168.106.
Mail Servers
Mail for incommand.com is handled by two mail servers — mx2.emailarray.com and mx.emailarray.com.
incommand.com uses an identical mail server configuration to several other domains — among them mccpuc.in, pulselessflow.com, origisconsulting.com and two more.
incommand.com shares at least some of its mail servers with other domains, such as lombardisl.com.
Hostnames pointing to five IP numbers:
mx.emailarray.com resolves to four IP addresses: 65.39.216.12, 65.39.216.33, 65.39.216.37 and two others.
Hostnames that resolve to three IP addresses:
The hostname mx2.emailarray.com directs to 65.39.216.33, 65.39.216.37 and 65.39.216.41.
Both mx.emailarray.com and mx2.emailarray.com resolve to 65.39.216.33 IP addresses each.
Both mx.emailarray.com and mx2.emailarray.com resolve to 65.39.216.37 IP addresses each.
Both mx.emailarray.com and mx2.emailarray.com resolve to 65.39.216.41 IP addresses each.