`bingsidewalk.com`

DNSSEC	⚠️ Not signed
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
SOA	`ns1-04.azure-dns.com`azuredns-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.net`nstld@verisign-grs.com serial=1778504006

Same first word

bingsidewalk.com

DNS History

8 records (4 active, 4 former)

●NSns1-04.azure-dns.com2026-02-28 → 2026-05-11 · 3 obs

○ 2016-08-09 07:48:52
● 2026-02-28 15:52:12
● 2026-05-11 13:01:26

○NSns1.msft.net2015-08-17 → 2016-08-09 · 4 obs

● 2015-08-17 07:20:08
● 2016-08-09 07:48:52
○ 2026-02-28 15:52:12
○ 2026-05-11 13:01:26

●NSns2-04.azure-dns.net2026-02-28 → 2026-05-11 · 3 obs

○ 2016-08-09 07:48:52
● 2026-02-28 15:52:12
● 2026-05-11 13:01:26

○NSns2.msft.net2015-08-17 → 2016-08-09 · 4 obs

● 2015-08-17 07:20:08
● 2016-08-09 07:48:52
○ 2026-02-28 15:52:12
○ 2026-05-11 13:01:26

●NSns3-04.azure-dns.org2026-02-28 → 2026-05-11 · 3 obs

○ 2016-08-09 07:48:52
● 2026-02-28 15:52:12
● 2026-05-11 13:01:26

○NSns3.msft.net2015-08-17 → 2016-08-09 · 4 obs

● 2015-08-17 07:20:08
● 2016-08-09 07:48:52
○ 2026-02-28 15:52:12
○ 2026-05-11 13:01:26

●NSns4-04.azure-dns.info2026-02-28 → 2026-05-11 · 3 obs

○ 2016-08-09 07:48:52
● 2026-02-28 15:52:12
● 2026-05-11 13:01:26

○NSns4.msft.net2015-08-17 → 2016-08-09 · 4 obs

● 2015-08-17 07:20:08
● 2016-08-09 07:48:52
○ 2026-02-28 15:52:12
○ 2026-05-11 13:01:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bingsidewalk.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:13.107.236.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 bingsidewalk.com (unsigned zone)

⏱️ Timing

Total: 590ms | 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

bingsidewalk.com delegates 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.

bingsidewalk.com at least partially shares name servers with other domains, for instance charingfield.org, clarityhearing.co.nz, granite.clouddevice.io, raswomenshealth.net and trustedchoice.net.

Host names with two IP numbers: ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4; ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4; ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4; ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4.

bingsidewalk.com - robtex.com