arquing.com.mx - robtex.com
arquing.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=1786146516 | ||||||
Previously MX for
arquing.com.mx |
Same first word
Similar names
DNS History
10 records (0 active, 10 former)
○NSanuj.ns.cloudflare.com2016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○NSns1.poderw.com2015-08-03 → 2016-03-15 · 4 obs
● 2015-08-03 23:44:56
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
○NSns2.poderw.com2015-08-03 → 2016-03-15 · 4 obs
● 2015-08-03 23:44:56
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
○NSsue.ns.cloudflare.com2016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○MXarquing.com.mx2015-08-03 → 2016-03-15 · 4 obs
● 2015-08-03 23:44:56
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
○A104.31.94.1702016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○A104.31.95.1702016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○A2400:cb00:2048:1::681f:5eaa2016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○A2400:cb00:2048:1::681f:5faa2016-09-15 → 2017-04-19 · 5 obs
○ 2016-03-15 15:18:02
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
● 2016-09-15 17:11:58
● 2017-04-19 09:11:18
○ 2026-05-22 19:00:52
○ 2026-08-07 23:50:06
○A64.64.9.2392015-08-03 → 2016-03-15 · 4 obs
● 2015-08-03 23:44:56
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
● 2016-03-15 15:18:02
○ 2016-09-15 17:11:58
○ 2026-08-07 23:50:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
✅ Authoritative Response
Server:189.201.244.1
NS records: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 284ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|