`windowsresponde.com`

DNSSEC	⚠️ Not signed
A	52.164.206.56^{🇮🇪 Microsoft52.160.0.0/11 MICROSOFT}
A	104.215.95.187^{🇺🇸 Microsoft104.208.0.0/13 MICROSOFT}
NS	`ns1-06.azure-dns.com` ⭐
		A	2603:1061:0:700::6^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
		A	13.107.236.6^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
NS	`ns2-06.azure-dns.net`
		A	2620:1ec:8ec:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
		A	150.171.21.6^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
NS	`ns3-06.azure-dns.org`
		A	2a01:111:4000:700::6^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-06.azure-dns.org`
		A	204.14.183.6^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-06.azure-dns.org`
NS	`ns4-06.azure-dns.info`
		A	2620:1ec:bda:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
		A	208.84.5.6^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
SOA	`ns1-06.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=1771291435

Same first word

windowsresponde.com

DNS History

13 records (6 active, 7 former)

●NSns1-06.azure-dns.com2019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○NSns1.msft.net2015-05-24 → 2016-12-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

●NSns2-06.azure-dns.net2019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○NSns2.msft.net2015-05-24 → 2016-12-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

●NSns3-06.azure-dns.org2019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○NSns3.msft.net2015-05-24 → 2016-12-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

●NSns4-06.azure-dns.info2019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○NSns4.msft.net2015-05-24 → 2016-12-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

●A104.215.95.1872019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○A40.84.199.2332016-12-17 → 2016-12-17 · 4 obs

○ 2016-07-17 13:39:10
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

●A52.164.206.562019-03-12 → 2026-03-23 · 3 obs

○ 2016-12-17 19:23:28
● 2019-03-12 10:59:44
● 2026-03-23 16:05:06

○A64.4.6.1002015-05-24 → 2016-12-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-12-17 19:23:28
○ 2019-03-12 10:59:44
○ 2026-03-23 16:05:06

○A65.55.39.102015-05-24 → 2016-07-17 · 4 obs

● 2015-05-24 02:16:04
● 2016-07-17 13:39:10
○ 2016-12-17 19:23:28
○ 2026-03-23 16:05:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net...	-
windowsresponde.com	ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.6

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for windowsresponde.com (unsigned zone)

⏱️ Timing

Total: 445ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.215.95.187, 52.164.206.56`
NS	4	`ns1-06.azure-dns.com, ns2-06.azure-dns.net...`
SOA	1	`ns1-06.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

windowsresponde.com points to two IP numbers: 52.164.206.56 and 104.215.95.187.

Other host names such as microsoftcommunitycontributor.tv, verify-msnaccount.biz, surfacebrowse.com, mslsocial.com and chartfares.com share IP numbers with windowsresponde.com.

Name Servers

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

At least part of the name servers for windowsresponde.com are shared with other domains, for instance foglight.org, capitalconcrete.com.au, eczacipos.com.tr, sccfca.org and windowscontent.com.

Host names with two IP numbers:

ns1-06.azure-dns.com points to: 2603:1061:0:700::6 and 13.107.236.6

ns4-06.azure-dns.info points to: 2620:1ec:bda:700::6 and 208.84.5.6

ns2-06.azure-dns.net points to: 2620:1ec:8ec:700::6 and 150.171.21.6

ns3-06.azure-dns.org points to: 2a01:111:4000:700::6 and 204.14.183.6

windowsresponde.com - robtex.com