networksensor.com - dns.ninja

`networksensor.com`

DNSSEC	⚠️ Not signed
A	38.106.30.254^{🇺🇸 AS27405038.106.30.0/24 Route Registered for Cogent Communications Customer - Youneed communication}
NS	`ns1.multiprotocol.com` ⭐
		A	45.32.193.219^{🇺🇸 AS-VULTR45.32.192.0/20 Vultr Assigned Prefix}
			PTR	`45.32.193.219.vultrusercontent.com`
NS	`ns.multiprotocol.com`
		A	207.148.13.179^{🇺🇸 AS-VULTR207.148.8.0/21 Vultr Assigned Prefix}
			PTR	`ns.multiprotocol.com`
NS	`ns2.multiprotocol.com`
		A	45.63.8.240^{🇺🇸 AS-VULTR45.63.0.0/20 Vultr Assigned Prefix}
			PTR	`45.63.8.240.vultrusercontent.com`
MX	`networksensor-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:f804::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr03cu00403.inbound.protection.outlook.com`
		A	2a01:111:f403:f907::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm1pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr21cu00100.inbound.protection.outlook.com`
		A	52.101.8.51^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm1pr04cu00203.inbound.protection.outlook.com`
		A	52.101.11.19^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr04cu00203.inbound.protection.outlook.com`
		A	52.101.41.58^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr02cu00102.inbound.protection.outlook.com`
		A	52.101.41.183^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00307.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`MS=ms44730894`
SOA	`ns.multiprotocol.com`hostmaster@multiprotocol.com 2005-12-20 #4

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

Same first word

networksensor.org

networksensor.com

networksensor.net

Similar names

sensornetwork.eu

sensornetwork.com

sensornetwork.net

DNS History

11 records (5 active, 6 former)

●NSns.multiprotocol.com2015-08-12 → 2026-07-26 · 2 obs

● 2015-08-12 12:33:44
● 2026-07-26 22:00:10

●NSns1.multiprotocol.com2015-08-12 → 2026-07-26 · 2 obs

● 2015-08-12 12:33:44
● 2026-07-26 22:00:10

●NSns2.multiprotocol.com2015-08-12 → 2026-07-26 · 2 obs

● 2015-08-12 12:33:44
● 2026-07-26 22:00:10

○MXmx1.intechrety.com2020-01-28 → 2020-01-28 · 4 obs

○ 2017-04-03 22:17:32
● 2020-01-28 09:15:56
○ 2026-02-19 12:32:00
○ 2026-07-26 22:00:10

○MXmx2.intechrety.com2020-01-28 → 2020-01-28 · 4 obs

○ 2017-04-03 22:17:32
● 2020-01-28 09:15:56
○ 2026-02-19 12:32:00
○ 2026-07-26 22:00:10

○MXmx3.intechrety.com2020-01-28 → 2020-01-28 · 4 obs

○ 2017-04-03 22:17:32
● 2020-01-28 09:15:56
○ 2026-02-19 12:32:00
○ 2026-07-26 22:00:10

●MXnetworksensor-com.mail.protection.outlook.com2026-02-19 → 2026-07-26 · 3 obs

○ 2020-01-28 09:15:56
● 2026-02-19 12:32:00
● 2026-07-26 22:00:10

○MXscrolloutf1-2.networksensor.com2015-08-12 → 2017-04-03 · 4 obs

● 2015-08-12 12:33:44
● 2017-04-03 22:17:32
○ 2020-01-28 09:15:56
○ 2026-07-26 22:00:10

○MXscrolloutf1.networksensor.com2015-08-12 → 2017-04-03 · 4 obs

● 2015-08-12 12:33:44
● 2017-04-03 22:17:32
○ 2020-01-28 09:15:56
○ 2026-07-26 22:00:10

○A205.134.235.2532015-08-12 → 2017-04-03 · 4 obs

● 2015-08-12 12:33:44
● 2017-04-03 22:17:32
○ 2020-01-28 09:15:56
○ 2026-07-26 22:00:10

●A38.106.30.2542020-01-28 → 2026-07-26 · 3 obs

○ 2017-04-03 22:17:32
● 2020-01-28 09:15:56
● 2026-07-26 22:00:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
networksensor.com	ns.multiprotocol.com, ns1.multiprotocol.com, ns2.multiprotocol.com	3 records

✅ Authoritative Response

Server:207.148.13.179

NS records: ns.multiprotocol.com, ns1.multiprotocol.com, ns2.multiprotocol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for networksensor.com (unsigned zone)

⏱️ Timing

Total: 189ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`38.106.30.254`
NS	3	`ns1.multiprotocol.com, ns2.multiprotocol.com...`
MX	1	`networksensor-com.mail.protection.outloo`
TXT	2	`v=spf1 include:spf.protection.outlook.co, MS=ms44730894`
SOA	1	`ns.multiprotocol.com hostmaster.multipro`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns.multiprotocol.com, ns1.multiprotocol.com, ns2.multiprotocol.com)

Analysis

IP Addresses

networksensor.com directs to one IP number, which is 38.106.30.254.

Name Servers

networksensor.com has three name servers — ns1.multiprotocol.com, ns2.multiprotocol.com and ns.multiprotocol.com.

networksensor.com shares at least some of its name servers with other domains, including networksensor.org, multiprotocol.com, intechrety.com and two others.

Each of the three hostnames points to exactly one IP address: ns1.multiprotocol.com points to 45.32.193.219, ns2.multiprotocol.com points to 45.63.8.240 and ns.multiprotocol.com points to 207.148.13.179.

Mail Servers

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

networksensor-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.8.51, 52.101.11.19 and 52.101.41.58, along with 5 other.