microsoftdataverse.in - dns.ninja
microsoftdataverse.in
| 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 | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1786018555 | ||||||
Same first word
DNS History
4 records (4 active, 0 former)
●NSns1-09.azure-dns.com2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 12:24:00
●NSns2-09.azure-dns.net2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 12:24:00
●NSns3-09.azure-dns.org2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 12:24:00
●NSns4-09.azure-dns.info2026-02-28 → 2026-08-06 · 2 obs
● 2026-08-06 12:24:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns2.registry.in, ns3.registry.in, ns4.registry.in, ns1.registry.in | - |
| microsoftdataverse.in | ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info | - |
✅ Authoritative Response
Server:208.84.5.9
NS records: ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for microsoftdataverse.in (unsigned zone)
⏱️ Timing
Total: 180ms | 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 |
Analysis
Name Servers
Four name servers handle the delegation for microsoftdataverse.in: ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org.
The name servers of microsoftdataverse.in overlap at least partially with those of other domains — among them gustav.healthcare, accessone.mu, ayhanaksu.com and two more.
Each of the four hosts ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org has two IP addresses. ns1-09.azure-dns.com points to 13.107.236.9 and 2603:1061:0:700::9. ns4-09.azure-dns.info points to 208.84.5.9 and 2620:1ec:bda:700::9. ns2-09.azure-dns.net points to 150.171.21.9 and 2620:1ec:8ec:700::9. ns3-09.azure-dns.org points to 204.14.183.9 and 2a01:111:4000:700::9.