msidlab8.com - dns.ninja

`msidlab8.com`

DNSSEC	⚠️ Not signed
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	`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`
MX	`msidlab8-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01602.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::16^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00306.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr02cu00101.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.9.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00400.inbound.protection.outlook.com`
		A	52.101.41.180^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
		A	52.101.50.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00502.inbound.protection.outlook.com`
TXT	`MS=ms77533568`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-03.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=1785642922

Same first word

msidlab8.com

DNS History

9 records (6 active, 3 former)

●NSns1-02.azure-dns.com2018-01-30 → 2026-08-02 · 3 obs

○ 2017-01-04 16:07:30
● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

●NSns1-03.azure-dns.com2018-01-30 → 2026-08-02 · 3 obs

○ 2017-01-04 16:07:30
● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

○NSns1.hover.com2017-01-04 → 2017-01-04 · 3 obs

● 2017-01-04 16:07:30
○ 2018-01-30 09:16:16
○ 2026-08-02 04:01:28

●NSns2-02.azure-dns.net2018-01-30 → 2026-08-02 · 3 obs

○ 2017-01-04 16:07:30
● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

○NSns2.hover.com2017-01-04 → 2017-01-04 · 3 obs

● 2017-01-04 16:07:30
○ 2018-01-30 09:16:16
○ 2026-08-02 04:01:28

●NSns3-02.azure-dns.org2018-01-30 → 2026-08-02 · 3 obs

○ 2017-01-04 16:07:30
● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

●NSns4-02.azure-dns.info2018-01-30 → 2026-08-02 · 3 obs

○ 2017-01-04 16:07:30
● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

●MXmsidlab8-com.mail.protection.outlook.com2018-01-30 → 2026-08-02 · 2 obs

● 2018-01-30 09:16:16
● 2026-08-02 04:01:28

○A64.98.145.302017-01-04 → 2017-01-04 · 3 obs

● 2017-01-04 16:07:30
○ 2018-01-30 09:16:16
○ 2026-08-02 04:01:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
msidlab8.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:204.14.183.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 msidlab8.com (unsigned zone)

⏱️ Timing

Total: 368ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
MX	1	`msidlab8-com.mail.protection.outlook.com`
TXT	2	`MS=ms77533568, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1-03.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

msidlab8.com has five name servers, which are ns1-02.azure-dns.com, ns1-03.azure-dns.com, ns4-02.azure-dns.info and two others.

There is at least partial name server overlap between msidlab8.com and other domains — batteriexperten.no, xbim.net, mwtubing.com and two more among them.

It is common to find these name servers alongside the name servers ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-03.azure-dns.info and two others.

Hostnames that resolve to two IP addresses:

ns1-02.azure-dns.com directs traffic to 13.107.236.2 and 2603:1061:0:700::2.

ns1-03.azure-dns.com directs traffic to 13.107.236.3 and 2603:1061:0:700::3.

ns4-02.azure-dns.info directs traffic to 208.84.5.2 and 2620:1ec:bda:700::2.

ns2-02.azure-dns.net directs traffic to 150.171.21.2 and 2620:1ec:8ec:700::2.

ns3-02.azure-dns.org directs traffic to 204.14.183.2 and 2a01:111:4000:700::2.

Mail Servers

Mail for msidlab8.com is handled by a single mail server, msidlab8-com.mail.protection.outlook.com.

msidlab8-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.9.17, 52.101.9.24, 52.101.41.180 and 5 others.