`microsoft-verification.com`

DNSSEC	⚠️ Not signed
A	20.70.246.20^{🇦🇺 Microsoft20.64.0.0/10}
A	20.76.201.171^{🇳🇱 Microsoft20.64.0.0/10}
A	20.112.250.133^{🇺🇸 Microsoft20.64.0.0/10}
A	20.231.239.246^{🇺🇸 Microsoft20.192.0.0/10}
A	20.236.44.162^{🇺🇸 Microsoft20.192.0.0/10}
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

microsoft-verification.org

microsoft-verification.net

microsoft-verification.us

microsoft-verification.biz

microsoft-verification.com

DNS History

19 records (9 active, 10 former)

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

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
● 2026-03-23 14:50:22

○NSns1.msft.net2015-07-02 → 2017-02-15 · 4 obs

● 2015-07-02 06:59:40
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

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

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
● 2026-03-23 14:50:22

○NSns2.msft.net2015-07-02 → 2017-02-15 · 4 obs

● 2015-07-02 06:59:40
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

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

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
● 2026-03-23 14:50:22

○NSns3.msft.net2015-07-02 → 2017-02-15 · 4 obs

● 2015-07-02 06:59:40
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

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

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
● 2026-03-23 14:50:22

○NSns4.msft.net2015-07-02 → 2017-02-15 · 4 obs

● 2015-07-02 06:59:40
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

○A104.215.95.1872019-04-08 → 2019-04-08 · 4 obs

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
○ 2026-02-28 17:09:22
○ 2026-03-23 14:50:22

●A20.112.250.1332026-02-28 → 2026-03-23 · 3 obs

○ 2019-04-08 20:24:20
● 2026-02-28 17:09:22
● 2026-03-23 14:50:22

●A20.231.239.2462026-02-28 → 2026-03-23 · 3 obs

○ 2019-04-08 20:24:20
● 2026-02-28 17:09:22
● 2026-03-23 14:50:22

●A20.236.44.1622026-02-28 → 2026-03-23 · 3 obs

○ 2019-04-08 20:24:20
● 2026-02-28 17:09:22
● 2026-03-23 14:50:22

●A20.70.246.202026-02-28 → 2026-03-23 · 3 obs

○ 2019-04-08 20:24:20
● 2026-02-28 17:09:22
● 2026-03-23 14:50:22

●A20.76.201.1712026-02-28 → 2026-03-23 · 3 obs

○ 2019-04-08 20:24:20
● 2026-02-28 17:09:22
● 2026-03-23 14:50:22

○A40.84.199.2332017-02-15 → 2017-02-15 · 4 obs

○ 2016-06-25 23:05:02
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

○A52.164.206.562019-04-08 → 2019-04-08 · 4 obs

○ 2017-02-15 10:48:16
● 2019-04-08 20:24:20
○ 2026-02-28 17:09:22
○ 2026-03-23 14:50:22

○A52.178.167.1092017-02-15 → 2017-02-15 · 4 obs

○ 2016-06-25 23:05:02
● 2017-02-15 10:48:16
○ 2019-04-08 20:24:20
○ 2026-03-23 14:50:22

○A64.4.6.1002015-07-02 → 2016-06-25 · 4 obs

● 2015-07-02 06:59:40
● 2016-06-25 23:05:02
○ 2017-02-15 10:48:16
○ 2026-03-23 14:50:22

○A65.55.39.102015-07-02 → 2016-06-25 · 4 obs

● 2015-07-02 06:59:40
● 2016-06-25 23:05:02
○ 2017-02-15 10:48:16
○ 2026-03-23 14:50:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net...	-
microsoft-verification.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 microsoft-verification.com (unsigned zone)

⏱️ Timing

Total: 658ms | Queries: -

📄 Records

Type	Count	Sample Data
A	5	`20.76.201.171, 20.112.250.133...`
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

microsoft-verification.com points to five IPs: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.

other host names include freehalogames.com, technetbrasil.com.br, navision.cz, visioitcentral.net and coding4fun.de; they share IP numbers with microsoft-verification.com.

Name Servers

microsoft-verification.com delegates 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.

microsoft-verification.com at least partially shares name servers with other domains, for instance uhparma.net, skype.cz, ventrac.co.nz, novabase.net and g-connect.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.

microsoft-verification.com - robtex.com