`bingcollections.com`

DNSSEC	⚠️ Not signed
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
SOA	`ns1-02.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=1774578782

Same first word

bingcollections.com

DNS History

8 records (4 active, 4 former)

●NSns1-02.azure-dns.com2020-01-19 → 2026-03-27 · 3 obs

○ 2017-02-10 03:49:08
● 2020-01-19 02:20:50
● 2026-03-27 02:50:28

○NSns1.msft.net2015-06-01 → 2017-02-10 · 4 obs

● 2015-06-01 02:19:46
● 2017-02-10 03:49:08
○ 2020-01-19 02:20:50
○ 2026-03-27 02:50:28

●NSns2-02.azure-dns.net2020-01-19 → 2026-03-27 · 3 obs

○ 2017-02-10 03:49:08
● 2020-01-19 02:20:50
● 2026-03-27 02:50:28

○NSns2.msft.net2015-06-01 → 2017-02-10 · 4 obs

● 2015-06-01 02:19:46
● 2017-02-10 03:49:08
○ 2020-01-19 02:20:50
○ 2026-03-27 02:50:28

●NSns3-02.azure-dns.org2020-01-19 → 2026-03-27 · 3 obs

○ 2017-02-10 03:49:08
● 2020-01-19 02:20:50
● 2026-03-27 02:50:28

○NSns3.msft.net2015-06-01 → 2017-02-10 · 4 obs

● 2015-06-01 02:19:46
● 2017-02-10 03:49:08
○ 2020-01-19 02:20:50
○ 2026-03-27 02:50:28

●NSns4-02.azure-dns.info2020-01-19 → 2026-03-27 · 3 obs

○ 2017-02-10 03:49:08
● 2020-01-19 02:20:50
● 2026-03-27 02:50:28

○NSns4.msft.net2015-06-01 → 2017-02-10 · 4 obs

● 2015-06-01 02:19:46
● 2017-02-10 03:49:08
○ 2020-01-19 02:20:50
○ 2026-03-27 02:50:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net...	-
bingcollections.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.2

NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bingcollections.com (unsigned zone)

⏱️ Timing

Total: 203ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
SOA	1	`ns1-02.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

Name Servers

bingcollections.com is delegated to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

bingcollections.com shares name servers with other domains at least partially, for instance vectone.com, 0.110.127.61.in-addr.arpa, mobiliseit.com, redwoodcity.gov and jumpahead.sg.

Host names with two IP numbers:

ns1-02.azure-dns.com resolves to 2603:1061:0:700::2 and 13.107.236.2.

ns4-02.azure-dns.info resolves to 2620:1ec:bda:700::2 and 208.84.5.2.

ns2-02.azure-dns.net resolves to 2620:1ec:8ec:700::2 and 150.171.21.2.

ns3-02.azure-dns.org resolves to 2a01:111:4000:700::2 and 204.14.183.2.

bingcollections.com - robtex.com