leadhealing.com - dns.ninja

`leadhealing.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::6815:2fca^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:ac73^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.47.202^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.172.115^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`amber.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a40^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amber.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c040^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`amber.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2040^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`amber.ns.cloudflare.com`
		A	108.162.192.64^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amber.ns.cloudflare.com`
		A	172.64.32.64^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amber.ns.cloudflare.com`
		A	173.245.58.64^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amber.ns.cloudflare.com`
NS	`jay.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b7b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jay.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c17b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jay.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:217b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jay.ns.cloudflare.com`
		A	108.162.193.123^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jay.ns.cloudflare.com`
		A	172.64.33.123^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jay.ns.cloudflare.com`
		A	173.245.59.123^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jay.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.47.202, 172.67.172.115
		IPv6 hints	2606:4700:3033::6815:2fca, 2606:4700:3037::ac43:ac73
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=198, name=cloudflare-ech.com
SOA	`amber.ns.cloudflare.com`dns@cloudflare.com serial=2406635010

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

⚠️ On DNS blocklist: tif

Same first word

leadhealing.com

DNS History

7 records (6 active, 1 former)

●NSamber.ns.cloudflare.com2026-03-18 → 2026-07-03 · 2 obs

● 2026-03-18 20:59:30
● 2026-07-03 07:59:50

●NSjay.ns.cloudflare.com2026-03-18 → 2026-07-03 · 2 obs

● 2026-03-18 20:59:30
● 2026-07-03 07:59:50

●A104.21.47.2022026-03-18 → 2026-07-03 · 2 obs

● 2026-03-18 20:59:30
● 2026-07-03 07:59:50

●A172.67.172.1152026-03-18 → 2026-07-03 · 2 obs

● 2026-03-18 20:59:30
● 2026-07-03 07:59:50

●A2606:4700:3033::6815:2fca2026-03-18 → 2026-07-03 · 2 obs

● 2026-03-18 20:59:30
● 2026-07-03 07:59:50

○A2606:4700:3033::ac43:ac732026-03-18 → 2026-06-13 · 4 obs

● 2026-03-18 20:59:30
● 2026-06-13 20:46:20
○ 2026-06-28 19:22:26
○ 2026-07-03 07:59:50

●A2606:4700:3037::ac43:ac732026-06-28 → 2026-07-03 · 3 obs

○ 2026-06-13 20:46:20
● 2026-06-28 19:22:26
● 2026-07-03 07:59:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, g.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net...	-
leadhealing.com	jay.ns.cloudflare.com, amber.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.123

NS records: jay.ns.cloudflare.com, amber.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadhealing.com (unsigned zone)

⏱️ Timing

Total: 338ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.47.202, 172.67.172.115`
AAAA	2	`2606:4700:3037::ac43:ac73, 2606:4700:3033::6815:2fca`
NS	2	`amber.ns.cloudflare.com, jay.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`amber.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (jay.ns.cloudflare.com, jay.ns.cloudflare.com, jay.ns.cloudflare.com...)

Analysis

IP Addresses

leadhealing.com points to the four IP addresses 104.21.47.202, 172.67.172.115, 2606:4700:3033::6815:2fca and 2606:4700:3037::ac43:ac73.

dashboardv3.xyz, bet-99.net, noome.net and two other host names share IP numbers with leadhealing.com.

Name Servers

leadhealing.com has two authoritative name servers — amber.ns.cloudflare.com and jay.ns.cloudflare.com.

leadhealing.com uses the same name servers as several other domains — among them queenofquiz.com, propelharmony.com, brokerloop.net and two more.

The name servers of leadhealing.com overlap at least partially with those of other domains — among them paragon.enterprises, ashilov.com, tarnowski.net and two more.

These name servers commonly appear in combination with the name servers neil.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

amber.ns.cloudflare.com points to 108.162.192.64, 172.64.32.64, 173.245.58.64 and 3 other IP addresses.

jay.ns.cloudflare.com points to 108.162.193.123, 172.64.33.123, 173.245.59.123 and 3 other IP addresses.