dedicatednode.com - dns.ninja

`dedicatednode.com`

DNSSEC	⚠️ Not signed
A	69.72.136.43^{🇬🇧 PWEBTECH69.72.128.0/17 FortressITX Route}
		PTR	`d14709.usc1.stableserver.net`
NS	`ns2.mysecurecloudhost.com` ⭐ ⚠️ Not in parent delegation
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns1.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns1.vm295.tmdcloud.com` ⚠️ Not in zone NS records
		A	65.60.61.173^{🇺🇸 SINGLEHOP65.60.0.0/18}
			PTR	`vm295.tmdcloud.com`
NS	`ns2.vm295.tmdcloud.com` ⚠️ Not in zone NS records
		A	65.60.61.173^{🇺🇸 SINGLEHOP65.60.0.0/18}
			PTR	`vm295.tmdcloud.com`
NS	`ns3.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns4.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
MX	`dedicatednode.com` ⭐
		A	69.72.136.43^{🇬🇧 PWEBTECH69.72.128.0/17 FortressITX Route}
			PTR	`d14709.usc1.stableserver.net`
SOA	`ns2.mysecurecloudhost.com`root@vm295.tmdcloud.com 2026-05-02 #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=1785031257

MX for

dedicatednode.com

Previously MX for

www.dedicatednode.com

Subdomains

www.dedicatednode.com

Same first word

dedicatednode.com

DNS History

18 records (8 active, 10 former)

○NSns1.mddservices.com2015-07-16 → 2015-12-23 · 4 obs

● 2015-07-16 17:15:56
● 2015-12-23 15:55:24
○ 2016-03-25 04:38:28
○ 2026-07-26 02:12:50

●NSns1.mysecurecloudhost.com2026-05-03 → 2026-07-26 · 3 obs

○ 2026-02-16 05:16:16
● 2026-05-03 21:00:04
● 2026-07-26 02:12:50

○NSns1.supportedns.com2016-03-25 → 2017-04-02 · 5 obs

○ 2015-12-23 15:55:24
● 2016-03-25 04:38:28
● 2017-04-02 23:30:04
○ 2026-02-16 05:16:16
○ 2026-07-26 02:12:50

●NSns1.vm295.tmdcloud.com2026-02-16 → 2026-07-26 · 3 obs

○ 2017-04-02 23:30:04
● 2026-02-16 05:16:16
● 2026-07-26 02:12:50

○NSns2.mddservices.com2015-07-16 → 2015-12-23 · 4 obs

● 2015-07-16 17:15:56
● 2015-12-23 15:55:24
○ 2016-03-25 04:38:28
○ 2026-07-26 02:12:50

●NSns2.mysecurecloudhost.com2026-05-03 → 2026-07-26 · 3 obs

○ 2026-02-16 05:16:16
● 2026-05-03 21:00:04
● 2026-07-26 02:12:50

○NSns2.supportedns.com2016-03-25 → 2017-04-02 · 5 obs

○ 2015-12-23 15:55:24
● 2016-03-25 04:38:28
● 2017-04-02 23:30:04
○ 2026-02-16 05:16:16
○ 2026-07-26 02:12:50

●NSns2.vm295.tmdcloud.com2026-02-16 → 2026-07-26 · 3 obs

○ 2017-04-02 23:30:04
● 2026-02-16 05:16:16
● 2026-07-26 02:12:50

○NSns3.mddservices.com2015-07-16 → 2015-12-23 · 4 obs

● 2015-07-16 17:15:56
● 2015-12-23 15:55:24
○ 2016-03-25 04:38:28
○ 2026-07-26 02:12:50

●NSns3.mysecurecloudhost.com2026-05-03 → 2026-07-26 · 3 obs

○ 2026-02-16 05:16:16
● 2026-05-03 21:00:04
● 2026-07-26 02:12:50

●NSns4.mysecurecloudhost.com2026-05-03 → 2026-07-26 · 3 obs

○ 2026-02-16 05:16:16
● 2026-05-03 21:00:04
● 2026-07-26 02:12:50

●MXdedicatednode.com2015-07-16 → 2026-07-26 · 6 obs

● 2015-07-16 17:15:56
● 2015-12-23 15:55:24
○ 2016-03-25 04:38:28
○ 2017-04-02 23:30:04
● 2026-02-16 05:16:16
● 2026-07-26 02:12:50

○MXscanner01.mail.supportedns.com2016-03-25 → 2017-04-02 · 5 obs

○ 2015-12-23 15:55:24
● 2016-03-25 04:38:28
● 2017-04-02 23:30:04
○ 2026-02-16 05:16:16
○ 2026-07-26 02:12:50

○MXscanner02.mail.supportedns.com2016-03-25 → 2017-04-02 · 5 obs

○ 2015-12-23 15:55:24
● 2016-03-25 04:38:28
● 2017-04-02 23:30:04
○ 2026-02-16 05:16:16
○ 2026-07-26 02:12:50

○A162.244.253.172016-03-25 → 2017-04-02 · 5 obs

○ 2015-12-23 15:55:24
● 2016-03-25 04:38:28
● 2017-04-02 23:30:04
○ 2026-02-16 05:16:16
○ 2026-07-26 02:12:50

○A162.244.253.652015-07-16 → 2015-12-23 · 4 obs

● 2015-07-16 17:15:56
● 2015-12-23 15:55:24
○ 2016-03-25 04:38:28
○ 2026-07-26 02:12:50

○A65.60.61.1732026-02-16 → 2026-05-01 · 5 obs

○ 2017-04-02 23:30:04
● 2026-02-16 05:16:16
● 2026-05-01 18:59:50
○ 2026-05-03 21:00:04
○ 2026-07-26 02:12:50

●A69.72.136.432026-05-03 → 2026-07-26 · 3 obs

○ 2026-05-01 18:59:50
● 2026-05-03 21:00:04
● 2026-07-26 02:12:50

🔍 DNS Trace

Analysis

Hierarchy

www.dedicatednode.com is delegated beneath dedicatednode.com.

Mail Server Role

The MX record for dedicatednode.com points back to dedicatednode.com — it is its own mail server.

IP Addresses

dedicatednode.com directs to one IP number, which is 69.72.136.43.

Other host names share IP numbers with dedicatednode.com; cloud9wraps.com is one such example.

Name Servers

The DNS delegation for dedicatednode.com covers 6 name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and 3 more.

There is at least partial name server overlap between dedicatednode.com and other domains — siteoutsite.com, gasnerlaw.com, patriciamendozagallery.com and two more among them.

These name servers are routinely co-deployed with the name servers ns4.mysecurecloudhost.com, ns1.a2hosting.com, ns2.a2hosting.com and two others.

Hosts that resolve to one IP address:

ns1.mysecurecloudhost.com points to the IP address 13.248.158.180.

ns2.mysecurecloudhost.com points to the IP address 75.2.118.134.

ns3.mysecurecloudhost.com points to the IP address 76.223.26.245.

ns4.mysecurecloudhost.com points to the IP address 99.83.147.209.

ns1.vm295.tmdcloud.com points to the IP address 65.60.61.173.

ns2.vm295.tmdcloud.com points to the IP address 65.60.61.173.

These two host names — ns1.vm295.tmdcloud.com and ns2.vm295.tmdcloud.com — each point to 65.60.61.173 IP addresses.

Mail Servers

The MX record for dedicatednode.com points to a single mail server: dedicatednode.com.

There is one IP number for dedicatednode.com: 69.72.136.43.