near.org

https://near.org
dApp frontend · scanned 7 h ago

Findings

  • medium Content-Security-Policy does not restrict scripts
    The Content-Security-Policy has no script-src or default-src, so it does not limit which scripts can run.
  • medium No HTTP Strict Transport Security
    Browsers are not told to always use HTTPS, so a network attacker can downgrade the first visit and swap the front end.
  • 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.
  • info No Permissions-Policy
    The site does not restrict powerful browser features (camera, microphone, payment, USB) for itself and embedded frames.
  • info Third-party scripts
    The homepage loads scripts from 3 third-party origin(s); each one can read and change the wallet UI.

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

Scan notes

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

Script https://near.org/_next/static/chunks/0psvc2-xx4oyr.js truncated at 200 KB.

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
Cloudflare
DNS provider
Namecheap
DNSSEC
No
HTTPS
Yes
HSTS
No
CSP
Yes
Wallet SDKs
None detected
Third-party scripts
3
Scripts scanned
6
security.txt
No
robots.txt
Yes

Badge

DappVet score 81

[![Vetted by DappVet](https://dappvet.com/badge/BiMhxN2O.svg)](https://dappvet.com/d/near.org)

Share on X

Changed something?

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