⚠️ This post links to an external website. ⚠️
My HTTP Header Analyzer has evolved significantly after six years. With over 5 million uses, it now resides at
headers.dev. I audited it against OWASP's recommendations, fixing common issues like the dangers of usingunsafe-inlineandunsafe-evalin Content Security Policies. The analyzer now recognizes new headers likeSpeculation-RulesandCache-Status, improving its ability to catch misconfigurations. It now explains more than 150 headers in detail. The Open Web is stronger when we all review our HTTP headers to ensure security and performance.
continue reading ondri.es
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.