`mclanedatasystems.com`

DNSSEC	⚠️ Not signed
NS	`ns1-36.azure-dns.com` ⭐
		A	2603:1061:0:10::24^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
		A	150.171.10.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
NS	`ns2-36.azure-dns.net`
		A	2620:1ec:8ec:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
		A	150.171.16.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
NS	`ns3-36.azure-dns.org`
		A	2a01:111:4000:10::24^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-36.azure-dns.org`
		A	13.107.222.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-36.azure-dns.org`
NS	`ns4-36.azure-dns.info`
		A	2620:1ec:bda:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
		A	13.107.206.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
SOA	`ns1-36.azure-dns.com`azuredns-hostmaster@microsoft.com 2005-10-13 #6

`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=1774584207

Same first word

mclanedatasystems.com

DNS History

6 records (4 active, 2 former)

○NSmcns1.mclaneco.com2015-12-28 → 2017-07-10 · 4 obs

● 2015-12-28 00:51:34
● 2017-07-10 09:29:56
○ 2026-03-18 19:54:26
○ 2026-03-27 04:23:20

○NSmcns2.mclaneco.com2015-12-28 → 2017-07-10 · 4 obs

● 2015-12-28 00:51:34
● 2017-07-10 09:29:56
○ 2026-03-18 19:54:26
○ 2026-03-27 04:23:20

●NSns1-36.azure-dns.com2026-03-18 → 2026-03-27 · 3 obs

○ 2017-07-10 09:29:56
● 2026-03-18 19:54:26
● 2026-03-27 04:23:20

●NSns2-36.azure-dns.net2026-03-18 → 2026-03-27 · 3 obs

○ 2017-07-10 09:29:56
● 2026-03-18 19:54:26
● 2026-03-27 04:23:20

●NSns3-36.azure-dns.org2026-03-18 → 2026-03-27 · 3 obs

○ 2017-07-10 09:29:56
● 2026-03-18 19:54:26
● 2026-03-27 04:23:20

●NSns4-36.azure-dns.info2026-03-18 → 2026-03-27 · 3 obs

○ 2017-07-10 09:29:56
● 2026-03-18 19:54:26
● 2026-03-27 04:23:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
mclanedatasystems.com	ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns4-36.azure-dns.info, ns3-36.azure-dns.org	2 records

✅ Authoritative Response

Server:150.171.10.36

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mclanedatasystems.com (unsigned zone)

⏱️ Timing

Total: 247ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

mclanedatasystems.com is delegated to four name servers: ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org.

mclanedatasystems.com at least partially shares its name servers with other domains, for instance nexboard.com.br, abazure.net, grupoeitb.eus, eloview.fr and breakfastclubcanada.org.

Host names with two IPs: ns1-36.azure-dns.com points to 2603:1061:0:10::24 and 150.171.10.36; ns4-36.azure-dns.info points to 2620:1ec:bda:10::24 and 13.107.206.36; ns2-36.azure-dns.net points to 2620:1ec:8ec:10::24 and 150.171.16.36; ns3-36.azure-dns.org points to 2a01:111:4000:10::24 and 13.107.222.36.

mclanedatasystems.com - robtex.com