Check the HTTP response headers of any website. Analyse security headers, server info, caching, CORS, and content policies.
HTTP headers are key-value pairs sent between the client and server with every request and response. They control caching, security policies, content negotiation, authentication, and much more. Checking a server's response headers reveals its security posture, technology stack, and configuration quality.
Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options defend against common web attacks including MITM, XSS, and clickjacking.
Cache-Control, ETag, Last-Modified, and Vary control browser and CDN caching behaviour, directly impacting page load speed.
The Server and X-Powered-By headers often reveal web server software and version (nginx 1.24, Apache 2.4, PHP 8.2). Hiding these reduces attack surface.
Access-Control-Allow-Origin controls which origins can make cross-site requests. Overly permissive CORS (*) can expose APIs to malicious sites.
In Apache, use Header always set in .htaccess or a VirtualHost block. In nginx, use add_header directives. CDNs like Cloudflare allow header rules in the dashboard.
That site grades headers A+ through F. Aim for at least an A by implementing HSTS, CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.