Auto-detects your tech stack — CMS, framework, language, server & hosting — then runs targeted checks
curl -I or securityheaders.com before trusting them.
| Category | Technologies | Detection Method |
|---|---|---|
| CMS | WordPress, Drupal, Joomla, Shopify, Wix, Squarespace | HTML body signatures, meta generator tags, CDN URLs, cookie names |
| Framework | Laravel, Django, Rails, Express/Node, Next.js, Nuxt, Angular, Vue, React | Cookie names (XSRF-TOKEN, csrftoken), HTML attributes, script patterns, X-Powered-By header |
| Language | PHP, Python, Ruby, Node.js, ASP.NET, Java | X-Powered-By header, PHPSESSID cookie, X-AspNet-Version header, X-Runtime header |
| Web Server | Nginx, Apache, IIS, LiteSpeed, Caddy | Server response header |
| CDN / WAF | Cloudflare, Fastly, Akamai, Sucuri | CF-Ray, X-Fastly-Request-Id, X-Sucuri-ID, X-Check-Cacheable headers |
| Hosting | Vercel, Netlify, AWS, Azure, Heroku, GitHub Pages, DigitalOcean | X-Vercel-Id, X-Nf-Request-Id, X-Amz-*, X-Azure-Ref, Via: heroku headers |
| Check | What is tested | Severity |
|---|---|---|
| HTTPS Enforced | URL uses https:// — encrypted transport active | Critical |
| HSTS | Strict-Transport-Security header present | Warning |
| X-Frame-Options | Clickjacking protection via DENY/SAMEORIGIN | Warning |
| X-Content-Type-Options | nosniff prevents MIME-type confusion XSS | Warning |
| Content-Security-Policy | Script whitelist present in response headers | Warning |
| Referrer-Policy | Controls URL leakage in Referer header | Info |
| Server Header Leak | Server/X-Powered-By not exposing version | Warning |
| .git/HEAD Exposed | Source code repo accessible via web (all platforms) | Critical |
| .env Exposed | Environment secrets file accessible (all platforms) | Critical |
curl -I.| # | Step | Technical Detail |
|---|---|---|
| 01 | URL Validation | Input parsed with the browser's native URL() API. https:// auto-added if missing. Origin extracted to avoid path leakage. |
| 02 | HTTPS Check | Protocol read directly from the parsed URL — no network request needed for this check. |
| 03 | Page Fetch via Proxy | Homepage fetched via our server-side fetch.php (real Chrome User-Agent, follows redirects, SSRF-guarded) — reliably reads WAF-protected sites. Falls back to api.allorigins.win if the backend is unavailable. Returns headers + body as JSON. |
| 04 | Stack Fingerprinting | Body text, response headers, and cookie names tested against 35+ technology detectors (CMS, framework, language, server, CDN, hosting). Each match increments a confidence score. |
| 05 | WordPress Fallback Probe | If WordPress is not detected from the page body (e.g. site behind a CDN blocking the proxy), /wp-login.php is probed separately. A 200 response containing WP markup confirms the CMS. |
| 06 | Check Selection | Detected platform IDs map to check pools. Checks are merged and deduplicated by path. Universal checks (.env, .git, all 6 security headers) always run regardless of detection result. |
| 07 | Header Audit | 6 security headers checked by exact key in the normalized header dictionary. Presence = pass, absence = warning or info per severity classification. |
| 08 | Path Probing | Sensitive paths fetched via allorigins proxy. status.http_code checked — 200–399 = accessible (flagged). 403/404/410 = blocked (good). 7-second timeout per path. |
| 09 | Score Calculation | Score = 100 − (criticals × 20) − (warnings × 8), clamped to [0, 100]. Rendered as an animated SVG ring. Colour thresholds: ≥75 green, ≥50 amber, <50 red. |
curl -I https://yoursite.com in any terminal. Shows exact server-level headers — most reliable method to confirm or dispute any header check result./xmlrpc.php, /.env etc.) in your browser. Content visible = file is exposed. 404 = blocked correctly.