weex.com

https://weex.com
dApp frontend · scanned 5 h ago

Findings

  • medium CSP allows scripts from any origin
    The Content-Security-Policy allows scripts from any host or scheme, so it does not stop an attacker-hosted script.
  • low CSP allows 'unsafe-inline' scripts
    The Content-Security-Policy allows inline scripts ('unsafe-inline'), which removes most of its protection against XSS.
  • low DNSSEC not enabled
    DNS answers for the domain are not signed, so a resolver-level attacker could redirect users to a fake front end.
  • low No security.txt
    There is no /.well-known/security.txt, so researchers who find a vulnerability have no published way to report it.
  • info No CAA record
    Any certificate authority may issue certificates for the domain.

Evidence, exact locations and fixes are in the deep report. How scoring works.

Scan notes

Homepage HTML truncated at 256 KB.

JavaScript: scanned at most 6 of 66 scripts (budget: 6 files and the per-scan request cap).

Get the full picture

Evidence, locations, fixes and an AI code review. Private link, no email.

For the team behind it: prove ownership and add active checks.

Paid in crypto via NOWPayments. Automated pre-audit, not an audit.

Facts

Hosting
AWS CloudFront
DNS provider
AWS Route 53
DNSSEC
No
HTTPS
Yes
HSTS
Yes (365 days)
CSP
Yes
Wallet SDKs
None detected
Third-party scripts
0
Scripts scanned
6
security.txt
No
robots.txt
Yes

Badge

DappVet score 85

[![Vetted by DappVet](https://dappvet.com/badge/zqsVcCg4.svg)](https://dappvet.com/d/weex.com)

Share on X

Changed something?

Scores refresh every 6 hours. Rescan now to pick up a fix.