Every check / csp-allows-any-source
Does your content policy allow code from anywhere at all?
We read the rules in your Content-Security-Policy that say where scripts and plugins may come from, and look for a bare wildcard, *, which allows any origin.
How it decides
Those are script-src and object-src, or default-src where either is missing, as a browser reads them, and the check speaks up when either allows any origin.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
A policy like that makes every checking tool report the protection as configured while it stops nothing.
In more detail
If an attacker gets a single tag onto one of your pages, the policy will not object. Naming the hosts you load from is the fix, rolled out in report-only mode first.
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 standards
- Its name in a report
csp-allows-any-source