`microsoftready.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=1777027506

Same first word

microsoftready.com

microsoftready.net

DNS History

9 records (4 active, 5 former)

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

○ 2018-09-02 19:32:48
● 2026-02-28 16:49:02
● 2026-04-24 11:02:48

○NSns1.msft.net2017-05-09 → 2018-09-02 · 4 obs

● 2017-05-09 01:23:56
● 2018-09-02 19:32:48
○ 2026-02-28 16:49:02
○ 2026-04-24 11:02:48

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

○ 2018-09-02 19:32:48
● 2026-02-28 16:49:02
● 2026-04-24 11:02:48

○NSns2.msft.net2017-05-09 → 2018-09-02 · 4 obs

● 2017-05-09 01:23:56
● 2018-09-02 19:32:48
○ 2026-02-28 16:49:02
○ 2026-04-24 11:02:48

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

○ 2018-09-02 19:32:48
● 2026-02-28 16:49:02
● 2026-04-24 11:02:48

○NSns3.msft.net2017-05-09 → 2018-09-02 · 4 obs

● 2017-05-09 01:23:56
● 2018-09-02 19:32:48
○ 2026-02-28 16:49:02
○ 2026-04-24 11:02:48

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

○ 2018-09-02 19:32:48
● 2026-02-28 16:49:02
● 2026-04-24 11:02:48

○NSns4.msft.net2017-05-09 → 2018-09-02 · 4 obs

● 2017-05-09 01:23:56
● 2018-09-02 19:32:48
○ 2026-02-28 16:49:02
○ 2026-04-24 11:02:48

○A40.112.191.1592018-09-02 → 2018-09-02 · 3 obs

● 2018-09-02 19:32:48
○ 2026-02-28 16:49:02
○ 2026-04-24 11:02:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net...	-
microsoftready.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:150.171.21.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 microsoftready.com (unsigned zone)

⏱️ Timing

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

microsoftready.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.

microsoftready.com at least partially shares its name servers with other domains, for instance allenbradley.gr, ossonline.net, instantgroup.com.au, gorestoran.net and lvfs.net.

Host names with two IPs: ns1-02.azure-dns.com points to 2603:1061:0:700::2 and 13.107.236.2; ns4-02.azure-dns.info points to 2620:1ec:bda:700::2 and 208.84.5.2; ns2-02.azure-dns.net points to 2620:1ec:8ec:700::2 and 150.171.21.2; ns3-02.azure-dns.org points to 2a01:111:4000:700::2 and 204.14.183.2.

microsoftready.com - robtex.com