`securedconnectivity.net`

DNSSEC	⚠️ Not signed
A	52.86.242.172^{🇺🇸 Amazon52.86.0.0/15 EC2 IAD prefix}
		PTR	`ec2-52-86-242-172.compute-1.amazonaws.com`
NS	`dns1.p01.nsone.net` ⭐ ⚠️ Not in parent delegation
		A	2620:4d:4000:6259:7:1:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p01.nsone.net`
NS	`dns1.p03.nsone.net` ⚠️ Not in zone NS records
		A	2620:4d:4000:6259:7:3:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p03.nsone.net`
		A	198.51.44.3^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p03.nsone.net`
NS	`dns2.p01.nsone.net` ⚠️ Not in parent delegation
		A	2a00:edc0:6259:7:1::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p01.nsone.net`
		A	198.51.45.1^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns2.p01.nsone.net`
NS	`dns2.p03.nsone.net` ⚠️ Not in zone NS records
		A	2a00:edc0:6259:7:3::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p03.nsone.net`
		A	198.51.45.3^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns2.p03.nsone.net`
NS	`dns3.p01.nsone.net` ⚠️ Not in parent delegation
		A	2620:4d:4000:6259:7:1:0:3^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns3.p01.nsone.net`
		A	198.51.44.65^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns3.p01.nsone.net`
NS	`dns3.p03.nsone.net` ⚠️ Not in zone NS records
		A	2620:4d:4000:6259:7:3:0:3^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns3.p03.nsone.net`
		A	198.51.44.67^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns3.p03.nsone.net`
NS	`dns4.p01.nsone.net` ⚠️ Not in parent delegation
		A	2a00:edc0:6259:7:1::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p01.nsone.net`
		A	198.51.45.65^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns4.p01.nsone.net`
NS	`dns4.p03.nsone.net` ⚠️ Not in zone NS records
		A	2a00:edc0:6259:7:3::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p03.nsone.net`
		A	198.51.45.67^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns4.p03.nsone.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c0d::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dl-in-f27.1e100.net`
		A	142.250.101.26^{🇺🇸 Google142.250.101.0/24}
			PTR	`dz-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f26.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4023:3003::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f27.1e100.net`
		A	172.253.145.26^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.26^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f26.1e100.net`
TXT	`MS=ms75351715`
TXT	`v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com ~all`
TXT	`google-site-verification=r90h9rVDiW-WMl34vxMk09QjifUB5kHW5CHh3BGg6vU`
SOA	`dns1.p01.nsone.net`hostmaster@nsone.net serial=1563996972

`net`

	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=1774533927

Subdomains

www.securedconnectivity.net

Same first word

securedconnectivity.net

DNS History

24 records (14 active, 10 former)

●NSdns1.p01.nsone.net2018-07-31 → 2026-03-26 · 3 obs

○ 2017-12-22 14:22:34
● 2018-07-31 20:04:50
● 2026-03-26 14:25:56

●NSdns1.p03.nsone.net2026-02-15 → 2026-03-26 · 3 obs

○ 2018-07-31 20:04:50
● 2026-02-15 01:16:24
● 2026-03-26 14:25:56

●NSdns2.p01.nsone.net2018-07-31 → 2026-03-26 · 3 obs

○ 2017-12-22 14:22:34
● 2018-07-31 20:04:50
● 2026-03-26 14:25:56

●NSdns2.p03.nsone.net2026-02-15 → 2026-03-26 · 3 obs

○ 2018-07-31 20:04:50
● 2026-02-15 01:16:24
● 2026-03-26 14:25:56

●NSdns3.p01.nsone.net2018-07-31 → 2026-03-26 · 3 obs

○ 2017-12-22 14:22:34
● 2018-07-31 20:04:50
● 2026-03-26 14:25:56

●NSdns3.p03.nsone.net2026-02-15 → 2026-03-26 · 3 obs

○ 2018-07-31 20:04:50
● 2026-02-15 01:16:24
● 2026-03-26 14:25:56

●NSdns4.p01.nsone.net2018-07-31 → 2026-03-26 · 3 obs

○ 2017-12-22 14:22:34
● 2018-07-31 20:04:50
● 2026-03-26 14:25:56

●NSdns4.p03.nsone.net2026-02-15 → 2026-03-26 · 3 obs

○ 2018-07-31 20:04:50
● 2026-02-15 01:16:24
● 2026-03-26 14:25:56

○NSns1.securedconnectivity.net2016-03-10 → 2017-12-22 · 7 obs

● 2016-03-10 16:21:30
● 2016-04-01 07:16:18
○ 2016-04-11 10:44:52
● 2016-05-25 18:11:12
● 2017-12-22 14:22:34
○ 2018-07-31 20:04:50
○ 2026-03-26 14:25:56

○NSns2.securedconnectivity.net2016-03-10 → 2017-12-22 · 7 obs

● 2016-03-10 16:21:30
● 2016-04-01 07:16:18
○ 2016-04-11 10:44:52
● 2016-05-25 18:11:12
● 2017-12-22 14:22:34
○ 2018-07-31 20:04:50
○ 2026-03-26 14:25:56

○NSns71.domaincontrol.com2016-04-11 → 2016-04-11 · 4 obs

○ 2016-04-01 07:16:18
● 2016-04-11 10:44:52
○ 2016-05-25 18:11:12
○ 2026-03-26 14:25:56

○NSns72.domaincontrol.com2016-04-11 → 2016-04-11 · 4 obs

