`eventuallyleechbeautifully.com`

DNSSEC	⚠️ Not signed
A	172.240.108.68^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.76^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.84^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.127.234^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.242^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.243^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.244^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.253.132^{🇺🇸 SERVERS172.240.253.0/24 .COM WAS1}
NS	`ns1.publicdnsservice.com` ⭐
		A	52.223.51.231^{🇺🇸 Amazon52.223.48.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
NS	`ns2.publicdnsservice.com`
		A	99.83.185.193^{🇺🇸 Amazon99.83.176.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
SOA	`ns1.publicdnsservice.com`hostmaster@eventuallyleechbeautifully.com 2026-02-19 #4

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

⚠️ On DNS blocklist: tif

Subdomains

www.eventuallyleechbeautifully.com

Same first word

eventuallyleechbeautifully.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
eventuallyleechbeautifully.com	ns1.publicdnsservice.com, ns2.publicdnsservice.com	2 records

✅ Authoritative Response

Server:52.223.51.231

NS records: ns1.publicdnsservice.com, ns2.publicdnsservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for eventuallyleechbeautifully.com (unsigned zone)

⏱️ Timing

Total: 137ms | Queries: -

📄 Records

Type	Count	Sample Data
A	8	`172.240.127.234, 172.240.108.76...`
NS	2	`ns2.publicdnsservice.com, ns1.publicdnsservice.com`
SOA	1	`ns1.publicdnsservice.com hostmaster.even`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.publicdnsservice.com, ns2.publicdnsservice.com)

Analysis

Hierarchy

eventuallyleechbeautifully.com is parent of www.eventuallyleechbeautifully.com.

IP Addresses

Eight IP numbers are pointed to by eventuallyleechbeautifully.com: 172.240.108.68, 172.240.108.76, 172.240.108.84, 172.240.127.234, 172.240.127.242, 172.240.127.243, 172.240.127.244 and 172.240.253.132.

Other host names, for instance www.reconstructcoal.com, thumbthesishealthy.com, entreatbeggar.com, bunkerjewelleryvaliant.com and diffuseusermessage.com share IP numbers with eventuallyleechbeautifully.com.

Name Servers

eventuallyleechbeautifully.com's delegation is to two name servers ns1.publicdnsservice.com and ns2.publicdnsservice.com.

eventuallyleechbeautifully.com shares the same name server configuration as other domains, such as effectivecreativeformats.com, fishmaterialistic.com, minimizediscourteous.com, intensiveuglyjune.com and haychalk.com.

eventuallyleechbeautifully.com shares name servers with other domains to at least some extent, for instance realizebutterflyfarfetched.com and ratiogodlessirrigate.com.

These name servers are commonly used alongside ns1.sharehostsns.com and ns2.sharehostsns.com.

Host names with a single IP:

ns1.publicdnsservice.com resolves to 52.223.51.231.

ns2.publicdnsservice.com resolves to 99.83.185.193.

eventuallyleechbeautifully.com - robtex.com

eventuallyleechbeautifully.com

com