`denverprotection.com`

DNSSEC	⚠️ Not signed
A	35.208.112.34^{🇺🇸 Google35.208.0.0/15}
		PTR	`34.112.208.35.bc.googleusercontent.com`
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	`denverprotection-com.mail.eo.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::b^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr02cu00603.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch4pr21cu00105.inbound.protection.outlook.com`
		A	52.101.8.44^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm5pr04cu00104.inbound.protection.outlook.com`
		A	52.101.9.14^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr03cu00206.inbound.protection.outlook.com`
		A	52.101.10.5^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr04cu00105.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
TXT	`mscid=xS/ePnEp/9cYIGjiTAs8aVXkJxfV5NpyUh/tHsODKahn5lvVGrOwrHmpzwl7ng+GPt3NBxg...`
TXT	`v=spf1 include: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=1774880287

Same first word

denverprotection.com

DNS History

13 records (6 active, 7 former)

●NSns1.bdm.microsoftonline.com2015-05-27 → 2026-03-30 · 3 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2026-03-30 14:30:54

○NSns1.officelive.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 13:28:56
○ 2015-05-27 14:10:48
○ 2026-03-30 14:30:54

●NSns2.bdm.microsoftonline.com2015-05-27 → 2026-03-30 · 3 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2026-03-30 14:30:54

○NSns2.officelive.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 13:28:56
○ 2015-05-27 14:10:48
○ 2026-03-30 14:30:54

●NSns3.bdm.microsoftonline.com2015-05-27 → 2026-03-30 · 3 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2026-03-30 14:30:54

●NSns4.bdm.microsoftonline.com2015-05-27 → 2026-03-30 · 3 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2026-03-30 14:30:54

●MXdenverprotection-com.mail.eo.outlook.com2015-05-27 → 2026-03-30 · 3 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2026-03-30 14:30:54

○MXpamx1.hotmail.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 13:28:56
○ 2015-05-27 14:10:48
○ 2026-03-30 14:30:54

○A104.146.207.292016-07-12 → 2016-07-12 · 4 obs

○ 2016-03-19 08:22:26
● 2016-07-12 18:10:06
○ 2017-02-19 11:29:56
○ 2026-03-30 14:30:54

○A104.146.232.692017-02-19 → 2017-02-19 · 4 obs

○ 2016-07-12 18:10:06
● 2017-02-19 11:29:56
○ 2020-01-17 21:13:08
○ 2026-03-30 14:30:54

○A191.234.214.292015-05-27 → 2016-03-19 · 5 obs

○ 2008-03-17 13:28:56
● 2015-05-27 14:10:48
● 2016-03-19 08:22:26
○ 2016-07-12 18:10:06
○ 2026-03-30 14:30:54

○A207.46.222.112008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 13:28:56
○ 2015-05-27 14:10:48
○ 2026-03-30 14:30:54

●A35.208.112.342020-01-17 → 2026-03-30 · 3 obs

○ 2017-02-19 11:29:56
● 2020-01-17 21:13:08
● 2026-03-30 14:30:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
denverprotection.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 denverprotection.com (unsigned zone)

⏱️ Timing

Total: 126ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.208.112.34`
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`denverprotection-com.mail.eo.outlook.com`
TXT	2	`mscid=xS/ePnEp/9cYIGjiTAs8aVXkJxfV5NpyUh, v=spf1 include:outlook.com ~all`
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

IP Addresses

denverprotection.com maps to IP address 35.208.112.34.

Other host names, for example, 34.112.208.35.bc.googleusercontent.com share IP numbers with denverprotection.com.

Name Servers

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

denverprotection.com at least partially shares name servers with other domains such as chr-dalsgaard.dk, teampcl.com, reklamefolder.nl, laserjet.ch and cmmcpr.com.