Build a Content Security Policy header by selecting directives and allowed sources. Everything runs locally in your browser — nothing is uploaded.
Generate a security.txt file for your website following RFC 9116 standard. Specify contact email, security policy URL, encryption key, and expiry date for vulnerability disclosure.
Validate .htaccess files against 30+ known Apache directives. Checks RewriteEngine, RewriteRule, ErrorDocument, Redirect, Header, Options, and block directives. Flags unknown directives.
Validate Content Security Policy headers against W3C spec and common pitfalls. Everything runs locally in your browser — nothing is uploaded.
Generates random integers or decimals within a user-defined min-max range with optional repetition filtering. Uses the browser random number generator — fine for games, raffles, and sampling, not for security secrets. Everything runs locally in your browser — nothing is uploaded.
Produces a robots.txt file from a point-and-click form where you set allowed and disallowed paths, crawl delays, and sitemap references. Everything runs locally in your browser — nothing is uploaded.
Content Security Policy Generator lets you build a Content Security Policy header by selecting directives and allowed sources. Everything runs locally in your browser — nothing is uploaded.. It works on any device with a modern web browser.
Yes. After the initial page load, Content Security Policy Generator runs entirely on your device with no internet connection needed. All processing is done locally.
Tools cover JavaScript, CSS, HTML, SQL, Python, JSON, XML, CSV, and more. Check the tool description for specifics.
Yes. Since processing is local, performance depends on your device. Most operations handle large files without issue.
Yes. Formatters use well-known libraries (sql-formatter, Prettier-compatible patterns) and follow widely adopted rules.