microsoftevents.net - dns.ninja

`microsoftevents.net`

DNSSEC	⚠️ Not signed
A	134.170.185.64^{🇺🇸 Microsoft134.170.0.0/16 MICROSOFT}
A	134.170.188.147^{🇺🇸 Microsoft134.170.0.0/16 MICROSOFT}
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org`
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info`
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
SOA	`ns1-03.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1782604605

Same first word

microsoftevents.org

microsoftevents.it

microsoftevents.com

microsoftevents.net

Similar names

eventsmicrosoft.live

eventsmicrosoft.org

eventsmicrosoft.com

DNS History

18 records (6 active, 12 former)

○NSdns1.cp.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSdns1.dc.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSdns1.sj.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSdns1.tk.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSdns3.jp.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSdns3.uk.msft.net2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

●NSns1-03.azure-dns.com2026-03-01 → 2026-06-28 · 3 obs

○ 2018-10-19 13:09:10
● 2026-03-01 09:56:26
● 2026-06-28 00:00:40

○NSns1.enterpriseevents.com2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSns1.msft.net2015-08-18 → 2018-10-19 · 5 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2018-10-19 13:09:10
○ 2026-03-01 09:56:26
○ 2026-06-28 00:00:40

●NSns2-03.azure-dns.net2026-03-01 → 2026-06-28 · 3 obs

○ 2018-10-19 13:09:10
● 2026-03-01 09:56:26
● 2026-06-28 00:00:40

○NSns2.msft.net2015-08-18 → 2018-10-19 · 5 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2018-10-19 13:09:10
○ 2026-03-01 09:56:26
○ 2026-06-28 00:00:40

●NSns3-03.azure-dns.org2026-03-01 → 2026-06-28 · 3 obs

○ 2018-10-19 13:09:10
● 2026-03-01 09:56:26
● 2026-06-28 00:00:40

○NSns3.enterpriseevents.com2007-09-18 → 2007-09-18 · 3 obs

● 2007-09-18 08:43:00
○ 2015-08-18 18:52:54
○ 2026-06-28 00:00:40

○NSns3.msft.net2015-08-18 → 2018-10-19 · 5 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2018-10-19 13:09:10
○ 2026-03-01 09:56:26
○ 2026-06-28 00:00:40

●NSns4-03.azure-dns.info2026-03-01 → 2026-06-28 · 3 obs

○ 2018-10-19 13:09:10
● 2026-03-01 09:56:26
● 2026-06-28 00:00:40

○NSns4.msft.net2015-08-18 → 2018-10-19 · 5 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2018-10-19 13:09:10
○ 2026-03-01 09:56:26
○ 2026-06-28 00:00:40

●A134.170.185.642015-08-18 → 2026-06-28 · 3 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2026-06-28 00:00:40

●A134.170.188.1472015-08-18 → 2026-06-28 · 3 obs

○ 2007-09-18 08:43:00
● 2015-08-18 18:52:54
● 2026-06-28 00:00:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	i.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...	-
microsoftevents.net	ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.3

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftevents.net (unsigned zone)

⏱️ Timing

Total: 285ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`134.170.185.64, 134.170.188.147`
NS	4	`ns1-03.azure-dns.com, ns2-03.azure-dns.net...`
SOA	1	`ns1-03.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-03.azure-dns.net, ns2-03.azure-dns.net)

Analysis

IP Addresses

microsoftevents.net directs to two IP numbers, 134.170.185.64 and 134.170.188.147

microsoftevent.net and microsoftevents.org, along with other host names, share IP addresses with microsoftevents.net.

Name Servers

Four name servers handle the delegation for microsoftevents.net: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.

microsoftevents.net partially shares its NS delegation with several other domains, including webfleet.ch, frtl.utn.edu.ar, jeld-wenmillworkuniversity.net and two others.

ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org each carry two IP addresses. ns1-03.azure-dns.com has 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info has 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net has 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org has 204.14.183.3 and 2a01:111:4000:700::3.