humanish.com.mx - robtex.com
humanish.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=1785192877 | ||||||
Same first word
Similar names
hihumans.com |
muhsinah.com |
himanshu.ca |
shanhumi.com |
himanshu.net |
himanshu.pro |
hshuamin.com |
himanshu.me |
himanshu.com |
himanshu.us |
himanshu.cloudapp.net |
DNS History
10 records (3 active, 7 former)
●NScloud1.triara.com2026-06-27 → 2026-07-27 · 3 obs
○ 2017-03-28 18:02:52
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
●NScloud2.triara.com2026-06-27 → 2026-07-27 · 3 obs
○ 2017-03-28 18:02:52
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
●NScloud3.triara.com2026-06-27 → 2026-07-27 · 3 obs
○ 2017-03-28 18:02:52
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
● 2026-06-27 02:07:44
● 2026-07-27 23:07:12
○NSdns1.triara.com2015-07-14 → 2017-03-28 · 4 obs
● 2015-07-14 01:54:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
○NSdns2.triara.com2015-07-14 → 2017-03-28 · 4 obs
● 2015-07-14 01:54:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
○NSdns3.triara.com2015-07-14 → 2017-03-28 · 4 obs
● 2015-07-14 01:54:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
○MXmaila.correonegocios.com2015-07-14 → 2017-03-28 · 4 obs
● 2015-07-14 01:54:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
○MXmailb.correonegocios.com2015-07-14 → 2017-03-28 · 4 obs
● 2015-07-14 01:54:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
○A200.57.128.472015-07-14 → 2015-07-14 · 3 obs
● 2015-07-14 01:54:12
○ 2015-12-11 04:31:18
○ 2026-07-27 23:07:12
○ 2015-12-11 04:31:18
○ 2026-07-27 23:07:12
○A69.49.115.402015-12-11 → 2017-03-28 · 5 obs
○ 2015-07-14 01:54:12
● 2015-12-11 04:31:18
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
● 2015-12-11 04:31:18
● 2017-03-28 18:02:52
○ 2026-06-27 02:07:44
○ 2026-07-27 23:07:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| humanish.com.mx | cloud1.triara.com, cloud2.triara.com, cloud3.triara.com | - |
✅ Authoritative Response
Server:200.57.128.148
NS records: cloud1.triara.com, cloud2.triara.com, cloud3.triara.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for humanish.com.mx (unsigned zone)
⏱️ Timing
Total: 569ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
humanish.com.mx carries NS records delegating to cloud1.triara.com, cloud2.triara.com and cloud3.triara.com.
At least some of humanish.com.mx's name servers are shared with other domains, for example vasesa.mx, clubnautico.com.mx, pergam.com.mx and two more.
cloud1.triara.com and cloud3.triara.com both resolve to 200.57.128.148, while cloud2.triara.com resolves to 200.57.185.72. All three hostnames map to exactly one IP address each.
cloud1.triara.com along with cloud3.triara.com each resolve to 200.57.128.148 IP addresses.