`nuancediagnosticsolutions.com`

DNSSEC	⚠️ Not signed
NS	`ns1-37.azure-dns.com` ⭐
		A	2603:1061:0:10::25^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-37.azure-dns.com`
		A	150.171.10.37^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-37.azure-dns.com`
NS	`ns2-37.azure-dns.net`
		A	2620:1ec:8ec:10::25^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-37.azure-dns.net`
		A	150.171.16.37^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-37.azure-dns.net`
NS	`ns3-37.azure-dns.org`
		A	2a01:111:4000:10::25^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-37.azure-dns.org`
		A	13.107.222.37^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-37.azure-dns.org`
NS	`ns4-37.azure-dns.info`
		A	2620:1ec:bda:10::25^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-37.azure-dns.info`
		A	13.107.206.37^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-37.azure-dns.info`
SOA	`ns1-37.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=1784530637

Same first word

nuancediagnosticsolutions.com

DNS History

4 records (4 active, 0 former)

●NSns1-37.azure-dns.com2026-02-28 → 2026-07-20 · 2 obs

● 2026-02-28 15:34:22
● 2026-07-20 07:21:16

●NSns2-37.azure-dns.net2026-02-28 → 2026-07-20 · 2 obs

● 2026-02-28 15:34:22
● 2026-07-20 07:21:16

●NSns3-37.azure-dns.org2026-02-28 → 2026-07-20 · 2 obs

● 2026-02-28 15:34:22
● 2026-07-20 07:21:16

●NSns4-37.azure-dns.info2026-02-28 → 2026-07-20 · 2 obs

● 2026-02-28 15:34:22
● 2026-07-20 07:21:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
nuancediagnosticsolutions.com	ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns4-37.azure-dns.info, ns3-37.azure-dns.org	2 records

✅ Authoritative Response

Server:13.107.206.37

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for nuancediagnosticsolutions.com (unsigned zone)

⏱️ Timing

Total: 286ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

The authoritative name servers for nuancediagnosticsolutions.com are ns1-37.azure-dns.com, ns4-37.azure-dns.info, ns2-37.azure-dns.net and ns3-37.azure-dns.org.

There is at least partial name server overlap between nuancediagnosticsolutions.com and other domains — 9d.environment.api.powerplatformusercontent.com, ac3d5d241ec69a5e5fa95eb7603c4a19.azr.footprintdns.com, builtrec.com and two more among them.

All four hostnames — ns1-37.azure-dns.com, ns4-37.azure-dns.info, ns2-37.azure-dns.net and ns3-37.azure-dns.org — resolve to two IP numbers apiece: ns1-37.azure-dns.com to 150.171.10.37 and 2603:1061:0:10::25; ns4-37.azure-dns.info to 13.107.206.37 and 2620:1ec:bda:10::25; ns2-37.azure-dns.net to 150.171.16.37 and 2620:1ec:8ec:10::25; ns3-37.azure-dns.org to 13.107.222.37 and 2a01:111:4000:10::25.

nuancediagnosticsolutions.com - robtex.com