`mini-connected.com.kw`

DNSSEC	⚠️ Not signed
A	160.46.226.164^{🇩🇪 UNSPECIFIED160.46.224.0/19 Route Object BMW}
		PTR	`mini.de`
		PTR	`mini.mini.fi`
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=ms40244930`
TXT	`dtm-domain-verification=NV10orHzSZFYLigKsb89jw7r-UIk1QZZv9gvu2EZ55I`
TXT	`v=spf1 include:2f1bql3lx.spf.checkpoint-spf.com include:spf.protection.outloo...`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2019-10-22 #17

`com.kw`

	DNSSEC	⚠️ Not signed
	NS	`a.nic.kw` ⭐ ⚠️ Not in parent delegation
	NS	`b.nic.kw` ⚠️ Not in parent delegation
	NS	`c.nic.kw` ⚠️ Not in parent delegation
	NS	`d.nic.kw` ⚠️ Not in parent delegation
	NS	`pch.nic.kw` ⚠️ Not in parent delegation
	SOA	`a.nic.kw`admin@nic.kw serial=1783942261

WOT: SAFE (60/100)
WOT: SAFE (64/100)

Same first word

DNS History

5 records (5 active, 0 former)

●NSdns1.cscdns.net2026-06-01 → 2026-07-13 · 2 obs

● 2026-06-01 23:52:50
● 2026-07-13 11:48:34

●NSdns2.cscdns.net2026-06-01 → 2026-07-13 · 2 obs

● 2026-06-01 23:52:50
● 2026-07-13 11:48:34

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

● 2026-06-01 23:52:50
● 2026-07-13 11:48:34

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

● 2026-06-01 23:52:50
● 2026-07-13 11:48:34

●A160.46.226.1642026-06-01 → 2026-07-13 · 2 obs

● 2026-06-01 23:52:50
● 2026-07-13 11:48:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
kw	a.nic.kw, b.nic.kw, c.nic.kw, d.nic.kw...	8 records
mini-connected.com.kw	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.com.kw (unsigned zone)

⏱️ Timing

Total: 3381ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`160.46.226.164`
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=ms40244930, dtm-domain-verification=NV10orHzSZFYLigK...`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.nic.kw, b.nic.kw, c.nic.kw...)

Analysis

IP Addresses

mini-connected.com.kw has exactly one IP address — 160.46.226.164.

mini.it, mini.ua, mini.pt plus two other host names have IP numbers in common with mini-connected.com.kw.

Name Servers

mini-connected.com.kw has two authoritative name servers — dns1.cscdns.net and dns2.cscdns.net.

The name server configuration of mini-connected.com.kw is shared with other domains, for instance straighttalkcom.com, skyresult.com, avenuerepaid.com and two others.

The name servers for mini-connected.com.kw overlap at least partially with those of other domains — for example cfocardhistory.com.

Both dns1.cscdns.net and dns2.cscdns.net have two IP addresses each. dns1.cscdns.net resolves to 156.154.130.100 and 2610:a1:1022::100; dns2.cscdns.net resolves to 156.154.131.100 and 2610:a1:1023::100.

Mail Servers

mini-connected.com.kw uses two mail servers, mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com.

The mail server setup of mini-connected.com.kw matches that of other domains such as partner.bmw.it, mini-connected.co.za, mini.com.mx and two others.

At least a portion of mini-connected.com.kw's mail servers are shared with other domains, among them mini-plus.co.kr and bmw-plus.co.kr.

Hosts with 28 IP addresses each:

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

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

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3f9 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3fa IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3fb IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3fc IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3fd IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3fe IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2011:300::3ff IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3f9 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3fa IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3fb IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3fc IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3fd IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3fe IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 2620:101:2012:300::3ff IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.65.242 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.68.119 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.68.120 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.68.121 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.69.24 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.69.27 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.69.29 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.69.30 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.71.48 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.71.60 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.71.69 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.71.126 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.72.34 IP addresses.

The host names mx1.hc324-48.eu.iphmx.com and mx2.hc324-48.eu.iphmx.com both resolve to 207.54.72.35 IP addresses.

mini-connected.com.kw - robtex.com