`mini-connected.co.za`

DNSSEC	⚠️ Not signed
NS	`dns1.cscdns.net` ⭐
		A	2610:a1:1022::100^{🇺🇸 MAINT-ID-120082610:a1:1022::/48 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
		A	156.154.130.100^{🇺🇸 MAINT-ID-12008156.154.130.0/24 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`ns5.bac.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`g.ns-bac.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
NS	`dns2.cscdns.net`
		A	2610:a1:1023::100^{🇺🇸 MAINT-ID-120082610:a1:1023::/48 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
		A	156.154.131.100^{🇺🇸 MAINT-ID-12008156.154.131.0/24 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`ns9.bac.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
			PTR	`h.ns-bac.org`
MX	`mx1.hc324-48.eu.iphmx.com` ⭐
		A	2620:101:2011:300::3f9^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fa^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fb^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fc^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fd^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fe^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3ff^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3f9^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fa^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fb^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fc^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fd^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fe^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3ff^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.65.242^{🇺🇸 CISCO-2207.54.65.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.68.119^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.68.120^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.68.121^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.69.24^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.27^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.29^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.30^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.71.48^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.60^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.69^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.126^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.72.34^{🇺🇸 CISCO-2207.54.72.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.72.35^{🇺🇸 CISCO-2207.54.72.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
MX	`mx2.hc324-48.eu.iphmx.com`⁽²⁰⁾
		A	2620:101:2011:300::3f9^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fa^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fb^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fc^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fd^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3fe^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2011:300::3ff^{🇺🇸 CISCO-22620:101:2011::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3f9^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fa^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fb^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fc^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fd^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3fe^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	2620:101:2012:300::3ff^{🇺🇸 CISCO-22620:101:2012::/48 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.65.242^{🇺🇸 CISCO-2207.54.65.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.68.119^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.68.120^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.68.121^{🇺🇸 CISCO-2207.54.68.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.69.24^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.27^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.29^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.69.30^{🇺🇸 CISCO-2207.54.69.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.71.48^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.60^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.69^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.71.126^{🇺🇸 CISCO-2207.54.71.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	207.54.72.34^{🇺🇸 CISCO-2207.54.72.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
		A	207.54.72.35^{🇺🇸 CISCO-2207.54.72.0/24 Cisco Systems Ironport Division Rondebeltweg 62 Almere, State-Flevoland 1329 BG Netherlands}
TXT	`MS=ms47757203`
TXT	`dtm-domain-verification=X6MLtKDsxEi5DgyhsSM-LDAMts4_ANlJ84G7XwSXFFI`
TXT	`v=spf1 include:257rycytu.spf.checkpoint-spf.com include:spf.protection.outloo...`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2019-10-10 #10

`co.za`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.coza.net.za` ⭐
	NS	`coza1.dnsnode.net`
	NS	`ns2.dns.net.za`
	NS	`ns2us.dns.business`
	NS	`ns5.dns.net.za`
	MX	`mx2.dns.business` ⭐
	TXT	`google-site-verification=likJ1inLA3BiWH30vLTURD5kbYZshPreaO0bQH_pMVM`
	TXT	`v=spf1 a:mail.coza.net.za a:mx2.coza.net.za a:mail.registry.net.za include:_...`
	SOA	`ns.coza.net.za`this-is-probably-not-the-email-address-you-are-looking-for@co.za serial=2025078255

rank #678285 globally
rank #1240 in the tld
WOT: SAFE (72/100)

Same first word

DNS History

4 records (4 active, 0 former)

●NSdns1.cscdns.net2026-06-02 → 2026-07-14 · 2 obs

● 2026-06-02 06:38:58
● 2026-07-14 23:23:24

●NSdns2.cscdns.net2026-06-02 → 2026-07-14 · 2 obs

● 2026-06-02 06:38:58
● 2026-07-14 23:23:24

●MXmx1.hc324-48.eu.iphmx.com2026-06-02 → 2026-07-14 · 2 obs

● 2026-06-02 06:38:58
● 2026-07-14 23:23:24

●MXmx2.hc324-48.eu.iphmx.com2026-06-02 → 2026-07-14 · 2 obs

● 2026-06-02 06:38:58
● 2026-07-14 23:23:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
za	nsza.is.co.za, za1.dnsnode.net, za-ns.anycast.pch.net	5 records
mini-connected.co.za	dns1.cscdns.net, dns2.cscdns.net	-

✅ Authoritative Response

Server:156.154.131.100

NS records: dns1.cscdns.net, dns2.cscdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mini-connected.co.za (unsigned zone)

⏱️ Timing

Total: 1068ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.cscdns.net, dns2.cscdns.net`
MX	2	`mx1.hc324-48.eu.iphmx.com (pri: 10), mx2.hc324-48.eu.iphmx.com (pri: 20)`
TXT	3	`MS=ms47757203, dtm-domain-verification=X6MLtKDsxEi5Dgyh...`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

📌 Glue Records Collected

Total: 5

In-bailiwick: 1 (nsza.is.co.za)

Out-of-bailiwick: 4 (za-ns.anycast.pch.net, za1.dnsnode.net, za-ns.anycast.pch.net...)

Analysis

Name Servers

mini-connected.co.za is delegated to two name servers: dns1.cscdns.net and dns2.cscdns.net.

mini-connected.co.za uses the same name servers as several other domains — among them jedichallenges.org, wirelesstdwaterhouse.com, caldic.org and two more.

mini-connected.co.za shares at least some of its name servers with other domains, such as hemul.dk.

dns1.cscdns.net and dns2.cscdns.net each resolve to two IP addresses: dns1.cscdns.net points to 156.154.130.100 and 2610:a1:1022::100, while dns2.cscdns.net points to 156.154.131.100 and 2610:a1:1023::100.

Mail Servers

Mail for mini-connected.co.za is handled by two mail servers — mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com.

mini-connected.co.za uses an identical mail server configuration to several other domains — among them mini.lu, minifs.cz, mini.my and two more.

Some mail servers of mini-connected.co.za are also used by other domains, notably mini-plus.co.kr and bmw-plus.co.kr.

Hostnames that resolve to 28 IP addresses:

mx1.hc324-48.eu.iphmx.com resolves to 207.54.65.242, 207.54.68.119, 207.54.68.120 and 25 other IP addresses.

mx2.hc324-48.eu.iphmx.com resolves to 207.54.65.242, 207.54.68.119, 207.54.68.120 and 25 other IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3f9 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3fa IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3fb IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3fc IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3fd IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3fe IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2011:300::3ff IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3f9 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3fa IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3fb IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3fc IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3fd IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3fe IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 2620:101:2012:300::3ff IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.65.242 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.68.119 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.68.120 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.68.121 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.69.24 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.69.27 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.69.29 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.69.30 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.71.48 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.71.60 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.71.69 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.71.126 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.72.34 IP addresses.

mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com are host names that each point to 207.54.72.35 IP addresses.

mini-connected.co.za - robtex.com