cmsseattle.com - dns.ninja

`cmsseattle.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` ⚠️ Not in parent delegation
		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` ⚠️ Not in parent delegation
		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	`cmsseattle-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.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:f913::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr05cu00101.inbound.protection.outlook.com`
		A	52.101.9.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00205.inbound.protection.outlook.com`
		A	52.101.40.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr03cu00300.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
		A	52.101.50.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00502.inbound.protection.outlook.com`
TXT	`mscid=9yeUTzNBZM7AZSAMFxemA8LpLNNuhj2nSiABOBsxHfs397bCpAHikLtIIqMnvV5L0whS0q2...`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
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=1785556267

Same first word

cmsseattle.com

Similar names

mclestates.com

selectatms.com

DNS History

9 records (5 active, 4 former)

●NSns1.bdm.microsoftonline.com2016-03-26 → 2026-08-01 · 3 obs

○ 2015-12-18 00:03:04
● 2016-03-26 22:58:02
● 2026-08-01 04:20:14

○NSns1.hover.com2015-12-18 → 2015-12-18 · 3 obs

● 2015-12-18 00:03:04
○ 2016-03-26 22:58:02
○ 2026-08-01 04:20:14

●NSns2.bdm.microsoftonline.com2016-03-26 → 2026-08-01 · 3 obs

○ 2015-12-18 00:03:04
● 2016-03-26 22:58:02
● 2026-08-01 04:20:14

○NSns2.hover.com2015-12-18 → 2015-12-18 · 3 obs

● 2015-12-18 00:03:04
○ 2016-03-26 22:58:02
○ 2026-08-01 04:20:14

●NSns3.bdm.microsoftonline.com2016-03-26 → 2026-08-01 · 3 obs

○ 2015-12-18 00:03:04
● 2016-03-26 22:58:02
● 2026-08-01 04:20:14

●NSns4.bdm.microsoftonline.com2016-03-26 → 2026-08-01 · 3 obs

○ 2015-12-18 00:03:04
● 2016-03-26 22:58:02
● 2026-08-01 04:20:14

●MXcmsseattle-com.mail.protection.outlook.com2016-03-26 → 2026-08-01 · 3 obs

○ 2015-12-18 00:03:04
● 2016-03-26 22:58:02
● 2026-08-01 04:20:14

○MXmx.hover.com.cust.hostedemail.com2015-12-18 → 2015-12-18 · 3 obs

● 2015-12-18 00:03:04
○ 2016-03-26 22:58:02
○ 2026-08-01 04:20:14

○A64.99.80.302015-12-18 → 2015-12-18 · 3 obs

● 2015-12-18 00:03:04
○ 2016-03-26 22:58:02
○ 2026-08-01 04:20:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
cmsseattle.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com	4 records

✅ Authoritative Response

Server:150.171.21.208

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cmsseattle.com (unsigned zone)

⏱️ Timing

Total: 133ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`cmsseattle-com.mail.protection.outlook.c`
TXT	2	`mscid=9yeUTzNBZM7AZSAMFxemA8LpLNNuhj2nSi, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 4

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

Analysis

Name Servers

Four name servers handle the delegation for cmsseattle.com: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

cmsseattle.com partially shares its NS delegation with several other domains, including pinnaclehealth.net, landstorfer.net, resoluteteam.com and two others.

ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com each carry two IP addresses. ns1.bdm.microsoftonline.com has 13.107.236.208 and 2603:1061:0:700::d0; ns2.bdm.microsoftonline.com has 150.171.21.208 and 2620:1ec:8ec:700::d0; ns3.bdm.microsoftonline.com has 204.14.183.208 and 2a01:111:4000:700::d0; ns4.bdm.microsoftonline.com has 208.84.5.208 and 2620:1ec:bda:700::d0.

Mail Servers

cmsseattle.com uses one mail server — cmsseattle-com.mail.protection.outlook.com.

cmsseattle-com.mail.protection.outlook.com has 8 IP addresses: 52.101.9.21, 52.101.40.0, 52.101.42.18 plus 5 more.