jito.network

https://jito.network
dApp frontend · scanned 6 h ago

Findings

  • 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.

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

Scan notes

Homepage returned HTTP 403; front-end checks may be incomplete.

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

Badge

DappVet score 87

[![Vetted by DappVet](https://dappvet.com/badge/qPhR5wlM.svg)](https://dappvet.com/d/jito.network)

Share on X

Changed something?

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