bingweb.com - dns.ninja
bingweb.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-04.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::4Microsoft2603:1000::/25 MICROSOFT | ||||||
| A | 13.107.236.4Microsoft13.104.0.0/14 MICROSOFT | ||||||
| NS | ns2-04.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::4Microsoft2620:1ec::/36 MICROSOFT | ||||||
| A | 150.171.21.4Microsoft150.171.0.0/16 MICROSOFT | ||||||
| NS | ns3-04.azure-dns.org | ||||||
| A | 2a01:111:4000:700::4Microsoft2a01:111:4000::/36 | ||||||
| A | 204.14.183.4Microsoft204.14.180.0/22 | ||||||
| NS | ns4-04.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::4Microsoft2620:1ec::/36 MICROSOFT | ||||||
| A | 208.84.5.4Microsoft208.84.0.0/21 MICROSOFT | ||||||
| SOA | ns1-04.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1781207118 | ||||||
DNS History
8 records (4 active, 4 former)
●NSns1-04.azure-dns.com2026-03-01 → 2026-06-11 · 3 obs
● 2026-03-01 08:03:46
● 2026-06-11 20:08:06
○NSns1.msft.net2015-07-22 → 2017-03-18 · 4 obs
● 2017-03-18 08:03:58
○ 2026-03-01 08:03:46
○ 2026-06-11 20:08:06
●NSns2-04.azure-dns.net2026-03-01 → 2026-06-11 · 3 obs
● 2026-03-01 08:03:46
● 2026-06-11 20:08:06
○NSns2.msft.net2015-07-22 → 2017-03-18 · 4 obs
● 2017-03-18 08:03:58
○ 2026-03-01 08:03:46
○ 2026-06-11 20:08:06
●NSns3-04.azure-dns.org2026-03-01 → 2026-06-11 · 3 obs
● 2026-03-01 08:03:46
● 2026-06-11 20:08:06
○NSns3.msft.net2015-07-22 → 2017-03-18 · 4 obs
● 2017-03-18 08:03:58
○ 2026-03-01 08:03:46
○ 2026-06-11 20:08:06
●NSns4-04.azure-dns.info2026-03-01 → 2026-06-11 · 3 obs
● 2026-03-01 08:03:46
● 2026-06-11 20:08:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net... | - |
| bingweb.com | ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info | 2 records |
✅ Authoritative Response
Server:208.84.5.4
NS records: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bingweb.com (unsigned zone)
⏱️ Timing
Total: 4644ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-04.azure-dns.com, ns2-04.azure-dns.net... |
| SOA | 1 | ns1-04.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-04.azure-dns.com, ns1-04.azure-dns.com)
Analysis
Name Servers
bingweb.com is delegated to four name servers, ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.
Each of the four hosts ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org has two IP addresses. ns1-04.azure-dns.com points to 13.107.236.4 and 2603:1061:0:700::4. ns4-04.azure-dns.info points to 208.84.5.4 and 2620:1ec:bda:700::4. ns2-04.azure-dns.net points to 150.171.21.4 and 2620:1ec:8ec:700::4. ns3-04.azure-dns.org points to 204.14.183.4 and 2a01:111:4000:700::4.