`bluewellnessla.com`

DNSSEC	⚠️ Not signed
A	159.140.143.46^{🇺🇸 AS17264159.140.142.0/23}
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
SOA	`ns1-04.azure-dns.com`hostmaster@ns1.bcbsla.com 2015-11-05 #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=1774836252

Same first word

bluewellnessla.com

DNS History

6 records (5 active, 1 former)

●NSns1-04.azure-dns.com2026-03-21 → 2026-03-30 · 3 obs

○ 2017-09-27 14:46:58
● 2026-03-21 16:58:24
● 2026-03-30 02:19:40

○NSns1.bcbsla.com2016-12-16 → 2017-09-27 · 4 obs

● 2016-12-16 13:04:18
● 2017-09-27 14:46:58
○ 2026-03-21 16:58:24
○ 2026-03-30 02:19:40

●NSns2-04.azure-dns.net2026-03-21 → 2026-03-30 · 3 obs

○ 2017-09-27 14:46:58
● 2026-03-21 16:58:24
● 2026-03-30 02:19:40

●NSns3-04.azure-dns.org2026-03-21 → 2026-03-30 · 3 obs

○ 2017-09-27 14:46:58
● 2026-03-21 16:58:24
● 2026-03-30 02:19:40

●NSns4-04.azure-dns.info2026-03-21 → 2026-03-30 · 3 obs

○ 2017-09-27 14:46:58
● 2026-03-21 16:58:24
● 2026-03-30 02:19:40

●A159.140.143.462016-12-16 → 2026-03-30 · 2 obs

● 2016-12-16 13:04:18
● 2026-03-30 02:19:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, a.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...	-
bluewellnessla.com	ns1-04.azure-dns.com, ns2-04.azure-dns.net	2 records

✅ Authoritative Response

Server:13.107.236.4

NS records: ns1-04.azure-dns.com, ns2-04.azure-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bluewellnessla.com (unsigned zone)

⏱️ Timing

Total: 229ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`159.140.143.46`
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
SOA	1	`ns1-04.azure-dns.com hostmaster.ns1.bcbs`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

bluewellnessla.com maps to IP address 159.140.143.46.

Name Servers

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

bluewellnessla.com at least partially shares name servers with other domains such as nineeleven.com.au, emsdemo21.com, lh1ondemand.com, vendelectric.com and group-me.mx.

Host names with two IP numbers:

ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4

ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4

ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4

ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4

bluewellnessla.com - robtex.com