securityconnection.org - dns.ninja

`securityconnection.org`

DNSSEC	⚠️ Not signed
NS	`ns1.jalex.co.za` ⭐
		A	35.209.199.186^{🇺🇸 Google35.208.0.0/15}
			PTR	`186.199.209.35.bc.googleusercontent.com`
NS	`ns2.jalex.co.za`
		A	34.60.146.207^{🇺🇸 Google34.60.0.0/16}
			PTR	`ns2.jalex.co.za`
NS	`ns3.jalex.co.za` ⚠️ Not in parent delegation
		A	105.213.179.185^{🇿🇦 MTNBUSINESS-ASN105.213.128.0/18 MTN South Africa}
			PTR	`105-213-179-185.access.supersonic.co.za`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f26.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`google-site-verification=R_fVSCmEujMlIAC3wZTHg8FNk1aaVM8hJLHasu06dOs`
SOA	`ns1.jalex.co.za`dns@jalex.co.za 2026-04-03 #15

`org`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.org.afilias-nst.info` ⭐ ⚠️ Not in parent delegation
	NS	`a2.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`c0.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`d0.org.afilias-nst.org`
	SOA	`a0.org.afilias-nst.info`hostmaster@donuts.email serial=1785140584

Subdomains

portal.securityconnection.org

ns1.securityconnection.org

ns3.securityconnection.org

Same first word

securityconnection.org

securityconnection.com

DNS History

16 records (6 active, 10 former)

●NSns1.jalex.co.za2026-04-04 → 2026-07-27 · 3 obs

○ 2026-02-16 07:30:04
● 2026-04-04 14:33:08
● 2026-07-27 08:32:42

○NSns1.lucidview.net2015-05-08 → 2017-04-02 · 4 obs

● 2015-05-08 13:58:00
● 2017-04-02 00:45:58
○ 2026-02-16 07:30:04
○ 2026-07-27 08:32:42

●NSns2.jalex.co.za2026-04-04 → 2026-07-27 · 3 obs

○ 2026-02-16 07:30:04
● 2026-04-04 14:33:08
● 2026-07-27 08:32:42

○NSns2.lucidview.net2015-05-08 → 2017-04-02 · 4 obs

● 2015-05-08 13:58:00
● 2017-04-02 00:45:58
○ 2026-02-16 07:30:04
○ 2026-07-27 08:32:42

●NSns3.jalex.co.za2026-04-04 → 2026-07-27 · 6 obs

○ 2026-02-16 07:30:04
● 2026-04-04 14:33:08
● 2026-06-08 03:12:02
○ 2026-07-18 09:03:52
● 2026-07-27 08:32:40
● 2026-07-27 08:32:42

○NSns3.lucidview.net2015-05-08 → 2017-04-02 · 4 obs

● 2015-05-08 13:58:00
● 2017-04-02 00:45:58
○ 2026-02-16 07:30:04
○ 2026-07-27 08:32:42

○NSns3.totalnameservers.com2026-02-16 → 2026-02-16 · 4 obs

○ 2017-04-02 00:45:58
● 2026-02-16 07:30:04
○ 2026-04-04 14:33:08
○ 2026-07-27 08:32:42

○NSns3.totalnameservers.com.securityconnection.org2026-02-16 → 2026-02-16 · 4 obs

○ 2017-04-02 00:45:58
● 2026-02-16 07:30:04
○ 2026-04-04 14:33:08
○ 2026-07-27 08:32:42

○NSns4.totalnameservers.com2026-02-16 → 2026-02-16 · 4 obs

○ 2017-04-02 00:45:58
● 2026-02-16 07:30:04
○ 2026-04-04 14:33:08
○ 2026-07-27 08:32:42

●MXalt1.aspmx.l.google.com2017-04-02 → 2026-07-27 · 6 obs

○ 2016-03-24 12:51:10
● 2017-04-02 00:45:58
● 2026-06-08 03:12:02
○ 2026-07-18 09:03:52
● 2026-07-27 08:32:40
● 2026-07-27 08:32:42

●MXalt2.aspmx.l.google.com2017-04-02 → 2026-07-27 · 6 obs

○ 2016-03-24 12:51:10
● 2017-04-02 00:45:58
● 2026-06-08 03:12:02
○ 2026-07-18 09:03:52
● 2026-07-27 08:32:40
● 2026-07-27 08:32:42

○MXalt3.aspmx.l.google.com2017-04-02 → 2017-04-02 · 4 obs

○ 2016-03-24 12:51:10
● 2017-04-02 00:45:58
○ 2026-02-16 07:30:04
○ 2026-07-27 08:32:42

○MXalt4.aspmx.l.google.com2017-04-02 → 2017-04-02 · 4 obs

○ 2016-03-24 12:51:10
● 2017-04-02 00:45:58
○ 2026-02-16 07:30:04
○ 2026-07-27 08:32:42

●MXaspmx.l.google.com2015-05-08 → 2026-07-27 · 5 obs

● 2015-05-08 13:58:00
● 2026-06-08 03:12:02
○ 2026-07-18 09:03:52
● 2026-07-27 08:32:40
● 2026-07-27 08:32:42

○MXmail.lucidview.net2015-05-08 → 2016-03-24 · 4 obs

● 2015-05-08 13:58:00
● 2016-03-24 12:51:10
○ 2017-04-02 00:45:58
○ 2026-07-27 08:32:42

○A41.66.190.1132015-05-08 → 2026-02-16 · 4 obs

● 2015-05-08 13:58:00
● 2026-02-16 07:30:04
○ 2026-04-04 14:33:08
○ 2026-07-27 08:32:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
org	b2.org.afilias-nst.org, d0.org.afilias-nst.org, b0.org.afilias-nst.org	-
securityconnection.org	ns1.jalex.co.za, ns2.jalex.co.za	-

✅ Authoritative Response

Server:35.209.199.186

NS records: ns1.jalex.co.za, ns2.jalex.co.za

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securityconnection.org (unsigned zone)

⏱️ Timing

Total: 1764ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`ns3.jalex.co.za, ns1.jalex.co.za...`
MX	3	`ALT2.ASPMX.L.GOOGLE.COM (pri: 10), ASPMX.L.GOOGLE.COM (pri: 1)...`
TXT	1	`google-site-verification=R_fVSCmEujMlIAC`
SOA	1	`ns1.jalex.co.za dns.jalex.co.za`

Analysis

Hierarchy

portal.securityconnection.org, ns1.securityconnection.org and ns3.securityconnection.org each fall under the parent domain securityconnection.org.

Name Servers

DNS for securityconnection.org is handled by three authoritative name servers: ns1.jalex.co.za, ns2.jalex.co.za and ns3.jalex.co.za.

securityconnection.org partially shares its NS delegation with several other domains, including jalex.co.za, lucidview.co.za, lucidview.org and two others.

These name servers often co-occur with the name servers ns4.jalex.co.za.

ns1.jalex.co.za, ns2.jalex.co.za and ns3.jalex.co.za all have one IP address each — ns1.jalex.co.za directs to 35.209.199.186, ns2.jalex.co.za directs to 34.60.146.207 and ns3.jalex.co.za directs to 105.213.179.185.

Mail Servers

securityconnection.org uses three mail servers — aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

There is at least a partial MX overlap between securityconnection.org and other domains, including gaoi.org, ns500698.ns500698.ns500698.ns500735.ns500736.ns500735.ns500576.ns500686.ns500652.ns500619.ns500619.trackreceptor.com, ns500754.ns500671.ns500754.ns500742.ns500731.ns500671.ns500731.ns500705.ns500688.ns500678.ns500671.ns500649.ns500291.ns500291.ns500291.ns500131.lustychickser.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Three hostnames — aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com — each have two IP addresses: aspmx.l.google.com has 172.253.62.27 and 2607:f8b0:4004:c27::1a, alt1.aspmx.l.google.com has 108.177.123.27 and 2800:3f0:4003:c0f::1b, and alt2.aspmx.l.google.com has 172.253.116.27 and 2a00:1450:400b:c02::1a.