Skip to content
Calcrivo

HTTP Security Score Calculator

Combine transport, headers, cookies and configuration hygiene into one HTTP security score and find the weakest pillar.

Inputs

seconds
%
%

Costs 8 hygiene points

Costs 6 hygiene points

Costs 6 hygiene points

Costs 5 hygiene points

HTTP Security Score

81/ 100

Overall Grade

B — Good

Transport Pillar

28.0/ 30

Hygiene Pillar

19/ 25

Weakest Pillar

Security headers

Highest-Value Fix

Stop returning stack traces and version banners

Step by step

  1. Values used

    HTTP to HTTPS redirect = 301 to HTTPS on every host — 10; HSTS max-age = 31,536,000 seconds; Lowest TLS version accepted = TLS 1.2 and 1.3 — 8; Security header score = 70 %; Cookie flag score = 80 %; Mixed content present on HTTPS pages = No; Stack traces or version banners in responses = Yes; TRACE, PUT or DELETE reachable without authorisation = No; Directory listing or source files reachable = No

  2. HTTP Security Score

    HTTP score = transport (30: redirect + HSTS + TLS version) + headers (25 × your header score) + cookies (20 × your cookie score) + hygiene (25: 8 no mixed content, 6 no verbose errors, 6 no unsafe methods, 5 no directory listing) = 100.

  3. HTTP Security Score

    = 81 / 100

  4. Overall Grade

    = B — Good

  5. Transport Pillar

    = 28.0 / 30

  6. Hygiene Pillar

    = 19 / 25

  7. Weakest Pillar

    = Security headers

  8. Highest-Value Fix

    = Stop returning stack traces and version banners

How it works

The four pillars are weighted by how directly each one prevents an attack: transport and headers stop interception and injection, cookies limit what a session compromise yields, and hygiene covers the misconfigurations that hand an attacker a free reconnaissance pass. Each pillar is normalised so the weakest one is visible rather than averaged away. A single composite score is what gets reported upward, but the pillar breakdown is what tells the engineer which morning's work moves it.

Formula

HTTP Security Score

HTTP score = transport (30: redirect + HSTS + TLS version) + headers (25 × your header score) + cookies (20 × your cookie score) + hygiene (25: 8 no mixed content, 6 no verbose errors, 6 no unsafe methods, 5 no directory listing) = 100.

transport
Whether the connection is encrypted and stays encrypted
hygiene
Configuration mistakes that leak information or accept unsafe requests

Frequently Asked Questions

How is HTTP Security Score calculated?

HTTP score = transport (30: redirect + HSTS + TLS version) + headers (25 × your header score) + cookies (20 × your cookie score) + hygiene (25: 8 no mixed content, 6 no verbose errors, 6 no unsafe methods, 5 no directory listing) = 100. The four pillars are weighted by how directly each one prevents an attack: transport and headers stop interception and injection, cookies limit what a session compromise yields, and hygiene covers the misconfigurations that hand an attacker a free reconnaissance pass. Each pillar is normalised so the weakest one is visible rather than averaged away.

Why does HTTP Security Score matter?

A single composite score is what gets reported upward, but the pillar breakdown is what tells the engineer which morning's work moves it.

What values do I need to enter?

This calculator takes 9 inputs: HTTP to HTTPS redirect, HSTS max-age, Lowest TLS version accepted, Security header score, Cookie flag score, Mixed content present on HTTPS pages, Stack traces or version banners in responses, TRACE, PUT or DELETE reachable without authorisation, Directory listing or source files reachable. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Why does verbose error output matter if nothing is exploitable?

Because it removes the attacker's guesswork. Stack traces name your framework, ORM and file paths; version banners map straight to a CVE list. Neither is a vulnerability on its own, and both shorten the reconnaissance phase from days to minutes.

You might also need