`mini-connected.ae`

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=ms92495259`
TXT	`dtm-domain-verification=Bfg-mes5fpab-lTtaatadX_1jTpcYSkpWqtdmKBdBJA`
TXT	`v=spf1 include:26fno2i3y.spf.checkpoint-spf.com include:spf.protection.outloo...`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2019-10-15 #14

`ae`

	DNSSEC	⚠️ Not signed
	NS	`ns1.aedns.ae` ⭐
	NS	`ns2.aedns.ae`
	NS	`ns4.apnic.net`
	NS	`n(0x736578)t-pch.aedns.ae`
	SOA	`ns1.aedns.ae`dns@aeda.ae serial=2013474987

Same first word

DNS History

5 records (5 active, 0 former)

●NSdns1.cscdns.net2026-05-26 → 2026-07-14 · 2 obs

● 2026-05-26 12:50:40
● 2026-07-14 11:09:18

●NSdns2.cscdns.net2026-05-26 → 2026-07-14 · 2 obs

● 2026-05-26 12:50:40
● 2026-07-14 11:09:18

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

● 2026-05-26 12:50:40
● 2026-07-14 11:09:18

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

● 2026-05-26 12:50:40
● 2026-07-14 11:09:18

●A160.46.226.1642026-05-26 → 2026-07-14 · 2 obs

● 2026-05-26 12:50:40
● 2026-07-14 11:09:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ae	ns1.aedns.ae, ns2.aedns.ae, ns4.apnic.net, n(0x736578)t-pch.aedns.ae	8 records
mini-connected.ae	dns1.cscdns.net, dns2.cscdns.net	-

✅ Authoritative Response

Server:156.154.130.100

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ae (unsigned zone)

⏱️ Timing

Total: 284ms | 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=ms92495259, dtm-domain-verification=Bfg-mes5fpab-lTt...`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

📌 Glue Records Collected

Total: 8

In-bailiwick: 6 (ns1.aedns.ae, ns1.aedns.ae, ns2.aedns.ae...)

Out-of-bailiwick: 2 (ns4.apnic.net, ns4.apnic.net)

Analysis

IP Addresses

mini-connected.ae resolves to one IP address: 160.46.226.164.

krah-enders.mini.de, isesaki.mini.jp, yamaguchi.mini.jp and two other host names share IP numbers with mini-connected.ae.

Name Servers

Two name servers handle the delegation for mini-connected.ae: dns1.cscdns.net and dns2.cscdns.net.

mini-connected.ae uses the same name servers as several other domains — among them shopwithgeorgia-pacific.org, necoflex.ie, davanti.co.nz and two more.

dns1.cscdns.net and dns2.cscdns.net both carry two IP addresses. The A records for dns1.cscdns.net are 156.154.130.100 and 2610:a1:1022::100; the A records for dns2.cscdns.net are 156.154.131.100 and 2610:a1:1023::100.

Mail Servers

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

mini-connected.ae uses an identical mail server configuration to several other domains — among them partner.bmw.com.mx, mininyc.com, mini-connected.hu and two more.

mini-connected.ae has at least partial mail server overlap with other domains such as mini-plus.co.kr, mini-stockholm.se, mini-me.com and two more.

Hostnames that resolve to 28 IP addresses:

mx1.hc324-48.eu.iphmx.com resolves to 207.54.65.242, 207.54.68.119 and 207.54.68.120 among others, with 25 other IP addresses in total.

mx2.hc324-48.eu.iphmx.com resolves to 207.54.65.242, 207.54.68.119 and 207.54.68.120 among others, with 25 other IP addresses in total.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3f9 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3fa IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3fb IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3fc IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3fd IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3fe IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2011:300::3ff IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3f9 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3fa IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3fb IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3fc IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3fd IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3fe IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 2620:101:2012:300::3ff IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.65.242 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.68.119 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.68.120 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.68.121 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.69.24 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.69.27 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.69.29 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.69.30 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.71.48 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.71.60 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.71.69 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.71.126 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.72.34 IP addresses.

mx1.hc324-48.eu.iphmx.com along with mx2.hc324-48.eu.iphmx.com each resolve to 207.54.72.35 IP addresses.

mini-connected.ae - robtex.com