`msidlab1.com`

DNSSEC	⚠️ Not signed
A	138.91.225.40^{🇺🇸 Microsoft138.91.0.0/16 MICROSOFT}
NS	`ns1-05.azure-dns.com` ⭐
		A	2603:1061:0:700::5^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
		A	13.107.236.5^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
NS	`ns2-05.azure-dns.net`
		A	2620:1ec:8ec:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
		A	150.171.21.5^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
NS	`ns3-05.azure-dns.org`
		A	2a01:111:4000:700::5^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-05.azure-dns.org`
		A	204.14.183.5^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-05.azure-dns.org`
NS	`ns4-05.azure-dns.info`
		A	2620:1ec:bda:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
		A	208.84.5.5^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
MX	`msidlab1-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c801::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:f90b::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f910::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr03cu00300.inbound.protection.outlook.com`
		A	52.101.40.1^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy4pr03cu00101.inbound.protection.outlook.com`
		A	52.101.50.7^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr21cu00207.inbound.protection.outlook.com`
		A	52.101.194.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr04cu00104.inbound.protection.outlook.com`
		A	52.101.194.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr21cu00107.inbound.protection.outlook.com`
TXT	`MS=ms37592014`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-05.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=1778697681

Same first word

msidlab1.com

DNS History

9 records (6 active, 3 former)

●NSns1-05.azure-dns.com2019-01-20 → 2026-05-13 · 3 obs

○ 2016-12-20 03:01:08
● 2019-01-20 06:29:24
● 2026-05-13 18:57:38

○NSns1.hover.com2016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 03:01:08
○ 2019-01-20 06:29:24
○ 2026-05-13 18:57:38

●NSns2-05.azure-dns.net2019-01-20 → 2026-05-13 · 3 obs

○ 2016-12-20 03:01:08
● 2019-01-20 06:29:24
● 2026-05-13 18:57:38

○NSns2.hover.com2016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 03:01:08
○ 2019-01-20 06:29:24
○ 2026-05-13 18:57:38

●NSns3-05.azure-dns.org2019-01-20 → 2026-05-13 · 3 obs

○ 2016-12-20 03:01:08
● 2019-01-20 06:29:24
● 2026-05-13 18:57:38

●NSns4-05.azure-dns.info2019-01-20 → 2026-05-13 · 3 obs

○ 2016-12-20 03:01:08
● 2019-01-20 06:29:24
● 2026-05-13 18:57:38

●MXmsidlab1-com.mail.protection.outlook.com2016-12-20 → 2026-05-13 · 2 obs

● 2016-12-20 03:01:08
● 2026-05-13 18:57:38

●A138.91.225.402019-01-20 → 2026-05-13 · 3 obs

○ 2016-12-20 03:01:08
● 2019-01-20 06:29:24
● 2026-05-13 18:57:38

○A64.98.145.302016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 03:01:08
○ 2019-01-20 06:29:24
○ 2026-05-13 18:57:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, e.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net...	-
msidlab1.com	ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.5

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for msidlab1.com (unsigned zone)

⏱️ Timing

Total: 512ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`138.91.225.40`
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
MX	1	`msidlab1-com.mail.protection.outlook.com`
TXT	2	`MS=ms37592014, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1-05.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

msidlab1.com points to a single IP: 138.91.225.40.

Other host names, for instance feige.us, sacko.com, snakenamed.com, waws-prod-bay-007.westus.cloudapp.azure.com and cencoinsurance.com share IP numbers with msidlab1.com.

Name Servers

msidlab1.com's delegation is handled by four name servers: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

msidlab1.com partially shares name servers with other domains; examples include lesfriday.com, horinsa.es, yuckers.com, arkasline.com.tr and ruche.buzz.