managednetworks.com - dns.ninja

`managednetworks.com`

DNSSEC	⚠️ Not signed
A	209.189.247.7^{🇺🇸 FDL-AS19366209.189.240.0/20 Fibertown}
		PTR	`7-247-189-209.fibertown.net`
NS	`ns1.fibertown.com` ⭐ ⚠️ Not in parent delegation
		A	209.189.224.40^{🇺🇸 FDL-AS19366209.189.224.0/21 Fibertown}
			PTR	`ns1.fibertown.com`
NS	`dns1.managednetworks.com` ⚠️ Not in zone NS records
		A	209.189.224.40^{🇺🇸 FDL-AS19366209.189.224.0/21 Fibertown}
			PTR	`ns1.fibertown.com`
NS	`dns2.managednetworks.com` ⚠️ Not in zone NS records
		A	209.189.224.45^{🇺🇸 FDL-AS19366209.189.224.0/21 Fibertown}
			PTR	`ns2.fibertown.com`
NS	`ns2.fibertown.com` ⚠️ Not in parent delegation
		A	209.189.224.45^{🇺🇸 FDL-AS19366209.189.224.0/21 Fibertown}
			PTR	`ns2.fibertown.com`
NS	`ns3.fibertown.com` ⚠️ Not in parent delegation
		A	199.101.240.215^{🇺🇸 FDL-AS19366199.101.240.0/21 Fibertown}
			PTR	`ns3.fibertown.com`
NS	`ns4.fibertown.com` ⚠️ Not in parent delegation
		A	199.101.240.220^{🇺🇸 FDL-AS19366199.101.240.0/21 Fibertown}
			PTR	`ns4.fibertown.com`
TXT	`v=spf1 mx ip4:209.189.224.202 ip4:209.189.225.102 include:mail.astin.us inclu...`
TXT	`0ed1fe018ac4760593c48c44c9a064ce`
TXT	`MS=ms10204935`
SOA	`ns1.fibertown.com`hostmaster@fibertown.com serial=1173858312

`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=1784999602

WOT: UNKNOWN (62/100)
📈 Tranco rank: #425,960

Subdomains

dns2.managednetworks.com

www.managednetworks.com

dns4.managednetworks.com

dns3.managednetworks.com

dns1.managednetworks.com

Same first word

managednetworks.ca

managednetworks.co.uk

managednetworks.net

managednetworks.com

DNS History

14 records (7 active, 7 former)

●NSdns1.managednetworks.com2009-01-19 → 2026-07-25 · 2 obs

● 2009-01-19 09:32:24
● 2026-07-25 17:17:30

●NSdns2.managednetworks.com2009-01-19 → 2026-07-25 · 2 obs

● 2009-01-19 09:32:24
● 2026-07-25 17:17:30

○NSdns3.managednetworks.com2009-01-19 → 2017-01-22 · 4 obs

● 2009-01-19 09:32:24
● 2017-01-22 02:45:32
○ 2026-03-07 14:29:06
○ 2026-07-25 17:17:30

●NSns1.fibertown.com2026-03-07 → 2026-07-25 · 3 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
● 2026-07-25 17:17:30

●NSns2.fibertown.com2026-03-07 → 2026-07-25 · 3 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
● 2026-07-25 17:17:30

●NSns3.fibertown.com2026-03-07 → 2026-07-25 · 3 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
● 2026-07-25 17:17:30

●NSns4.fibertown.com2026-03-07 → 2026-07-25 · 3 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
● 2026-07-25 17:17:30

○MXmanagednetworks-com.mail.protection.outlook.com2026-03-07 → 2026-03-07 · 4 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
○ 2026-07-03 13:06:50
○ 2026-07-25 17:17:30

○MXmx1.astin.us2015-06-28 → 2017-01-22 · 5 obs

○ 2009-01-19 09:32:24
● 2015-06-28 18:57:02
● 2017-01-22 02:45:32
○ 2026-03-07 14:29:06
○ 2026-07-25 17:17:30

○MXmx2.astin.us2015-06-28 → 2017-01-22 · 5 obs

○ 2009-01-19 09:32:24
● 2015-06-28 18:57:02
● 2017-01-22 02:45:32
○ 2026-03-07 14:29:06
○ 2026-07-25 17:17:30

○MXvirtload.managednetworks.net2009-01-19 → 2009-01-19 · 3 obs

● 2009-01-19 09:32:24
○ 2015-06-28 18:57:02
○ 2026-07-25 17:17:30

○A209.189.226.732009-01-19 → 2009-01-19 · 3 obs

● 2009-01-19 09:32:24
○ 2015-06-28 18:57:02
○ 2026-07-25 17:17:30

●A209.189.247.72026-03-07 → 2026-07-25 · 3 obs

○ 2017-01-22 02:45:32
● 2026-03-07 14:29:06
● 2026-07-25 17:17:30

○A209.189.248.1642015-06-28 → 2017-01-22 · 5 obs

○ 2009-01-19 09:32:24
● 2015-06-28 18:57:02
● 2017-01-22 02:45:32
○ 2026-03-07 14:29:06
○ 2026-07-25 17:17:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
managednetworks.com	dns1.managednetworks.com, dns2.managednetworks.com	2 records

✅ Authoritative Response

Server:209.189.224.45

NS records: dns1.managednetworks.com, dns2.managednetworks.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managednetworks.com (unsigned zone)

⏱️ Timing

Total: 337ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.189.247.7`
NS	4	`ns1.fibertown.com, ns2.fibertown.com...`
TXT	3	`0ed1fe018ac4760593c48c44c9a064ce, MS=ms10204935...`
SOA	1	`ns1.fibertown.com hostmaster.fibertown.c`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (dns1.managednetworks.com, dns2.managednetworks.com)

Analysis

Hierarchy

managednetworks.com has five child domains: dns2.managednetworks.com, www.managednetworks.com, dns4.managednetworks.com, dns3.managednetworks.com and dns1.managednetworks.com.

IP Addresses

managednetworks.com resolves to one IP address: 209.189.247.7.

Name Servers

managednetworks.com carries NS records listing 6 name servers — ns1.fibertown.com, ns2.fibertown.com, ns3.fibertown.com and 3 others.

There is at least partial name server overlap between managednetworks.com and other domains — 255.189.209.in-addr.arpa, 1.107.97.in-addr.arpa, 42.81.216.in-addr.arpa and two more among them.

These name servers regularly appear alongside ns4.fibertown.com, dns1.fibertown.com, dns2.fibertown.com and 6 other name servers in NS record sets.

Hosts with just one IP address:

ns1.fibertown.com resolves to the IP address 209.189.224.40.

ns2.fibertown.com resolves to the IP address 209.189.224.45.

ns3.fibertown.com resolves to the IP address 199.101.240.215.

ns4.fibertown.com resolves to the IP address 199.101.240.220.

dns1.managednetworks.com resolves to the IP address 209.189.224.40.

dns2.managednetworks.com resolves to the IP address 209.189.224.45.

ns1.fibertown.com and dns1.managednetworks.com each have 209.189.224.40 IP addresses.

ns2.fibertown.com and dns2.managednetworks.com each have 209.189.224.45 IP addresses.