controltech.co - dns.ninja

`controltech.co`

DNSSEC	⚠️ Not signed
NS	`nameserver01.mi.com.co` ⭐
		A	2800:1e0:d31:5::b^{🇨🇴 EdgeUno2800:1e0:d30::/44}
		A	52.45.124.85^{🇺🇸 Amazon52.44.0.0/15 EC2 Region prefix}
			PTR	`ec2-52-45-124-85.compute-1.amazonaws.com`
NS	`nameserver02.mi.com.co`
		A	2800:1e0:d31:5::c^{🇨🇴 EdgeUno2800:1e0:d30::/44}
		A	44.253.50.94^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
			PTR	`ec2-44-253-50-94.us-west-2.compute.amazonaws.com`
NS	`nameserver03.mi.com.co`
		A	2800:1e0:d31:5::a^{🇨🇴 EdgeUno2800:1e0:d30::/44}
		A	56.126.23.240^{🇺🇸 Amazon56.126.0.0/16 EC2 GRU prefix}
			PTR	`ec2-56-126-23-240.sa-east-1.compute.amazonaws.com`
NS	`nameserver04.mi.com.co`
		A	2800:1e0:d31:5::8^{🇨🇴 EdgeUno2800:1e0:d30::/44}
		A	63.180.140.204^{🇺🇸 Amazon63.180.0.0/14 EC2 FRA Prefix}
			PTR	`ec2-63-180-140-204.eu-central-1.compute.amazonaws.com`
MX	`mx03.mi.com.co` ⭐
		A	200.25.12.145^{🇨🇴 EdgeUno200.25.12.0/24 CIDR Block Allocated to Guadalajara}
			PTR	`smtp-out-1013.mi.com.co`
MX	`mx01.mi.com.co`⁽¹⁰⁾
		A	200.25.12.146^{🇨🇴 EdgeUno200.25.12.0/24 CIDR Block Allocated to Guadalajara}
			PTR	`smtp-out-1014.mi.com.co`
TXT	`v=spf1 include:_spf.mi.com.co ~all`
TXT	`v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6wPqhy9Mx0rYwKk...`
SOA	`nameserver01.mi.com.co`hostmaster@controltech.co 2022-09-12 #2

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759723896

Same first word

Similar names

DNS History

17 records (6 active, 11 former)

●NSnameserver01.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

●NSnameserver02.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

●NSnameserver03.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

●NSnameserver04.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

○NSns1.colombiahosting.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○NSns2.colombiahosting.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○NSns3.colombiahosting.com2020-02-25 → 2020-02-25 · 4 obs

○ 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○NSns4.colombiahosting.com2020-02-25 → 2020-02-25 · 4 obs

○ 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○MXalt1.aspmx.l.google.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○MXalt2.aspmx.l.google.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○MXaspmx.l.google.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○MXaspmx2.googlemail.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

○MXaspmx3.googlemail.com2015-06-25 → 2020-02-25 · 4 obs

● 2015-06-25 14:59:16
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

●MXmx01.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

●MXmx03.mi.com.co2026-04-07 → 2026-08-03 · 3 obs

○ 2020-02-25 18:27:26
● 2026-04-07 00:33:46
● 2026-08-03 17:06:10

○A190.8.176.102015-06-25 → 2017-02-07 · 4 obs

● 2015-06-25 14:59:16
● 2017-02-07 01:39:58
○ 2020-02-25 18:27:26
○ 2026-08-03 17:06:10

○A190.8.176.1002020-02-25 → 2020-02-25 · 4 obs

○ 2017-02-07 01:39:58
● 2020-02-25 18:27:26
○ 2026-04-07 00:33:46
○ 2026-08-03 17:06:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	-
controltech.co	nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co, nameserver04.mi.com.co	-

✅ Authoritative Response

Server:63.180.140.204

NS records: nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co, nameserver04.mi.com.co

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for controltech.co (unsigned zone)

⏱️ Timing

Total: 677ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`nameserver02.mi.com.co, nameserver03.mi.com.co...`
MX	2	`mx01.mi.com.co (pri: 10), mx03.mi.com.co (pri: 5)`
TXT	2	`v=spf1 include:_spf.mi.com.co ~all, v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQ`
SOA	1	`nameserver01.mi.com.co hostmaster.contro`

Analysis

Name Servers

controltech.co has four authoritative name servers: nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co and nameserver04.mi.com.co.

controltech.co shares at least some of its name servers with other domains, including computec.co, allianz.com.co, arp-sura.com and two others.

The host names nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co and nameserver04.mi.com.co each resolve to two IP addresses: nameserver01.mi.com.co resolves to 52.45.124.85 and 2800:1e0:d31:5::b; nameserver02.mi.com.co resolves to 44.253.50.94 and 2800:1e0:d31:5::c; nameserver03.mi.com.co resolves to 56.126.23.240 and 2800:1e0:d31:5::a; nameserver04.mi.com.co resolves to 63.180.140.204 and 2800:1e0:d31:5::8.

Mail Servers

controltech.co has two mail servers: mx01.mi.com.co and mx03.mi.com.co.

controltech.co shares the same mail server setup as other domains, including prismaabogados.com.co, multiservicioszas.com, onelove.com.co and two others.

controltech.co shares mail servers — at least in part — with other domains, including casqc.com, alfagres.com.co, coointeramericana.com and two others.

mx01.mi.com.co and mx03.mi.com.co each resolve to one IP number: mx01.mi.com.co points to 200.25.12.146 and mx03.mi.com.co points to 200.25.12.145.