metaverse.mx - robtex.com
metaverse.mx
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.93.100.204🇺🇸 IIHOS00145.93.100.0/24 | ||||||
| PTR | voiceless-beds.com | ||||||
| NS | ns41.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2142::15🇺🇸 GODADDY-DNS2603:5:2140::/44 | ||||||
| PTR | ns41.domaincontrol.com | ||||||
| A | 97.74.100.21🇺🇸 GODADDY-DNS97.74.100.0/23 | ||||||
| PTR | ns41.domaincontrol.com | ||||||
| NS | ns42.domaincontrol.com | ||||||
| A | 2603:5:2242::15🇺🇸 GODADDY-DNS2603:5:2240::/44 | ||||||
| PTR | ns42.domaincontrol.com | ||||||
| A | 173.201.68.21🇺🇸 GODADDY-DNS173.201.68.0/23 | ||||||
| PTR | ns42.domaincontrol.com | ||||||
| SOA | ns41.domaincontrol.comdns@jomax.net 2022-03-07 #1 | ||||||
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1774715110 | ||||||
Same first word
Similar names
DNS History
7 records (3 active, 4 former)
○NSns1.sedoparking.com2017-03-31 → 2017-03-31 · 3 obs
● 2017-03-31 16:29:58
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
○NSns2.sedoparking.com2017-03-31 → 2017-03-31 · 3 obs
● 2017-03-31 16:29:58
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
●NSns41.domaincontrol.com2026-03-08 → 2026-03-28 · 3 obs
○ 2020-03-07 04:59:26
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
●NSns42.domaincontrol.com2026-03-08 → 2026-03-28 · 3 obs
○ 2020-03-07 04:59:26
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
○MXlocalhost2017-03-31 → 2017-03-31 · 3 obs
● 2017-03-31 16:29:58
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
●A45.93.100.2042026-03-08 → 2026-03-28 · 3 obs
○ 2020-03-07 04:59:26
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
● 2026-03-08 16:26:40
● 2026-03-28 16:38:16
○A72.52.4.1222017-03-31 → 2017-03-31 · 3 obs
● 2017-03-31 16:29:58
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
○ 2020-03-07 04:59:26
○ 2026-03-28 16:38:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| metaverse.mx | ns41.domaincontrol.com, ns42.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.100.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for metaverse.mx (unsigned zone)
⏱️ Timing
Total: 277ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.93.100.204 |
| NS | 2 | ns41.domaincontrol.com, ns42.domaincontrol.com |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
metaverse.mx points to IP number 45.93.100.204.
Other host names, for instance, techassurgent.com share IP numbers with metaverse.mx.
Name Servers
metaverse.mx is delegated to two name servers: ns41.domaincontrol.com and ns42.domaincontrol.com.
metaverse.mx uses the same name server setup as other domains such as azminis-mhaa.com, nonsume.com, pis.la, wimic.us and grassvalley4sale.com.
Host names with two IP numbers:
ns41.domaincontrol.com points to 2603:5:2142::15 and 97.74.100.21; ns42.domaincontrol.com points to 2603:5:2242::15 and 173.201.68.21.