`keyreply.blob.core.windows.net`

	CNAME	`blob.sin22prdstr08a.store.core.windows.net`
	DNSSEC	⚠️ Not signed
	A	20.150.127.11^{🇸🇬 Microsoft20.150.0.0/15 MICROSOFT}

`blob.core.windows.net`

	DNSSEC	⚠️ Not signed
	NS	`ns1-64.azure-dns.com` ⭐
	NS	`ns2-64.azure-dns.net`
	NS	`ns3-64.azure-dns.org`
	NS	`ns4-64.azure-dns.info`
	TXT	`https://github.com/publicsuffix/list/pull/1891`
	SOA	`ns1-64.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

WOT: SAFE (62/100)
WOT: SAFE (71/100)

Same first word

keyreply.blob.core.windows.net

keyreply.com

DNS History

2 records (1 active, 1 former)

○CNAMEblob.sg3prdstr02a.store.core.windows.net2020-01-31 → 2020-01-31 · 3 obs

● 2020-01-31 11:18:44
○ 2026-03-29 08:35:12
○ 2026-07-12 18:36:34

●CNAMEblob.sin22prdstr08a.store.core.windows.net2026-03-29 → 2026-07-12 · 3 obs

○ 2020-01-31 11:18:44
● 2026-03-29 08:35:12
● 2026-07-12 18:36:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	h.gtld-servers.net, j.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net...	-
windows.net	ns1-39.azure-dns.com, ns2-39.azure-dns.net, ns3-39.azure-dns.org, ns4-39.azure-dns.info	1 record
blob.core.windows.net	ns1-64.azure-dns.com, ns2-64.azure-dns.net, ns3-64.azure-dns.org, ns4-64.azure-dns.info	-

✅ Authoritative Response

Server:13.107.222.64

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for windows.net (unsigned zone)

⏱️ Timing

Total: 1118ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`blob.sin22prdstr08a.store.core.windows.n`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns2-39.azure-dns.net)

Analysis

IP Addresses

keyreply.blob.core.windows.net resolves to one IP address: 20.150.127.11.

Other host names share IP numbers with keyreply.blob.core.windows.net; blob.sin22prdstr08a.store.core.windows.net is one such example.

keyreply.blob.core.windows.net - robtex.com