beaware360.com - dns.ninja
beaware360.com
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.netnstld@verisign-grs.com serial=1781433025 | ||||||
Subdomains
Same first word
beaware360.com |
DNS History
21 records (10 active, 11 former)
●NSns-1054.awsdns-03.org2026-04-05 → 2026-06-14 · 3 obs
● 2026-04-05 10:14:04
● 2026-06-14 10:57:12
●NSns-190.awsdns-23.com2026-04-05 → 2026-06-14 · 3 obs
● 2026-04-05 10:14:04
● 2026-06-14 10:57:12
●NSns-2034.awsdns-62.co.uk2026-04-05 → 2026-06-14 · 3 obs
● 2026-04-05 10:14:04
● 2026-06-14 10:57:12
●NSns-835.awsdns-40.net2026-04-05 → 2026-06-14 · 3 obs
● 2026-04-05 10:14:04
● 2026-06-14 10:57:12
○NSns03.domaincontrol.com2018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○NSns04.domaincontrol.com2018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
●MXalt1.aspmx.l.google.com2026-04-05 → 2026-06-14 · 2 obs
● 2026-06-14 10:57:12
●MXalt2.aspmx.l.google.com2026-04-05 → 2026-06-14 · 2 obs
● 2026-06-14 10:57:12
●MXalt3.aspmx.l.google.com2026-04-05 → 2026-06-14 · 2 obs
● 2026-06-14 10:57:12
●MXalt4.aspmx.l.google.com2026-04-05 → 2026-06-14 · 2 obs
● 2026-06-14 10:57:12
●MXaspmx.l.google.com2026-04-05 → 2026-06-14 · 2 obs
● 2026-06-14 10:57:12
●A160.153.176.1552026-04-05 → 2026-06-14 · 3 obs
● 2026-04-05 10:14:04
● 2026-06-14 10:57:12
○A184.168.221.362018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.372018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.412018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.432018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.512018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.602018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A184.168.221.622018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A50.63.202.352018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
○A50.63.202.472018-10-26 → 2018-10-26 · 3 obs
○ 2026-04-05 10:14:04
○ 2026-06-14 10:57:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| beaware360.com | ns-190.awsdns-23.com, ns-835.awsdns-40.net, ns-1054.awsdns-03.org, ns-2034.awsdns-62.co.uk | 2 records |
✅ Authoritative Response
Server:205.251.195.67
NS records: ns-190.awsdns-23.com, ns-835.awsdns-40.net, ns-1054.awsdns-03.org, ns-2034.awsdns-62.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for beaware360.com (unsigned zone)
⏱️ Timing
Total: 415ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.153.176.155 |
| NS | 4 | ns-1054.awsdns-03.org, ns-190.awsdns-23.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=OIWXRvqsmCsMUUb, v=spf1 include:amazonses.com ~all |
| SOA | 1 | ns-835.awsdns-40.net awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-190.awsdns-23.com, ns-190.awsdns-23.com)
Analysis
Hierarchy
beaware360.com serves as the parent of www.beaware360.com and emailgw.beaware360.com.
IP Addresses
beaware360.com has exactly one IP address — 160.153.176.155.
Among others, 155.176.153.160.host.secureserver.net, www.grupoinmotion.com, www.beaware360.com and grupoinmotion.com resolve to the same IP numbers as beaware360.com.
Name Servers
Four name servers handle the delegation for beaware360.com: ns-190.awsdns-23.com, ns-835.awsdns-40.net, ns-1054.awsdns-03.org and ns-2034.awsdns-62.co.uk.
beaware360.com has at least partial name server overlap with other domains, such as candycrushsoda.co, entertainmentcruises.okta.com, timoneflotte.com and two others.
ns-190.awsdns-23.com, ns-835.awsdns-40.net, ns-1054.awsdns-03.org and ns-2034.awsdns-62.co.uk all point to exactly two IP numbers each: ns-190.awsdns-23.com → 205.251.192.190 and 2600:9000:5300:be00::1; ns-835.awsdns-40.net → 205.251.195.67 and 2600:9000:5303:4300::1; ns-1054.awsdns-03.org → 205.251.196.30 and 2600:9000:5304:1e00::1; ns-2034.awsdns-62.co.uk → 205.251.199.242 and 2600:9000:5307:f200::1.
Mail Servers
beaware360.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by beaware360.com are shared with other domains: brandmasteracademy.com, newsinitiative.withgoogle.com, hilden.es and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.