becomingsecure.com - dns.ninja

becomingsecure.com

DNSSEC⚠️ Not signed
A3.33.165.172πŸ‡ΊπŸ‡Έ Amazon3.33.160.0/20
PTRaf17d99dea92b4a24.awsglobalaccelerator.com
A15.197.228.149πŸ‡ΊπŸ‡Έ Amazon15.197.224.0/20
NSns1.domaineasy.com ⭐
A13.248.133.179πŸ‡ΊπŸ‡Έ Amazon13.248.128.0/20
PTRa848a465156c22024.awsglobalaccelerator.com
NSns2.domaineasy.com
A76.223.18.168πŸ‡ΊπŸ‡Έ Amazon76.223.16.0/20
PTRa848a465156c22024.awsglobalaccelerator.com
TXTManaged Domain, please visit https://domaineasy.com
SOAns1.domaineasy.comhostmaster@ns1.domaineasy.com 2008-08-03 #0

com

Subdomains

Same first word

DNS History

8 records (4 active, 4 former)

202120222023202420252026NSns1.domaineasy.comns2.domaineasy.comns1.bluehost.comns2.bluehost.comMXmail.becomingsecure.comA15.197.228.1493.33.165.172162.241.216.242
β—‹NSns1.bluehost.com2020-01-12 β†’ 2020-01-12 Β· 3 obs
● 2020-01-12 18:48:14
β—‹ 2026-03-10 03:10:30
β—‹ 2026-07-24 10:49:14
●NSns1.domaineasy.com2026-03-10 β†’ 2026-07-24 Β· 3 obs
β—‹ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-07-24 10:49:14
β—‹NSns2.bluehost.com2020-01-12 β†’ 2020-01-12 Β· 3 obs
● 2020-01-12 18:48:14
β—‹ 2026-03-10 03:10:30
β—‹ 2026-07-24 10:49:14
●NSns2.domaineasy.com2026-03-10 β†’ 2026-07-24 Β· 3 obs
β—‹ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-07-24 10:49:14
β—‹MXmail.becomingsecure.com2020-01-12 β†’ 2020-01-12 Β· 3 obs
● 2020-01-12 18:48:14
β—‹ 2026-03-10 03:10:30
β—‹ 2026-07-24 10:49:14
●A15.197.228.1492026-03-10 β†’ 2026-07-24 Β· 3 obs
β—‹ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-07-24 10:49:14
β—‹A162.241.216.2422020-01-12 β†’ 2020-01-12 Β· 3 obs
● 2020-01-12 18:48:14
β—‹ 2026-03-10 03:10:30
β—‹ 2026-07-24 10:49:14
●A3.33.165.1722026-03-10 β†’ 2026-07-24 Β· 3 obs
β—‹ 2020-01-12 18:48:14
● 2026-03-10 03:10:30
● 2026-07-24 10:49:14

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
becomingsecure.comns1.domaineasy.com, ns2.domaineasy.com2 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: 108ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A23.33.165.172, 15.197.228.149
NS2ns2.domaineasy.com, ns1.domaineasy.com
TXT1Managed Domain, please visit https://dom
SOA1ns1.domaineasy.com hostmaster.ns1.domain

πŸ“Œ Glue Records Collected

Total: 2

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

Analysis

Hierarchy

mail.becomingsecure.com is delegated beneath becomingsecure.com.

IP Addresses

becomingsecure.com points to the IP addresses 3.33.165.172 and 15.197.228.149

www.weddingbee.melanietter.members.com, ibe.com, 108.249.202.uch.net and two other host names share IP numbers with becomingsecure.com.

Name Servers

The NS records for becomingsecure.com delegate to ns1.domaineasy.com and ns2.domaineasy.com.

becomingsecure.com uses the same name servers as several other domains β€” among them activity.gonzalezbullard0.members.com, frederiksen32halvorsen.members.com, hartleyrosenkilde90.members.com and two more.

becomingsecure.com and other domains like webitts.com share at least a portion of their name servers.

ns1.domaineasy.com β†’ 13.248.133.179 and ns2.domaineasy.com β†’ 76.223.18.168: one IP number per host name.