How it works
Content Security Policy builder accepts explicit HTTPS origins and generates separate directives. It rejects paths and injected directives instead of silently broadening the policy.
Worked example
An empty origin list allows same-origin scripts, styles, images, fonts and connections while setting default-src to none.
Before you rely on the result
This is a starting policy, not a security audit. It does not support inline code, nonces, hashes, workers or frames. Report-only does not block resources and no reporting endpoint is configured. Validate it against your application before enforcement.
Cite this page
ToolOctopus. “Content Security Policy builder.” Updated . https://tooloctopus.com/content-security-policy-builder.
Add an access date if your instructions require one.
Citation formatting uses citeproc-js by Frank Bennett and Citation Style Language styles. License and source code.