`healingrequest.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`verification-bukl82wwh56gubebnf9dqk.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net 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=1784124532

Same first word

healingrequest.com

DNS History

12 records (5 active, 7 former)

○NSns.buydomains.com2016-12-03 → 2017-10-03 · 5 obs

○ 2016-04-17 06:17:30
● 2016-12-03 20:00:02
● 2017-10-03 00:50:20
○ 2026-06-28 11:28:02
○ 2026-07-15 14:25:34

●NSns1.afternic.com2026-06-28 → 2026-07-15 · 3 obs

○ 2017-10-03 00:50:20
● 2026-06-28 11:28:02
● 2026-07-15 14:25:34

●NSns2.afternic.com2026-06-28 → 2026-07-15 · 3 obs

○ 2017-10-03 00:50:20
● 2026-06-28 11:28:02
● 2026-07-15 14:25:34

○NSns7.rookdns.com2015-10-15 → 2016-04-17 · 4 obs

● 2015-10-15 18:50:22
● 2016-04-17 06:17:30
○ 2016-12-03 20:00:02
○ 2026-07-15 14:25:34

○NSns8.rookdns.com2015-10-15 → 2016-04-17 · 4 obs

● 2015-10-15 18:50:22
● 2016-04-17 06:17:30
○ 2016-12-03 20:00:02
○ 2026-07-15 14:25:34

●NSverification-bukl82wwh56gubebnf9dqk.ns101.verify.hn2026-06-28 → 2026-07-15 · 3 obs

○ 2017-10-03 00:50:20
● 2026-06-28 11:28:02
● 2026-07-15 14:25:34

○MXmail.mxproc.com2015-10-15 → 2016-04-17 · 4 obs

● 2015-10-15 18:50:22
● 2016-04-17 06:17:30
○ 2016-12-03 20:00:02
○ 2026-07-15 14:25:34

●A13.248.169.482026-06-28 → 2026-07-15 · 3 obs

○ 2017-10-03 00:50:20
● 2026-06-28 11:28:02
● 2026-07-15 14:25:34

○A141.8.224.932015-10-15 → 2016-04-17 · 4 obs

● 2015-10-15 18:50:22
● 2016-04-17 06:17:30
○ 2016-12-03 20:00:02
○ 2026-07-15 14:25:34

○A141.8.225.1242016-12-03 → 2016-12-03 · 4 obs

○ 2016-04-17 06:17:30
● 2016-12-03 20:00:02
○ 2017-10-03 00:50:20
○ 2026-07-15 14:25:34

○A207.148.248.1432017-10-03 → 2017-10-03 · 4 obs

○ 2016-12-03 20:00:02
● 2017-10-03 00:50:20
○ 2026-06-28 11:28:02
○ 2026-07-15 14:25:34

●A76.223.54.1462026-06-28 → 2026-07-15 · 3 obs

○ 2017-10-03 00:50:20
● 2026-06-28 11:28:02
● 2026-07-15 14:25:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net...	-
healingrequest.com	ns1.afternic.com, ns2.afternic.com, verification-bukl82wwh56gubebnf9dqk.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-bukl82wwh56gubebnf9dqk.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for healingrequest.com (unsigned zone)

⏱️ Timing

Total: 3897ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

healingrequest.com has two IP addresses: 13.248.169.48 and 76.223.54.146

Two other host names, along with partidodigital.com, mail.growthair.com and podlimited.com, also share IP numbers with healingrequest.com.

Name Servers

Three name servers are authoritative for healingrequest.com: ns1.afternic.com, ns2.afternic.com and verification-bukl82wwh56gubebnf9dqk.ns101.verify.hn.

There is at least partial name server overlap between healingrequest.com and other domains — waterdownclinic.com, cpucooler.com, amoi.me and two more among them.

These name servers frequently co-occur with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45. verification-bukl82wwh56gubebnf9dqk.ns101.verify.hn resolves to 13.248.169.48 and 76.223.54.146. All three hostnames point to two IP numbers each.

healingrequest.com - robtex.com