microsoftdataverse.blog - robtex.com
microsoftdataverse.blog
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-01.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::1🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-01.azure-dns.com | ||||||
| A | 13.107.236.1🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-01.azure-dns.com | ||||||
| NS | ns2-01.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::1🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-01.azure-dns.net | ||||||
| A | 150.171.21.1🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-01.azure-dns.net | ||||||
| NS | ns3-01.azure-dns.org | ||||||
| A | 2a01:111:4000:700::1🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-01.azure-dns.org | ||||||
| A | 204.14.183.1🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-01.azure-dns.org | ||||||
| NS | ns4-01.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::1🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-01.azure-dns.info | ||||||
| A | 208.84.5.1🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-01.azure-dns.info | ||||||
| SOA | ns1-01.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
blog
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | prd-fzp-07.corp.cira.ca ⭐ | ||||||
| NS | a.ns.nic.blog | ||||||
| NS | b.ns.nic.blog | ||||||
| NS | c.ns.nic.blog | ||||||
| NS | d.ns.nic.blog | ||||||
| SOA | prd-fzp-07.corp.cira.caadmin-dns@cira.ca serial=2603221345 | ||||||
Same first word
DNS History
4 records (4 active, 0 former)
●NSns1-01.azure-dns.com2026-02-28 → 2026-03-22 · 2 obs
● 2026-03-22 18:53:42
●NSns2-01.azure-dns.net2026-02-28 → 2026-03-22 · 2 obs
● 2026-03-22 18:53:42
●NSns3-01.azure-dns.org2026-02-28 → 2026-03-22 · 2 obs
● 2026-03-22 18:53:42
●NSns4-01.azure-dns.info2026-02-28 → 2026-03-22 · 2 obs
● 2026-03-22 18:53:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| blog | a.ns.nic.blog, b.ns.nic.blog, c.ns.nic.blog, d.ns.nic.blog | 8 records |
| microsoftdataverse.blog | ns2-01.azure-dns.net, ns4-01.azure-dns.info, ns1-01.azure-dns.com, ns3-01.azure-dns.org | - |
✅ Authoritative Response
Server: 150.171.21.1
NS records: ns2-01.azure-dns.net, ns4-01.azure-dns.info, ns1-01.azure-dns.com, ns3-01.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for microsoftdataverse.blog (unsigned zone)
⏱️ Timing
Total: 637ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-01.azure-dns.com, ns2-01.azure-dns.net... |
| SOA | 1 | ns1-01.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a.ns.nic.blog, a.ns.nic.blog, b.ns.nic.blog...)
Analysis
Name Servers
microsoftdataverse.blog is delegated to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.
microsoftdataverse.blog at least partially shares name servers with other domains, for instance invekra.com, abionics.fr, sgproof.com, wwwjeld-wen.com and netarum.com.
Host names with two IP numbers:
ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1; ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1; ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1; ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1.