`managedthreatdetection.com`

DNSSEC	⚠️ Not signed
A	104.196.225.240^{🇺🇸 Google104.196.224.0/20}
		PTR	`240.225.196.104.bc.googleusercontent.com`
NS	`ns1-35.azure-dns.com` ⭐
		A	2603:1061:0:10::23^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-35.azure-dns.com`
		A	150.171.10.35^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-35.azure-dns.com`
NS	`ns2-35.azure-dns.net`
		A	2620:1ec:8ec:10::23^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-35.azure-dns.net`
		A	150.171.16.35^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-35.azure-dns.net`
NS	`ns3-35.azure-dns.org`
		A	2a01:111:4000:10::23^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-35.azure-dns.org`
		A	13.107.222.35^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-35.azure-dns.org`
NS	`ns4-35.azure-dns.info`
		A	2620:1ec:bda:10::23^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-35.azure-dns.info`
		A	13.107.206.35^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-35.azure-dns.info`
MX	`vtwil-mx-fw01.vertek.com` ⭐
MX	`vtcol-mx-fw01.vertek.com`⁽¹⁰⁰⁾
TXT	`v=spf1 ip4:8.225.177.0/24 ip4:67.217.123.0/24 ip4:52.4.47.58`
SOA	`ns1-35.azure-dns.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=1778435896

Same first word

managedthreatdetection.com

DNS History

12 records (7 active, 5 former)

●NSns1-35.azure-dns.com2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

●NSns2-35.azure-dns.net2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

●NSns3-35.azure-dns.org2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

●NSns4-35.azure-dns.info2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

○NSns67.vertek.com2018-05-16 → 2018-05-16 · 3 obs

● 2018-05-16 02:11:06
○ 2026-02-16 00:46:10
○ 2026-05-10 18:10:32

○NSns8.vertek.com2018-05-16 → 2018-05-16 · 3 obs

● 2018-05-16 02:11:06
○ 2026-02-16 00:46:10
○ 2026-05-10 18:10:32

○MXvtbursrmx99.vertekvt.net2018-05-16 → 2018-05-16 · 3 obs

● 2018-05-16 02:11:06
○ 2026-02-16 00:46:10
○ 2026-05-10 18:10:32

●MXvtcol-mx-fw01.vertek.com2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

○MXvtcolsrmx1.vertekvt.net2018-05-16 → 2018-05-16 · 3 obs

● 2018-05-16 02:11:06
○ 2026-02-16 00:46:10
○ 2026-05-10 18:10:32

●MXvtwil-mx-fw01.vertek.com2026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

●A104.196.225.2402026-02-16 → 2026-05-10 · 3 obs

○ 2018-05-16 02:11:06
● 2026-02-16 00:46:10
● 2026-05-10 18:10:32

○A34.233.91.1652018-05-16 → 2018-05-16 · 3 obs

● 2018-05-16 02:11:06
○ 2026-02-16 00:46:10
○ 2026-05-10 18:10:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net...	-
managedthreatdetection.com	ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.10.35

NS records: ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managedthreatdetection.com (unsigned zone)

⏱️ Timing

Total: 555ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.196.225.240`
NS	4	`ns1-35.azure-dns.com, ns2-35.azure-dns.net...`
MX	2	`vtwil-mx-fw01.vertek.com (pri: 10), vtcol-mx-fw01.vertek.com (pri: 100)`
TXT	1	`v=spf1 ip4:8.225.177.0/24 ip4:67.217.123`
SOA	1	`ns1-35.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-35.azure-dns.com, ns1-35.azure-dns.com)

Analysis

IP Addresses

managedthreatdetection.com points to a single IP address: 104.196.225.240.

Other host names, for instance summitpmg.com, managedthreatintelligence.com, itherm.com and 240.225.196.104.bc.googleusercontent.com share IP numbers with managedthreatdetection.com.

Name Servers

managedthreatdetection.com is delegated to four name servers: ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org.

At least part of the name servers for managedthreatdetection.com are shared with other domains, for instance sensalytics.io, dragonmessenger.com, campusmasterd.es, nexaexperience.com and olivermedical.com.

Host names with two IP numbers:

ns1-35.azure-dns.com points to: 2603:1061:0:10::23 and 150.171.10.35

ns4-35.azure-dns.info points to: 2620:1ec:bda:10::23 and 13.107.206.35

ns2-35.azure-dns.net points to: 2620:1ec:8ec:10::23 and 150.171.16.35

ns3-35.azure-dns.org points to: 2a01:111:4000:10::23 and 13.107.222.35

Mail Servers

managedthreatdetection.com is handled by two mail servers: vtcol-mx-fw01.vertek.com and vtwil-mx-fw01.vertek.com.

managedthreatdetection.com shares the same mail server setup as other domains, for instance managedthreatintelligence.com.

managedthreatdetection.com - robtex.com