○ 2016-04-01 07:16:18
● 2016-04-11 10:44:52
○ 2016-05-25 18:11:12
○ 2026-03-26 14:25:56

●MXalt1.aspmx.l.google.com2019-08-21 → 2026-03-26 · 3 obs

○ 2018-12-23 03:13:08
● 2019-08-21 17:00:34
● 2026-03-26 14:25:56

●MXalt2.aspmx.l.google.com2019-08-21 → 2026-03-26 · 3 obs

○ 2018-12-23 03:13:08
● 2019-08-21 17:00:34
● 2026-03-26 14:25:56

●MXalt3.aspmx.l.google.com2019-08-21 → 2026-03-26 · 3 obs

○ 2018-12-23 03:13:08
● 2019-08-21 17:00:34
● 2026-03-26 14:25:56

●MXalt4.aspmx.l.google.com2019-08-21 → 2026-03-26 · 3 obs

○ 2018-12-23 03:13:08
● 2019-08-21 17:00:34
● 2026-03-26 14:25:56

●MXaspmx.l.google.com2019-08-21 → 2026-03-26 · 3 obs

○ 2018-12-23 03:13:08
● 2019-08-21 17:00:34
● 2026-03-26 14:25:56

○MXironport.emecks.com2016-07-03 → 2017-04-04 · 5 obs

○ 2016-06-22 12:19:48
● 2016-07-03 21:15:56
● 2017-04-04 19:28:22
○ 2017-12-22 14:22:34
○ 2026-03-26 14:25:56

○MXironport2.emecks.com2016-07-03 → 2017-04-04 · 5 obs

○ 2016-06-22 12:19:48
● 2016-07-03 21:15:56
● 2017-04-04 19:28:22
○ 2017-12-22 14:22:34
○ 2026-03-26 14:25:56

○MXmx1.emailsrvr.com2016-03-10 → 2016-06-22 · 4 obs

● 2016-03-10 16:21:30
● 2016-06-22 12:19:48
○ 2016-07-03 21:15:56
○ 2026-03-26 14:25:56

○MXmx2.emailsrvr.com2016-03-10 → 2016-06-22 · 4 obs

● 2016-03-10 16:21:30
● 2016-06-22 12:19:48
○ 2016-07-03 21:15:56
○ 2026-03-26 14:25:56

○MXsecuredconnectivity-net.mail.protection.outlook.com2017-12-22 → 2018-12-23 · 5 obs

○ 2017-04-04 19:28:22
● 2017-12-22 14:22:34
● 2018-12-23 03:13:08
○ 2019-08-21 17:00:34
○ 2026-03-26 14:25:56

○A107.180.44.1682016-04-11 → 2016-04-11 · 3 obs

● 2016-04-11 10:44:52
○ 2016-05-25 18:11:12
○ 2026-03-26 14:25:56

●A52.86.242.1722016-06-22 → 2026-03-26 · 3 obs

○ 2016-05-25 18:11:12
● 2016-06-22 12:19:48
● 2026-03-26 14:25:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	h.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net...	-
securedconnectivity.net	dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net	8 records

✅ Authoritative Response

Server:198.51.45.67

NS records: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securedconnectivity.net (unsigned zone)

⏱️ Timing

Total: 240ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.86.242.172`
NS	4	`dns1.p01.nsone.net, dns2.p01.nsone.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	3	`MS=ms75351715, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`dns1.p01.nsone.net hostmaster.nsone.net`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (dns1.p03.nsone.net, dns1.p03.nsone.net, dns2.p03.nsone.net...)

Analysis

Hierarchy

The parent of www.securedconnectivity.net is securedconnectivity.net.

IP Addresses

securedconnectivity.net points to a single IP address: 52.86.242.172.

Other host names, such as ec2-52-86-242-172.compute-1.amazonaws.com and www.securedconnectivity.net, share IP numbers with securedconnectivity.net.

Name Servers

securedconnectivity.net is delegated to eight name servers: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net and dns4.p03.nsone.net.

securedconnectivity.net at least partially shares name servers with other domains, for example scholistichealth.com, endlichanders.de, almocovirtual.pt, arborlanesbowling.com and growingresilience.net.

these name servers are commonly used with the following name servers: ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, ns01.squarespacedns.com, ns01.jnjdns.com, ns02.jnjdns.com, ns03.jnjdns.com, ns04.jnjdns.com, ns01.msddns.com and ns02.msddns.com.

Host names with two IPs:

dns1.p01.nsone.net maps to 2620:4d:4000:6259:7:1:0:1, 198.51.44.1

dns2.p01.nsone.net maps to 2a00:edc0:6259:7:1::2, 198.51.45.1

dns3.p01.nsone.net maps to 2620:4d:4000:6259:7:1:0:3, 198.51.44.65

dns4.p01.nsone.net maps to 2a00:edc0:6259:7:1::4, 198.51.45.65

dns1.p03.nsone.net maps to 2620:4d:4000:6259:7:3:0:1, 198.51.44.3

dns2.p03.nsone.net maps to 2a00:edc0:6259:7:3::2, 198.51.45.3

dns3.p03.nsone.net maps to 2620:4d:4000:6259:7:3:0:3, 198.51.44.67

dns4.p03.nsone.net maps to 2a00:edc0:6259:7:3::4, 198.51.45.67

Mail Servers

securedconnectivity.net is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

securedconnectivity.net shares at least partially some mail servers with other domains, for instance xignaworks.com, lotusnutrients.com, virginiacanvasworks.com, ogp.cat and fnzambra.com.