`microsoftgignite.com`

DNSSEC	⚠️ Not signed
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
SOA	`ns1-01.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=1774403912

Same first word

microsoftgignite.com

microsoftgignite.mobi

microsoftgignite.biz

microsoftgignite.io

microsoftgignite.net

DNS History

8 records (4 active, 4 former)

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

○ 2018-09-17 14:37:50
● 2026-02-28 11:26:58
● 2026-03-25 02:02:06

○NSns1.msft.net2017-01-04 → 2018-09-17 · 4 obs

● 2017-01-04 22:58:02
● 2018-09-17 14:37:50
○ 2026-02-28 11:26:58
○ 2026-03-25 02:02:06

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

○ 2018-09-17 14:37:50
● 2026-02-28 11:26:58
● 2026-03-25 02:02:06

○NSns2.msft.net2017-01-04 → 2018-09-17 · 4 obs

● 2017-01-04 22:58:02
● 2018-09-17 14:37:50
○ 2026-02-28 11:26:58
○ 2026-03-25 02:02:06

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

○ 2018-09-17 14:37:50
● 2026-02-28 11:26:58
● 2026-03-25 02:02:06

○NSns3.msft.net2017-01-04 → 2018-09-17 · 4 obs

● 2017-01-04 22:58:02
● 2018-09-17 14:37:50
○ 2026-02-28 11:26:58
○ 2026-03-25 02:02:06

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

○ 2018-09-17 14:37:50
● 2026-02-28 11:26:58
● 2026-03-25 02:02:06

○NSns4.msft.net2017-01-04 → 2018-09-17 · 4 obs

● 2017-01-04 22:58:02
● 2018-09-17 14:37:50
○ 2026-02-28 11:26:58
○ 2026-03-25 02:02:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...	-
microsoftgignite.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftgignite.com (unsigned zone)

⏱️ Timing

Total: 244ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

microsoftgignite.com delegates to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

microsoftgignite.com at least partially shares name servers with other domains, including ocenter.eu, xboxlivediamond.org, fcbsixconsulting.com, purflux.de and bing4-int.com.

Host names with two IP numbers: ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1; ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1; ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1; ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1.

microsoftgignite.com - robtex.com