FULL SCAN — https://demo-app.example
8 things worth fixing (2 high · 3 medium · 2 low · 1 info).
What we found: GET /.env returned 200 with
database and API-key variable names visible to anyone who asks.
How to fix: block dotfile access in your server/framework config, delete the file from the web root, and rotate every secret that was in it — treat them as compromised.
What we found: Set-Cookie: session=…; Path=/ —
no Secure, HttpOnly, or SameSite.
How to fix: set all three flags on session cookies so they travel only over HTTPS, stay unreadable to scripts, and are not sent cross-site.
What we found: responses carry no CSP, so injected markup would run with the page's full privileges.
How to fix: start with a report-only CSP, review the violations, then enforce it.
What we found: http://demo-app.example serves
the app in cleartext and no Strict-Transport-Security header
is sent.
How to fix: 301-redirect all HTTP traffic to HTTPS and add an HSTS header so browsers refuse cleartext in future.
What we found: no X-Frame-Options header and
no CSP frame-ancestors directive.
How to fix: send X-Frame-Options: SAMEORIGIN (or a CSP
frame-ancestors rule) unless you intend others to embed your app.
What we found: Server: nginx/1.18.0 tells
attackers exactly which exploits to try first.
How to fix: suppress version tokens in your server config.
What we found: /.well-known/security.txt
returned 404, so researchers have no official way to report issues.
How to fix: publish a security.txt with a contact address.
What we found: the certificate chain verifies and old protocol versions are refused. No action needed.
Your report is generated from a live scan of your app: a crawl of your whole site (not just the homepage), copy-paste fix snippets for common stacks, a PDF download, and score history so a rescan shows what changed. Findings describe exposure, not confirmed vulnerability.
Run your free mini-scan Get your full report — $29