microsoftdataverse.mx - dns.ninja
microsoftdataverse.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-02.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::2🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| A | 13.107.236.2🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| NS | ns2-02.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| A | 150.171.21.2🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| NS | ns3-02.azure-dns.org | ||||||
| A | 2a01:111:4000:700::2🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| A | 204.14.183.2🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| NS | ns4-02.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| A | 208.84.5.2🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| SOA | ns1-02.azure-dns.comazuredns-hostmaster@microsoft.com serial=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=1786037256 | ||||||
Same first word
DNS History
4 records (4 active, 0 former)
●NSns1-02.azure-dns.com2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 17:29:10
●NSns2-02.azure-dns.net2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 17:29:10
●NSns3-02.azure-dns.org2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 17:29:10
●NSns4-02.azure-dns.info2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 17:29:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | e.mx-ns.mx, m.mx-ns.mx, c.mx-ns.mx, o.mx-ns.mx... | - |
| microsoftdataverse.mx | ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info | - |
✅ Authoritative Response
Server:150.171.21.2
NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for microsoftdataverse.mx (unsigned zone)
⏱️ Timing
Total: 344ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-02.azure-dns.com, ns2-02.azure-dns.net... |
| SOA | 1 | ns1-02.azure-dns.com azuredns-hostmaster |
Analysis
Name Servers
microsoftdataverse.mx has four authoritative name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.
The name servers of microsoftdataverse.mx overlap at least partially with those of other domains — among them crystal-sla.com.kh, uat.ssgp-public.fleet.ubi.com, live.eu and two more.
Each of the four hosts ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org has two IP addresses. ns1-02.azure-dns.com points to 13.107.236.2 and 2603:1061:0:700::2. ns4-02.azure-dns.info points to 208.84.5.2 and 2620:1ec:bda:700::2. ns2-02.azure-dns.net points to 150.171.21.2 and 2620:1ec:8ec:700::2. ns3-02.azure-dns.org points to 204.14.183.2 and 2a01:111:4000:700::2.