`secureconnection.com`

DNSSEC	⚠️ Not signed
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
MX	`mx.secureconnection.com` ⭐
		A	161.58.53.40^{🇺🇸 NTT-GIN-AS161.58.0.0/16 Rackdog}
TXT	`v=spf1 mx a:mx.secureconnection.com ip4:161.58.53.40 -all`
SOA	`ns1-01.azure-dns.com`dnsadmin@nttsvc.com 2020-10-22 #0

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

Previously MX for

secureconnection.com

Subdomains

mx.secureconnection.com

Same first word

secureconnection.us

secureconnection.icu

secureconnection.eu

secureconnection.net

secureconnection.nl

secureconnection.org

secureconnection.de

secureconnection.xyz

secureconnection.me

secureconnection.com

Similar names

connectionsecure.servehttp.com

rescueconnection.com

connectionsecure.com

DNS History

14 records (5 active, 9 former)

●NSns1-01.azure-dns.com2026-03-06 → 2026-05-09 · 3 obs

○ 2020-01-19 12:10:08
● 2026-03-06 11:21:46
● 2026-05-09 19:27:34

○NSns1.nttsvc.com2020-01-19 → 2020-01-19 · 4 obs

○ 2017-02-12 15:29:50
● 2020-01-19 12:10:08
○ 2026-03-06 11:21:46
○ 2026-05-09 19:27:34

○NSns1.secure.net2016-03-08 → 2017-02-12 · 5 obs

○ 2015-11-20 03:56:18
● 2016-03-08 13:44:52
● 2017-02-12 15:29:50
○ 2020-01-19 12:10:08
○ 2026-05-09 19:27:34

○NSns12.verio.de2015-07-25 → 2015-11-20 · 4 obs

● 2015-07-25 07:52:56
● 2015-11-20 03:56:18
○ 2016-03-08 13:44:52
○ 2026-05-09 19:27:34

○NSns13.verio.de2015-07-25 → 2015-11-20 · 4 obs

● 2015-07-25 07:52:56
● 2015-11-20 03:56:18
○ 2016-03-08 13:44:52
○ 2026-05-09 19:27:34

●NSns2-01.azure-dns.net2026-03-06 → 2026-05-09 · 3 obs

○ 2020-01-19 12:10:08
● 2026-03-06 11:21:46
● 2026-05-09 19:27:34

○NSns2.nttsvc.com2020-01-19 → 2020-01-19 · 4 obs

○ 2017-02-12 15:29:50
● 2020-01-19 12:10:08
○ 2026-03-06 11:21:46
○ 2026-05-09 19:27:34

○NSns2.secure.net2016-03-08 → 2017-02-12 · 5 obs

○ 2015-11-20 03:56:18
● 2016-03-08 13:44:52
● 2017-02-12 15:29:50
○ 2020-01-19 12:10:08
○ 2026-05-09 19:27:34

●NSns3-01.azure-dns.org2026-03-06 → 2026-05-09 · 3 obs

○ 2020-01-19 12:10:08
● 2026-03-06 11:21:46
● 2026-05-09 19:27:34

●NSns4-01.azure-dns.info2026-03-06 → 2026-05-09 · 3 obs

○ 2020-01-19 12:10:08
● 2026-03-06 11:21:46
● 2026-05-09 19:27:34

○MXmail-fwd.verio.de2015-07-25 → 2015-11-20 · 4 obs

● 2015-07-25 07:52:56
● 2015-11-20 03:56:18
○ 2016-03-08 13:44:52
○ 2026-05-09 19:27:34

●MXmx.secureconnection.com2017-02-12 → 2026-05-09 · 3 obs

○ 2016-07-10 04:48:40
● 2017-02-12 15:29:50
● 2026-05-09 19:27:34

○MXsecureconnection.com2016-03-08 → 2016-07-10 · 5 obs

○ 2015-11-20 03:56:18
● 2016-03-08 13:44:52
● 2016-07-10 04:48:40
○ 2017-02-12 15:29:50
○ 2026-05-09 19:27:34

○A82.112.116.1882015-07-25 → 2015-11-20 · 4 obs

● 2015-07-25 07:52:56
● 2015-11-20 03:56:18
○ 2016-03-08 13:44:52
○ 2026-05-09 19:27:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net...	-
secureconnection.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for secureconnection.com (unsigned zone)

⏱️ Timing

Total: 362ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
MX	1	`mx.secureconnection.com (pri: 10)`
TXT	1	`v=spf1 mx a:mx.secureconnection.com ip4:`
SOA	1	`ns1-01.azure-dns.com dnsadmin.nttsvc.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

secureconnection.com is the parent of mx.secureconnection.com.

Name Servers

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

secureconnection.com at least partially shares name servers with other domains, for instance 43.55.157.in-addr.arpa, no6.tv, lens.careers, pbms.com.br and usrelocation.com.

Host names with two IP numbers:

Host name ns1-01.azure-dns.com points to: 2603:1061:0:700::1 and 13.107.236.1.

Host name ns4-01.azure-dns.info points to: 2620:1ec:bda:700::1 and 208.84.5.1.

Host name ns2-01.azure-dns.net points to: 2620:1ec:8ec:700::1 and 150.171.21.1.

Host name ns3-01.azure-dns.org points to: 2a01:111:4000:700::1 and 204.14.183.1.

Mail Servers

secureconnection.com is handled by a single mail server, mx.secureconnection.com.

Host name mx.secureconnection.com points to IP address 161.58.53.40.

secureconnection.com - robtex.com