proactiveconnect.com - dns.ninja

`proactiveconnect.com`

DNSSEC	⚠️ Not signed
A	70.180.192.142^{🇺🇸 CCINET70.180.128.0/17 NETBLK-LV-ON-HFC-70-180-128-0}
		PTR	`ip70-180-192-142.lv.lv.cox.net`
NS	`ns2.no-ip.com` ⭐
		A	2a07:dc00:180::53^{🇺🇸 AS299972a07:dc00:180::/44}
			PTR	`ns2.no-ip.com`
		A	194.62.180.53^{🇺🇸 AS29997194.62.180.0/24}
			PTR	`ns2.no-ip.com`
NS	`ns1.no-ip.com`
		A	2a07:dc00:1810::53^{🇺🇸 AS299972a07:dc00:1810::/44}
			PTR	`ns1.no-ip.com`
		A	194.62.181.53^{🇺🇸 AS29997194.62.181.0/24}
			PTR	`ns1.no-ip.com`
NS	`ns3.no-ip.com`
		A	2a07:dc00:2550::53^{🇺🇸 AS299972a07:dc00:2550::/44}
			PTR	`ns3.no-ip.com`
		A	204.16.255.53^{🇺🇸 AS29997204.16.255.0/24 Vultr Customer Route}
			PTR	`ns3.no-ip.com`
NS	`ns4.no-ip.com`
		A	2620:0:2e64::53^{🇺🇸 AS299972620:0:2e64::/48 Vitalwerks Internet Solutions, LLC dba No-IP}
			PTR	`ns4.no-ip.com`
		A	204.16.254.53^{🇺🇸 AS29997204.16.254.0/24 Vultr Customer Route}
			PTR	`ns4.no-ip.com`
NS	`ns5.no-ip.com` ⚠️ Not in parent delegation
		A	194.62.181.53^{🇺🇸 AS29997194.62.181.0/24}
			PTR	`ns1.no-ip.com`
MX	`proactiveconnect-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00505.inbound.protection.outlook.com`
		A	2a01:111:f403:c927::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:c931::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr05cu00101.inbound.protection.outlook.com`
		A	52.101.8.34^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.11.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
		A	52.101.194.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`MS=ms54407044`
SOA	`ns2.no-ip.com`hostmaster@no-ip.com serial=2007074366

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

Same first word

proactiveconnect.com

DNS History

18 records (7 active, 11 former)

○NSns1.mydyndns.org2008-03-04 → 2020-02-11 · 4 obs

● 2008-03-04 18:36:02
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

●NSns1.no-ip.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○NSns1145.dns.dyn.com2015-06-15 → 2020-02-11 · 5 obs

○ 2008-03-04 18:36:02
● 2015-06-15 09:40:50
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

○NSns2.mydyndns.org2008-03-04 → 2008-03-04 · 3 obs

● 2008-03-04 18:36:02
○ 2015-06-15 09:40:50
○ 2026-08-15 05:13:26

●NSns2.no-ip.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○NSns2136.dns.dyn.com2015-06-15 → 2020-02-11 · 5 obs

○ 2008-03-04 18:36:02
● 2015-06-15 09:40:50
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

○NSns3.mydyndns.org2008-03-04 → 2008-03-04 · 3 obs

● 2008-03-04 18:36:02
○ 2015-06-15 09:40:50
○ 2026-08-15 05:13:26

●NSns3.no-ip.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○NSns3193.dns.dyn.com2015-06-15 → 2020-02-11 · 5 obs

○ 2008-03-04 18:36:02
● 2015-06-15 09:40:50
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

○NSns4.mydyndns.org2008-03-04 → 2008-03-04 · 3 obs

● 2008-03-04 18:36:02
○ 2015-06-15 09:40:50
○ 2026-08-15 05:13:26

●NSns4.no-ip.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○NSns4167.dns.dyn.com2015-06-15 → 2020-02-11 · 5 obs

○ 2008-03-04 18:36:02
● 2015-06-15 09:40:50
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

○NSns5.mydyndns.org2008-03-04 → 2008-03-04 · 3 obs

● 2008-03-04 18:36:02
○ 2015-06-15 09:40:50
○ 2026-08-15 05:13:26

●NSns5.no-ip.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○MXmail.proactiveconnect.com2015-06-15 → 2020-02-11 · 5 obs

○ 2008-03-04 18:36:02
● 2015-06-15 09:40:50
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

●MXproactiveconnect-com.mail.protection.outlook.com2026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

○A65.108.182.1142008-03-04 → 2020-02-11 · 4 obs

● 2008-03-04 18:36:02
● 2020-02-11 12:37:48
○ 2026-08-15 05:13:24
○ 2026-08-15 05:13:26

●A70.180.192.1422026-08-15 → 2026-08-15 · 3 obs

○ 2020-02-11 12:37:48
● 2026-08-15 05:13:24
● 2026-08-15 05:13:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
proactiveconnect.com	ns3.no-ip.com, ns2.no-ip.com, ns1.no-ip.com, ns4.no-ip.com	8 records

✅ Authoritative Response

Server:194.62.181.53

NS records: ns3.no-ip.com, ns2.no-ip.com, ns1.no-ip.com, ns4.no-ip.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for proactiveconnect.com (unsigned zone)

⏱️ Timing

Total: 327ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`70.180.192.142`
NS	5	`ns5.no-ip.com, ns3.no-ip.com...`
MX	1	`proactiveconnect-com.mail.protection.out`
TXT	2	`MS=ms54407044, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns2.no-ip.com hostmaster.no-ip.com`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns3.no-ip.com, ns3.no-ip.com, ns2.no-ip.com...)

Analysis

IP Addresses

proactiveconnect.com directs to one IP number, which is 70.180.192.142.

Name Servers

The authoritative name servers for proactiveconnect.com are ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com and two others.

There is at least partial name server overlap between proactiveconnect.com and other domains — androoka.net, mn.pp.se, sandhillsolutions.net and two more among them.

These name servers are routinely co-deployed with the name servers ns4.no-ip.com, ns5.no-ip.com, static-1.no-ip.com and two others.

Hosts with two IP numbers each:

ns1.no-ip.com maps to two IP addresses — 194.62.181.53 and 2a07:dc00:1810::53.

ns2.no-ip.com maps to two IP addresses — 194.62.180.53 and 2a07:dc00:180::53.

ns3.no-ip.com maps to two IP addresses — 204.16.255.53 and 2a07:dc00:2550::53.

ns4.no-ip.com maps to two IP addresses — 204.16.254.53 and 2620:0:2e64::53.

Hosts that resolve to one IP address:

ns5.no-ip.com points to the IP address 194.62.181.53.

These two host names — ns1.no-ip.com and ns5.no-ip.com — each point to 194.62.181.53 IP addresses.

Mail Servers

proactiveconnect.com routes its mail through a single mail server, proactiveconnect-com.mail.protection.outlook.com.

proactiveconnect-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.8.34, 52.101.9.17 and 52.101.11.17, along with 5 other.