taskforcedns.com - dns.ninja
taskforcedns.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | nameserver01.mi.com.co ⭐ | ||||||
| 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 | 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 | 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 | 63.180.140.204🇺🇸 Amazon63.180.0.0/14 EC2 FRA Prefix | ||||||
| PTR | ec2-63-180-140-204.eu-central-1.compute.amazonaws.com | ||||||
| SOA | nameserver01.mi.com.cohostmaster@taskforcedns.com 2026-05-25 #12 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1784004882 | ||||||
Previously MX for
taskforcedns.com |
Same first word
taskforcedns.com |
DNS History
8 records (4 active, 4 former)
●NSnameserver01.mi.com.co2026-03-15 → 2026-07-14 · 3 obs
● 2026-03-15 05:37:56
● 2026-07-14 05:18:58
●NSnameserver02.mi.com.co2026-03-15 → 2026-07-14 · 3 obs
● 2026-03-15 05:37:56
● 2026-07-14 05:18:58
●NSnameserver03.mi.com.co2026-03-15 → 2026-07-14 · 3 obs
● 2026-03-15 05:37:56
● 2026-07-14 05:18:58
●NSnameserver04.mi.com.co2026-03-15 → 2026-07-14 · 3 obs
● 2026-03-15 05:37:56
● 2026-07-14 05:18:58
○NSns1.taskforcedns.com2015-08-20 → 2017-05-25 · 4 obs
● 2017-05-25 16:33:12
○ 2026-03-15 05:37:56
○ 2026-07-14 05:18:58
○NSns2.taskforcedns.com2015-12-19 → 2017-05-25 · 5 obs
● 2015-12-19 15:21:22
● 2017-05-25 16:33:12
○ 2026-03-15 05:37:56
○ 2026-07-14 05:18:58
○MXtaskforcedns.com2015-12-19 → 2017-05-25 · 4 obs
● 2017-05-25 16:33:12
○ 2026-03-15 05:37:56
○ 2026-07-14 05:18:58
○A174.142.189.1382015-08-20 → 2017-05-25 · 4 obs
● 2017-05-25 16:33:12
○ 2026-03-15 05:37:56
○ 2026-07-14 05:18:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| taskforcedns.com | nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co, nameserver04.mi.com.co | - |
✅ Authoritative Response
Server:52.45.124.85
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 taskforcedns.com (unsigned zone)
⏱️ Timing
Total: 417ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | nameserver04.mi.com.co, nameserver02.mi.com.co... |
| SOA | 1 | nameserver01.mi.com.co hostmaster.taskfo |
Analysis
Name Servers
The NS records for taskforcedns.com point to four name servers: nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co and nameserver04.mi.com.co.
There is at least partial name server overlap between taskforcedns.com and other domains — cargadirecta.co, lopezylopezabogados.com, geofisicos.com.co and two more among them.
These name servers frequently co-occur with the name servers expired1.mi.com.co and expired2.mi.com.co.
The hosts nameserver01.mi.com.co, nameserver02.mi.com.co, nameserver03.mi.com.co and nameserver04.mi.com.co all resolve to exactly one IP address each: 52.45.124.85, 44.253.50.94, 56.126.23.240 and 63.180.140.204 respectively.