microsoftsessions.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`microsoftsessions.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-07.azure-dns.com` ⭐
		A	2603:1061:0:700::7^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-07.azure-dns.com`
		A	13.107.236.7^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-07.azure-dns.com`
NS	`ns2-07.azure-dns.net`
		A	2620:1ec:8ec:700::7^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-07.azure-dns.net`
		A	150.171.21.7^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-07.azure-dns.net`
NS	`ns3-07.azure-dns.org`
		A	2a01:111:4000:700::7^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-07.azure-dns.org`
		A	204.14.183.7^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-07.azure-dns.org`
NS	`ns4-07.azure-dns.info`
		A	2620:1ec:bda:700::7^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-07.azure-dns.info`
		A	208.84.5.7^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-07.azure-dns.info`
TXT	`microsoftsessions-new.azurewebsites.net`
SOA	`ns1-07.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=1786948449

Same first word

microsoftsessions.in

microsoftsessions.com.br

microsoftsessions.com

microsoftsessions.net

DNS History

17 records (9 active, 8 former)

●NSns1-07.azure-dns.com2026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

○NSns1.msft.net2015-12-06 → 2017-08-31 · 4 obs

● 2015-12-06 11:48:56
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

●NSns2-07.azure-dns.net2026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

○NSns2.msft.net2015-12-06 → 2017-08-31 · 4 obs

● 2015-12-06 11:48:56
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

●NSns3-07.azure-dns.org2026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

○NSns3.msft.net2015-12-06 → 2017-08-31 · 4 obs

● 2015-12-06 11:48:56
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

●NSns4-07.azure-dns.info2026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

○NSns4.msft.net2015-12-06 → 2017-08-31 · 4 obs

● 2015-12-06 11:48:56
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

●A20.112.250.1332026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

●A20.231.239.2462026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

●A20.236.44.1622026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

●A20.70.246.202026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

●A20.76.201.1712026-02-28 → 2026-08-17 · 3 obs

○ 2017-08-31 14:12:16
● 2026-02-28 16:45:14
● 2026-08-17 06:49:00

○A40.84.199.2332017-07-17 → 2017-08-31 · 5 obs

○ 2016-07-19 22:40:22
● 2017-07-17 14:18:38
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

○A52.178.167.1092017-07-17 → 2017-08-31 · 5 obs

○ 2016-07-19 22:40:22
● 2017-07-17 14:18:38
● 2017-08-31 14:12:16
○ 2026-02-28 16:45:14
○ 2026-08-17 06:49:00

○A64.4.6.1002015-12-06 → 2016-07-19 · 4 obs

● 2015-12-06 11:48:56
● 2016-07-19 22:40:22
○ 2017-07-17 14:18:38
○ 2026-08-17 06:49:00

○A65.55.39.102015-12-06 → 2016-07-19 · 4 obs

● 2015-12-06 11:48:56
● 2016-07-19 22:40:22
○ 2017-07-17 14:18:38
○ 2026-08-17 06:49:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net...	-
microsoftsessions.com	ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.7

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftsessions.com (unsigned zone)

⏱️ Timing

Total: 361ms | Queries: -

📄 Records

Type	Count	Sample Data
A	5	`20.76.201.171, 20.112.250.133...`
NS	4	`ns1-07.azure-dns.com, ns2-07.azure-dns.net...`
TXT	1	`microsoftsessions-new.azurewebsites.net`
SOA	1	`ns1-07.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

microsoftsessions.com directs to five IP numbers, including 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others

cloudstorconnect.com, msdn.dk, office365.com.tw plus two other host names have IP numbers in common with microsoftsessions.com.

Name Servers

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

At least some of microsoftsessions.com's name servers are shared with other domains, for example xbox-ufc.com, logss.com.au, cargoclique.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-07.azure-dns.com directs to 13.107.236.7 and 2603:1061:0:700::7; ns4-07.azure-dns.info directs to 208.84.5.7 and 2620:1ec:bda:700::7; ns2-07.azure-dns.net directs to 150.171.21.7 and 2620:1ec:8ec:700::7; ns3-07.azure-dns.org directs to 204.14.183.7 and 2a01:111:4000:700::7.