teamcomputer.co - dns.ninja

`teamcomputer.co`

DNSSEC	⚠️ Not signed
A	198.251.81.49^{🇺🇸 FRANTECH198.251.81.0/24 More specific routing object}
		PTR	`d2mail49.my-control-panel.com`
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	`redytec-co.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr05cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch1pr04cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00100.inbound.protection.outlook.com`
		A	52.101.10.16^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	52.101.11.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00205.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.50.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00502.inbound.protection.outlook.com`
MX	`10.mail.teamcomputer.co`⁽¹⁾
TXT	`v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`nameserver01.mi.com.co`hostmaster@teamcomputer.co 2026-04-29 #7

`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=1759729542

Subdomains

mail.teamcomputer.co

Same first word

teamcomputer.co

teamcomputer.in

Similar names

DNS History

10 records (7 active, 3 former)

●NSnameserver01.mi.com.co2026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

●NSnameserver02.mi.com.co2026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

●NSnameserver03.mi.com.co2026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

●NSnameserver04.mi.com.co2026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

○NSns.teamcomputer.co2015-06-28 → 2017-08-28 · 4 obs

● 2015-06-28 20:42:48
● 2017-08-28 05:41:36
○ 2026-02-23 07:07:34
○ 2026-08-10 11:13:20

●MX10.mail.teamcomputer.co2026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

●MXredytec-co.mail.protection.outlook.com2026-05-01 → 2026-08-10 · 3 obs

○ 2026-02-23 07:07:34
● 2026-05-01 14:15:12
● 2026-08-10 11:13:20

○MXsmtp.teamcomputer.co2015-06-28 → 2017-08-28 · 4 obs

● 2015-06-28 20:42:48
● 2017-08-28 05:41:36
○ 2026-02-23 07:07:34
○ 2026-08-10 11:13:20

○A190.147.19.442015-06-28 → 2017-08-28 · 4 obs

● 2015-06-28 20:42:48
● 2017-08-28 05:41:36
○ 2026-02-23 07:07:34
○ 2026-08-10 11:13:20

●A198.251.81.492026-02-23 → 2026-08-10 · 3 obs

○ 2017-08-28 05:41:36
● 2026-02-23 07:07:34
● 2026-08-10 11:13:20

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:44.253.50.94

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for teamcomputer.co (unsigned zone)

⏱️ Timing

Total: 532ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.251.81.49`
NS	4	`nameserver04.mi.com.co, nameserver02.mi.com.co...`
MX	2	`10.mail.teamcomputer.co (pri: 1), redytec-co.mail.protection.outlook.com (`
TXT	2	`v=spf1 include:_spf.google.com include:s, v=spf1 include:spf.protection.outlook.co`
SOA	1	`nameserver01.mi.com.co hostmaster.teamco`

Analysis

Hierarchy

The domain mail.teamcomputer.co falls under the parent teamcomputer.co.

IP Addresses

teamcomputer.co points to a single IP number: 198.251.81.49.

Additional host names — imagingthefuture.ch, mail.alkits.net, aware-project.eu and two others — share IP numbers with teamcomputer.co.

Name Servers

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

At least some of teamcomputer.co's name servers are shared with other domains, for example ecobrisa.co, identificamosdecolombia.com, grafismo.co and two more.

Four hostnames, each resolving to a pair of IP addresses: nameserver01.mi.com.co directs to 52.45.124.85 and 2800:1e0:d31:5::b; nameserver02.mi.com.co directs to 44.253.50.94 and 2800:1e0:d31:5::c; nameserver03.mi.com.co directs to 56.126.23.240 and 2800:1e0:d31:5::a; nameserver04.mi.com.co directs to 63.180.140.204 and 2800:1e0:d31:5::8.

Mail Servers

teamcomputer.co has two mail servers: 10.mail.teamcomputer.co and redytec-co.mail.protection.outlook.com.

Host names with 8 IP numbers:

redytec-co.mail.protection.outlook.com maps to 52.101.10.16, 52.101.11.13, 52.101.11.15 and 5 additional IP addresses.