microsoftdataverse.dev - dns.ninja
microsoftdataverse.dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-09.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::9🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-09.azure-dns.com | ||||||
| A | 13.107.236.9🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-09.azure-dns.com | ||||||
| NS | ns2-09.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::9🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-09.azure-dns.net | ||||||
| A | 150.171.21.9🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-09.azure-dns.net | ||||||
| NS | ns3-09.azure-dns.org | ||||||
| A | 2a01:111:4000:700::9🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-09.azure-dns.org | ||||||
| A | 204.14.183.9🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-09.azure-dns.org | ||||||
| NS | ns4-09.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::9🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-09.azure-dns.info | ||||||
| A | 208.84.5.9🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-09.azure-dns.info | ||||||
| SOA | ns1-09.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
DNS History
4 records (4 active, 0 former)
●NSns1-09.azure-dns.com2026-02-28 → 2026-06-09 · 2 obs
● 2026-06-09 04:19:54
●NSns2-09.azure-dns.net2026-02-28 → 2026-06-09 · 2 obs
● 2026-06-09 04:19:54
●NSns3-09.azure-dns.org2026-02-28 → 2026-06-09 · 2 obs
● 2026-06-09 04:19:54
●NSns4-09.azure-dns.info2026-02-28 → 2026-06-09 · 2 obs
● 2026-06-09 04:19:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| microsoftdataverse.dev | ns2-09.azure-dns.net, ns4-09.azure-dns.info, ns1-09.azure-dns.com, ns3-09.azure-dns.org | - |
✅ Authoritative Response
Server:150.171.21.9
NS records: ns2-09.azure-dns.net, ns4-09.azure-dns.info, ns1-09.azure-dns.com, ns3-09.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for microsoftdataverse.dev (unsigned zone)
⏱️ Timing
Total: 475ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-09.azure-dns.com, ns2-09.azure-dns.net... |
| SOA | 1 | ns1-09.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
microsoftdataverse.dev delegates DNS authority to 4 name servers — ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org.
microsoftdataverse.dev has at least partial name server overlap with other domains, such as brava.security, deesflorist.net, digitalis.fr and two others.
ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org all point to exactly two IP numbers each: ns1-09.azure-dns.com → 13.107.236.9 and 2603:1061:0:700::9; ns4-09.azure-dns.info → 208.84.5.9 and 2620:1ec:bda:700::9; ns2-09.azure-dns.net → 150.171.21.9 and 2620:1ec:8ec:700::9; ns3-09.azure-dns.org → 204.14.183.9 and 2a01:111:4000:700::9.