hospitalpc.com.mx - robtex.com
hospitalpc.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
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=1781918754 | ||||||
Same first word
Similar names
pchospital.it |
pchospital.dk |
cphospital.org |
pchospital.gr |
pchospital.us |
cphospital.com |
cphospital.com.au |
pchospital.cz |
pchospital.org |
platochips.com |
capitolhps.com |
pchospital.co.uk |
DNS History
11 records (0 active, 11 former)
○NSamir.ns.cloudflare.com2016-04-27 → 2017-01-10 · 5 obs
○ 2016-01-21 03:22:34
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
○NSlucy.ns.cloudflare.com2016-04-27 → 2017-01-10 · 5 obs
○ 2016-01-21 03:22:34
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
○NSns1.interplanet.com.mx2015-06-19 → 2016-01-21 · 4 obs
● 2015-06-19 22:06:02
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
○NSns2.interplanet.com.mx2015-06-19 → 2016-01-21 · 4 obs
● 2015-06-19 22:06:02
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
○MXfb.suantispam.com2015-06-19 → 2016-01-21 · 4 obs
● 2015-06-19 22:06:02
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
○MXmx.suantispam.com2015-06-19 → 2016-01-21 · 4 obs
● 2015-06-19 22:06:02
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
○A104.27.154.2342016-04-27 → 2017-01-10 · 5 obs
○ 2016-01-21 03:22:34
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
○A104.27.155.2342016-04-27 → 2017-01-10 · 5 obs
○ 2016-01-21 03:22:34
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
○A201.175.20.1922015-06-19 → 2016-01-21 · 4 obs
● 2015-06-19 22:06:02
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
● 2016-01-21 03:22:34
○ 2016-04-27 08:15:26
○ 2026-06-20 02:24:30
○A2400:cb00:2048:1::681b:9aea2017-01-10 → 2017-01-10 · 4 obs
○ 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
○A2400:cb00:2048:1::681b:9bea2017-01-10 → 2017-01-10 · 4 obs
○ 2016-04-27 08:15:26
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
● 2017-01-10 05:59:52
○ 2026-03-26 14:24:00
○ 2026-06-20 02:24:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | o.mx-ns.mx, i.mx-ns.mx, e.mx-ns.mx, c.mx-ns.mx... | - |
✅ Authoritative Response
Server:192.100.224.1
NS records: o.mx-ns.mx, i.mx-ns.mx, e.mx-ns.mx, c.mx-ns.mx, m.mx-ns.mx, x.mx-ns.mx
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 183ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|