3shealthapps.com - dns.ninja

`3shealthapps.com`

DNSSEC	⚠️ Not signed
NS	`ns-1276.awsdns-31.org` ⭐
		A	2600:9000:5304:fc00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1276.awsdns-31.org`
		A	205.251.196.252^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1276.awsdns-31.org`
NS	`ns-1017.awsdns-63.net`
		A	2600:9000:5303:f900::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-1017.awsdns-63.net`
		A	205.251.195.249^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-1017.awsdns-63.net`
NS	`ns-1696.awsdns-20.co.uk`
		A	2600:9000:5306:a000::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1696.awsdns-20.co.uk`
		A	205.251.198.160^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1696.awsdns-20.co.uk`
NS	`ns-466.awsdns-58.com`
		A	2600:9000:5301:d200::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-466.awsdns-58.com`
		A	205.251.193.210^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-466.awsdns-58.com`
SOA	`ns-1276.awsdns-31.org`awsdns-hostmaster@amazon.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=1786572834

Same first word

3shealthapps.com

DNS History

4 records (4 active, 0 former)

●NSns-1017.awsdns-63.net2026-03-04 → 2026-08-12 · 2 obs

● 2026-03-04 23:26:20
● 2026-08-12 22:35:32

●NSns-1276.awsdns-31.org2026-03-04 → 2026-08-12 · 2 obs

● 2026-03-04 23:26:20
● 2026-08-12 22:35:32

●NSns-1696.awsdns-20.co.uk2026-03-04 → 2026-08-12 · 2 obs

● 2026-03-04 23:26:20
● 2026-08-12 22:35:32

●NSns-466.awsdns-58.com2026-03-04 → 2026-08-12 · 2 obs

● 2026-03-04 23:26:20
● 2026-08-12 22:35:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
3shealthapps.com	ns-466.awsdns-58.com, ns-1017.awsdns-63.net, ns-1696.awsdns-20.co.uk, ns-1276.awsdns-31.org	2 records

✅ Authoritative Response

Server:205.251.198.160

NS records: ns-466.awsdns-58.com, ns-1017.awsdns-63.net, ns-1696.awsdns-20.co.uk, ns-1276.awsdns-31.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 3shealthapps.com (unsigned zone)

⏱️ Timing

Total: 241ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1017.awsdns-63.net, ns-1276.awsdns-31.org...`
SOA	1	`ns-1276.awsdns-31.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-466.awsdns-58.com, ns-466.awsdns-58.com)

Analysis

Name Servers

The domain 3shealthapps.com is delegated to these four name servers: ns-466.awsdns-58.com, ns-1017.awsdns-63.net, ns-1276.awsdns-31.org and ns-1696.awsdns-20.co.uk.

At least some of 3shealthapps.com's name servers are shared with other domains, for example bizequity.com, lmsonparle.net, lawss.kr and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-466.awsdns-58.com directs to 205.251.193.210 and 2600:9000:5301:d200::1; ns-1017.awsdns-63.net directs to 205.251.195.249 and 2600:9000:5303:f900::1; ns-1276.awsdns-31.org directs to 205.251.196.252 and 2600:9000:5304:fc00::1; ns-1696.awsdns-20.co.uk directs to 205.251.198.160 and 2600:9000:5306:a000::1.