`towermed.com`

DNSSEC	⚠️ Not signed
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com`
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com`
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`towermed-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:f802::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01403.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr04cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00201.inbound.protection.outlook.com`
		A	52.101.8.42^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr03cu00402.inbound.protection.outlook.com`
		A	52.101.10.8^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr04cu00100.inbound.protection.outlook.com`
		A	52.101.11.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00205.inbound.protection.outlook.com`
		A	52.101.41.56^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr21cu00100.inbound.protection.outlook.com`
TXT	`v=spf1 include:spfa.cpmails.com include:spf.protection.outlook.com ~all`
TXT	`mscid=K4hLog3GmUGP3ba0ENAnMuuPfLpyVliHJbgjB0KGLbht7FJAb1SgpCHBlzOtFfC/yq/e16h...`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=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=1774431112

Same first word

towermed.com

towermed.com.au

towermed.net

Similar names

toweredm.com

medtower.com

remotewd.com

DNS History

9 records (5 active, 4 former)

●NSns1.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2016-12-18 23:36:24
● 2026-03-25 09:37:20

●NSns2.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2016-12-18 23:36:24
● 2026-03-25 09:37:20

●NSns3.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2016-12-18 23:36:24
● 2026-03-25 09:37:20

●NSns4.bdm.microsoftonline.com2026-03-25 → 2026-03-25 · 2 obs

○ 2016-12-18 23:36:24
● 2026-03-25 09:37:20

○NSns69.worldnic.com2015-06-22 → 2016-12-18 · 3 obs

● 2015-06-22 17:18:24
● 2016-12-18 23:36:24
○ 2026-03-25 09:37:20

○NSns70.worldnic.com2015-06-22 → 2016-12-18 · 3 obs

● 2015-06-22 17:18:24
● 2016-12-18 23:36:24
○ 2026-03-25 09:37:20

○MXmail.towermed.com2015-06-22 → 2016-12-18 · 3 obs

● 2015-06-22 17:18:24
● 2016-12-18 23:36:24
○ 2026-03-25 09:37:20

●MXtowermed-com.mail.protection.outlook.com2026-03-25 → 2026-03-25 · 2 obs

○ 2016-12-18 23:36:24
● 2026-03-25 09:37:20

○A216.240.50.2112015-06-22 → 2016-12-18 · 3 obs

● 2015-06-22 17:18:24
● 2016-12-18 23:36:24
○ 2026-03-25 09:37:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
towermed.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com	8 records

✅ Authoritative Response

Server:204.14.183.208

NS records: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for towermed.com (unsigned zone)

⏱️ Timing

Total: 117ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`towermed-com.mail.protection.outlook.com`
TXT	2	`v=spf1 include:spfa.cpmails.com include:, mscid=K4hLog3GmUGP3ba0ENAnMuuPfLpyVliHJb`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...)

Analysis

Name Servers

towermed.com is delegated to four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

towermed.com shares name servers with other domains at least partially, for example mas-sam.com, exetec.co.uk, sgagnon.ca, rabeckco.com and cloud9online.com.au.