`becomingsecure.com`

DNSSEC	⚠️ Not signed
A	3.33.165.172^{🇺🇸 Amazon3.33.160.0/20}
		PTR	`af17d99dea92b4a24.awsglobalaccelerator.com`
A	15.197.228.149^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns1.domaineasy.com` ⭐
		A	13.248.133.179^{🇺🇸 Amazon13.248.128.0/20}
			PTR	`a848a465156c22024.awsglobalaccelerator.com`
NS	`ns2.domaineasy.com`
		A	76.223.18.168^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a848a465156c22024.awsglobalaccelerator.com`
TXT	`Managed Domain, please visit https://domaineasy.com`
SOA	`ns1.domaineasy.com`hostmaster@ns1.domaineasy.com 2008-08-03 #0

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

Same first word

becomingsecure.com

becomingsecure.org

DNS History

8 records (4 active, 4 former)

○NSns1.bluehost.com2020-01-12 → 2020-01-12 · 3 obs

● 2020-01-12 18:48:14
○ 2026-03-10 03:10:30
○ 2026-03-27 14:16:30

●NSns1.domaineasy.com2026-03-10 → 2026-03-27 · 3 obs

○ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-03-27 14:16:30

○NSns2.bluehost.com2020-01-12 → 2020-01-12 · 3 obs

● 2020-01-12 18:48:14
○ 2026-03-10 03:10:30
○ 2026-03-27 14:16:30

●NSns2.domaineasy.com2026-03-10 → 2026-03-27 · 3 obs

○ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-03-27 14:16:30

○MXmail.becomingsecure.com2020-01-12 → 2020-01-12 · 3 obs

● 2020-01-12 18:48:14
○ 2026-03-10 03:10:30
○ 2026-03-27 14:16:30

●A15.197.228.1492026-03-10 → 2026-03-27 · 3 obs

○ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-03-27 14:16:30

○A162.241.216.2422020-01-12 → 2020-01-12 · 3 obs

● 2020-01-12 18:48:14
○ 2026-03-10 03:10:30
○ 2026-03-27 14:16:30

●A3.33.165.1722026-03-10 → 2026-03-27 · 3 obs

○ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-03-27 14:16:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net...	-
becomingsecure.com	ns1.domaineasy.com, ns2.domaineasy.com	2 records

✅ Authoritative Response

Server:13.248.133.179

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for becomingsecure.com (unsigned zone)

⏱️ Timing

Total: 1104ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.165.172, 15.197.228.149`
NS	2	`ns1.domaineasy.com, ns2.domaineasy.com`
TXT	1	`Managed Domain, please visit https://dom`
SOA	1	`ns1.domaineasy.com hostmaster.ns1.domain`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

The entity becomingsecure.com points to two IP numbers: 3.33.165.172 and 15.197.228.149.

For instance, other host names www.weddingbee.melanietter.members.com, hostmaster.kingsize.org, ibe.com, telemas.com and 108.249.202.uch.net share IP numbers with becomingsecure.com.

Name Servers

becomingsecure.com is delegated to two name servers: ns1.domaineasy.com and ns2.domaineasy.com.

becomingsecure.com uses the same name server setup as other domains such as scamardo.com, frederiksen32halvorsen.members.com, hartleyrosenkilde90.members.com, suiteonline.com and viazon.com.

becomingsecure.com shares name servers with other domains at least partially, for example webitts.com.

Host names with one IP number:

ns1.domaineasy.com points to: 13.248.133.179.

ns2.domaineasy.com points to: 76.223.18.168.

becomingsecure.com - robtex.com