Every check / csp-unsafe-inline
Does your script policy still let in the scripts it should stop?
We read the script-src rule of your Content-Security-Policy and look for 'unsafe-inline' and 'unsafe-eval'.
How it decides
The check speaks up when it finds either, on a site that has a policy at all, and leaves 'unsafe-inline' alone beside a nonce, a hash or 'strict-dynamic', where browsers ignore it. A wildcard source is the wildcard check's.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
Those are the loopholes an injected script uses, so a policy that allows them stops little of what it was written to stop.
In more detail
Having a policy is the harder part, and most sites have not done it. Tightening this one is a developer task, not a rebuild.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The Business plan
- Proof you own the site
- Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
- Who it is about
- An intruder
- Listed under
- Instructions your site gives browsers
- The standard
- Its name in a report
csp-unsafe-inline