Sample report · live demo

See exactly what a scan finds, before you run one.

A real Jikida report on sample data — the same grade, severity breakdown and plain-English findings you get on your own site, code, repo and AWS account. No account needed to look.

Scan your site free → Read-only. We never store your credentials.
C
Website security scan

acme-shop.com

9 findings · grade C (71/100). Live scan of the public surface — headers, TLS, cookies and exposed paths. No critical holes, but a few things to close before launch.

CRITICAL 0
HIGH 2
MEDIUM 4
LOW 3
PASSED 19

HIGH 2 findings

Security headers are missing

headers.hsts_csp
Pillar Transport Resource https://acme-shop.com

What we found The site sends no Strict-Transport-Security and no Content-Security-Policy. A visitor on a hostile network can be downgraded to HTTP, and an injected script has nothing stopping it from loading.

What to do Add Strict-Transport-Security with a long max-age and a Content-Security-Policy that names the origins you actually load from. Start the CSP in report-only mode to catch anything you miss.

Directory listing is enabled

web.dir_listing
Pillar Config Resource https://acme-shop.com/uploads/

What we found /uploads/ returns a browsable file index. Anything written there — invoices, exports, backups — is discoverable by walking the list.

What to do Disable auto-indexing for that path and serve an explicit 403 or a controlled index page.

MEDIUM 4 findings

TLS certificate expires in 12 days

ssl.expiry
Pillar Transport Resource acme-shop.com · expires Oct 19

What we found The certificate is valid but close to expiry. If renewal fails silently, the site goes hard-down for every visitor with a browser warning.

What to do Confirm auto-renewal is running and alerting on failure. Jikida watches expiry and alerts you well before the deadline once the monitor is on.

Server banner leaks exact versions

headers.version_leak
Pillar Config Resource Server: nginx/1.18.0 · X-Powered-By: PHP/7.4.3

What we found Response headers advertise the exact web-server and language versions, handing an attacker a shortlist of version-specific exploits to try first.

What to do Turn off server tokens and remove X-Powered-By.

Session cookie missing Secure and SameSite

web.cookie_flags
Pillar Config Resource Set-Cookie: session=…

What we found The session cookie has neither Secure nor SameSite, so it can ride along on an insecure request or a cross-site one.

What to do Set Secure, HttpOnly and SameSite=Lax (or Strict) on session cookies.

Mixed content on the checkout page

web.mixed_content
Pillar Transport Resource https://acme-shop.com/checkout

What we found The checkout page loads one script over plain HTTP — an injection point on your most sensitive page.

What to do Load every asset over HTTPS and add upgrade-insecure-requests to the CSP as a backstop.

LOW 3 findings

No Referrer-Policy set

headers.referrer
Pillar Config Resource https://acme-shop.com

What we found Without a Referrer-Policy, full URLs leak to third-party resources in the Referer header.

What to do Add Referrer-Policy: strict-origin-when-cross-origin.

X-Content-Type-Options not set

headers.xcto
Pillar Config Resource https://acme-shop.com

What we found Browsers may MIME-sniff responses, turning a benign upload into executable content.

What to do Add X-Content-Type-Options: nosniff.

Admin path reachable in robots.txt

web.robots
Pillar Config Resource /robots.txt → Disallow: /admin

What we found robots.txt advertises /admin to anyone who reads it — the opposite of hiding it.

What to do Protect /admin with auth and drop it from robots.txt.

Findings are automated and heuristic — verify before acting on anything destructive. Sample data shown; your own report reflects your own site, code, repo and AWS account.

That took about a minute. Yours will too.

Point Jikida at a URL, a repo or an AWS account and get this same report on your own — graded, ranked and written to read. Free to start, free to stay.