Grade B — 2 to fix, 3 minor.
passive scan · the deep checks need you signed in · scanned 3h ago
This is a passive website security report for chromewebstore.google.com, graded B (80/100). We checked its SSL certificate, HTTP security headers, DNS records, email spoofing protection and publicly exposed files — the same surface a browser and a search engine already see.
We found 5 issues on this scan — each has a plain-English explanation and a copy-paste fix below.
Not your site?
Your site is served over HTTPS but doesn't send a Strict-Transport-Security header. Without it, the first visit (or a link typed as http://) can be intercepted and downgraded to plain HTTP before the redirect happens — a foothold for man-in-the-middle attacks on public Wi-Fi.
You have a Content-Security-Policy, which is great — but it contains a wildcard source or allows 'unsafe-inline'/'unsafe-eval' in script-src. Those let injected scripts execute, which is most of what a CSP is meant to stop.
These cookies are set without the Secure flag: NID. That means the browser will also send them over plain HTTP, where anyone on the same network can read them — including session cookies, which is enough to hijack a logged-in account.
These cookies don't set SameSite: NID. SameSite limits when the browser attaches a cookie to cross-site requests, which is a key defence against CSRF (a malicious site making authenticated requests as your user).
google.com is not protected by DNSSEC. DNSSEC signs your DNS records so resolvers can detect a forged answer — without it, an attacker who can poison DNS could point your domain at their own server without touching anything you control.
Sign up to fix these — then run the checks a passive scan can't. The stuff that actually gets vibe-coded apps hacked:
free for your first app · no card
Not chromewebstore.google.com? Scan your own site free →