`commanddomains.com`

DNSSEC	⚠️ Not signed
A	104.18.26.246^{Cloudflare104.18.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
A	104.18.27.246^{Cloudflare104.18.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns43.domaincontrol.com` ⭐
		A	2603:5:2152::16^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns43.domaincontrol.com`
		A	97.74.101.22^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns43.domaincontrol.com`
NS	`ns44.domaincontrol.com`
		A	2603:5:2252::16^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns44.domaincontrol.com`
		A	173.201.69.22^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns44.domaincontrol.com`
MX	`commanddomains-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c903::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr02cu00503.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm5pr02cu00203.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`ip-52-101-9-17.defastlink.net`
		A	52.101.9.20^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00604.inbound.protection.outlook.com`
		A	52.101.41.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01702.inbound.protection.outlook.com`
		A	52.101.50.7^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr21cu00207.inbound.protection.outlook.com`
TXT	`NETORG19277781.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
TXT	`protonmail-verification=437d4fb9a6b96e42042c31c17334a4cca7e31798`
SOA	`ns43.domaincontrol.com`dns@jomax.net 2026-01-01 #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=1771291435

Previously MX for

commanddomains.com

Same first word

commanddomains.com

DNS History

12 records (5 active, 7 former)

○NSns1.reliabledns.org2016-04-25 → 2016-04-25 · 4 obs

○ 2016-02-09 15:30:36
● 2016-04-25 23:23:46
○ 2018-07-16 03:04:04
○ 2026-03-24 12:49:24

○NSns1.stablehost.com2015-11-02 → 2016-02-09 · 4 obs

● 2015-11-02 13:53:12
● 2016-02-09 15:30:36
○ 2016-04-25 23:23:46
○ 2026-03-24 12:49:24

○NSns2.reliabledns.org2016-04-25 → 2016-04-25 · 4 obs

○ 2016-02-09 15:30:36
● 2016-04-25 23:23:46
○ 2018-07-16 03:04:04
○ 2026-03-24 12:49:24

○NSns2.stablehost.com2015-11-02 → 2016-02-09 · 4 obs

● 2015-11-02 13:53:12
● 2016-02-09 15:30:36
○ 2016-04-25 23:23:46
○ 2026-03-24 12:49:24

●NSns43.domaincontrol.com2026-02-17 → 2026-03-24 · 3 obs

○ 2018-07-16 03:04:04
● 2026-02-17 00:10:36
● 2026-03-24 12:49:24

●NSns44.domaincontrol.com2026-02-17 → 2026-03-24 · 3 obs

○ 2018-07-16 03:04:04
● 2026-02-17 00:10:36
● 2026-03-24 12:49:24

●MXcommanddomains-com.mail.protection.outlook.com2026-02-17 → 2026-03-24 · 3 obs

○ 2018-07-16 03:04:04
● 2026-02-17 00:10:36
● 2026-03-24 12:49:24

○MXcommanddomains.com2015-11-02 → 2016-04-25 · 4 obs

● 2015-11-02 13:53:12
● 2016-04-25 23:23:46
○ 2018-07-16 03:04:04
○ 2026-03-24 12:49:24

●A104.18.26.2462026-02-17 → 2026-03-24 · 3 obs

○ 2018-07-16 03:04:04
● 2026-02-17 00:10:36
● 2026-03-24 12:49:24

●A104.18.27.2462026-02-17 → 2026-03-24 · 3 obs

○ 2018-07-16 03:04:04
● 2026-02-17 00:10:36
● 2026-03-24 12:49:24

○A108.178.52.432015-11-02 → 2016-02-09 · 4 obs

● 2015-11-02 13:53:12
● 2016-02-09 15:30:36
○ 2016-04-25 23:23:46
○ 2026-03-24 12:49:24

○A198.20.65.112016-04-25 → 2016-04-25 · 4 obs

○ 2016-02-09 15:30:36
● 2016-04-25 23:23:46
○ 2018-07-16 03:04:04
○ 2026-03-24 12:49:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net...	-
commanddomains.com	ns43.domaincontrol.com, ns44.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.101.22

NS records: ns43.domaincontrol.com, ns44.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for commanddomains.com (unsigned zone)

⏱️ Timing

Total: 157ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.18.26.246, 104.18.27.246`
NS	2	`ns43.domaincontrol.com, ns44.domaincontrol.com`
MX	1	`commanddomains-com.mail.protection.outlo`
TXT	3	`NETORG19277781.onmicrosoft.com, v=spf1 include:secureserver.net -all...`
SOA	1	`ns43.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns43.domaincontrol.com, ns43.domaincontrol.com, ns44.domaincontrol.com...)

Analysis

IP Addresses

commanddomains.com points to two IPs: 104.18.26.246 and 104.18.27.246.

Other host names including chile.bumeran.com, ideotext.com, ataica.com, volentixlabs.com and voltacoach.com share IP numbers with commanddomains.com.

Name Servers

commanddomains.com's delegation uses two name servers, ns43.domaincontrol.com and ns44.domaincontrol.com.

commanddomains.com shares the same name server setup as other domains, for example visbase.com, nextkeyonline.com, lma.org, soldes.net and sisc.org.

commanddomains.com at least partially shares name servers with other domains; for instance schltd.com.

Host names with two IPs:

ns43.domaincontrol.com points to: 2603:5:2152::16 and 97.74.101.22

ns44.domaincontrol.com points to: 2603:5:2252::16 and 173.201.69.22

Mail Servers

commanddomains.com is handled by a single mail server, commanddomains-com.mail.protection.outlook.com.

Hostname commanddomains-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c903::3, 2a01:111:f403:c946::, 2a01:111:f403:f802::1, 2a01:111:f403:f905::3, 52.101.9.17, 52.101.9.20, 52.101.41.26 and 52.101.50.7.

commanddomains.com - robtex.com