harness.com.mx - robtex.com
harness.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | cloud1.triara.com ⚠️ Not in zone NS records | ||||||
| A | 200.57.128.148🇲🇽 AS19373200.57.128.0/20 LACNIC generated route for Triara.com S.A. de C.V. | ||||||
| PTR | cloud3.triara.com | ||||||
| NS | cloud2.triara.com ⚠️ Not in zone NS records | ||||||
| A | 200.57.185.72🇲🇽 AS19373200.57.184.0/21 LACNIC generated route for Triara.com S.A. de C.V. | ||||||
| PTR | cloud2.triara.com | ||||||
| NS | cloud3.triara.com ⚠️ Not in zone NS records | ||||||
| A | 200.57.128.148🇲🇽 AS19373200.57.128.0/20 LACNIC generated route for Triara.com S.A. de C.V. | ||||||
| PTR | cloud3.triara.com | ||||||
com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | m.mx-ns.mx ⭐ ⚠️ Not in parent delegation | ||||||
| NS | c.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | e.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | i.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | o.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | x.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1784083027 | ||||||
Same first word
Similar names
DNS History
11 records (3 active, 8 former)
●NScloud1.triara.com2026-06-27 → 2026-07-15 · 3 obs
● 2026-06-27 08:37:18
● 2026-07-15 02:40:24
●NScloud2.triara.com2026-06-27 → 2026-07-15 · 3 obs
● 2026-06-27 08:37:18
● 2026-07-15 02:40:24
●NScloud3.triara.com2026-06-27 → 2026-07-15 · 3 obs
● 2026-06-27 08:37:18
● 2026-07-15 02:40:24
○NSdns1.triara.com2015-07-13 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
○NSdns2.triara.com2015-07-13 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
○NSdns3.triara.com2015-07-13 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
○MXmaila.correonegocios.com2015-07-13 → 2016-04-29 · 4 obs
● 2016-04-29 22:21:22
○ 2017-01-08 23:28:28
○ 2026-07-15 02:40:24
○MXmaila.exchangeadministrado.com2017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
○MXmailb.correonegocios.com2015-07-13 → 2016-04-29 · 4 obs
● 2016-04-29 22:21:22
○ 2017-01-08 23:28:28
○ 2026-07-15 02:40:24
○MXmailb.exchangeadministrado.com2017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
○A200.57.128.472015-07-13 → 2017-01-08 · 4 obs
● 2017-01-08 23:28:28
○ 2026-06-27 08:37:18
○ 2026-07-15 02:40:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | o.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, c.mx-ns.mx... | - |
| harness.com.mx | cloud1.triara.com, cloud2.triara.com, cloud3.triara.com | - |
✅ Authoritative Response
Server:200.57.185.72
NS records: cloud1.triara.com, cloud2.triara.com, cloud3.triara.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for harness.com.mx (unsigned zone)
⏱️ Timing
Total: 1019ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
harness.com.mx carries NS records delegating to cloud1.triara.com, cloud2.triara.com and cloud3.triara.com.
harness.com.mx shares at least some of its name servers with other domains, including proyectosintesis.com, solumat.com.mx, tymelizondo.com.mx and two others.
The hostnames cloud1.triara.com, cloud2.triara.com and cloud3.triara.com each have one IP address. cloud1.triara.com resolves to 200.57.128.148; cloud2.triara.com resolves to 200.57.185.72; cloud3.triara.com resolves to 200.57.128.148 — the same address as cloud1.triara.com.
cloud1.triara.com along with cloud3.triara.com each resolve to 200.57.128.148 IP addresses.