Try “SSH”, “passkeys”, “WordPress” or “Content-Security-Policy”.
Section · 5 guides
Where your website or application runs decides who patches what, which defaults protect you and how much can go wrong. We compare web servers, hosting models and server distributions, and show the configuration that matters.
/servers/Four web servers, one question: which one leaves the fewest gaps once it is running? We compare defaults, automatic HTTPS, configuration risk, attack surface and how fast fixes reach you.
Medium impact6 min
Every hosting model splits security work between you and the provider. We compare shared hosting, unmanaged and managed servers, platforms as a service and static hosting by who patches, isolates and restores.
High impact5 min
Support periods, update processes and default protection differ more than package names. We compare Debian, Ubuntu LTS, Rocky Linux, AlmaLinux and Alpine as systems you leave running for years.
Medium impact5 min
Most attacks on SSH are automated guessing. Keys, a small drop-in file and an allow list make that guessing pointless. Here are the settings and how to apply them without locking yourself out.
High impact6 min
A padlock in the browser is the start, not the finish. This guide covers TLS 1.2 and 1.3, sensible ciphers, HSTS and preloading, and the shrinking certificate lifetimes that make automation mandatory.
High impact5 min
Compare
Interactive comparison
Five web server options scored from 1 to 5 for a small, self-managed site; higher is always better.
Best for small teams that want HTTPS and renewal handled without any extra work.
Best for admins who want a lean, well-documented server and are happy to add an ACME client.
Best where a hosting control panel provides it as an Apache replacement.
Best for applications that rely on .htaccess rules and for teams that know Apache well.
Best for self-managed WordPress hosts that want LiteSpeed caching without a licence.
| Criterion | Caddy | Nginx | LiteSpeed Enterprise | Apache HTTP Server | OpenLiteSpeed |
|---|---|---|---|---|---|
| Secure defaults | |||||
| Automatic HTTPS | |||||
| Low configuration risk | |||||
| Small attack surface | |||||
| Patch delivery | |||||
| Resilience under load |
Editorial assessment as of 31 October 2026. Scores from 1 to 5, higher is better. Your weights only change the order. Read the full comparison
Interactive comparison
Four distribution families scored from 1 to 5 as long-running servers for small teams; higher is always better.
Best for teams that want a stable, community-run server system with a clear advisory process.
Best for teams that want long support, wide documentation and updates on by default.
Best for admins who want ten years of free support and SELinux enforcing by default.
Best as a small container base image that is rebuilt often.
| Criterion | Debian stable | Ubuntu LTS | Rocky Linux and AlmaLinux | Alpine Linux |
|---|---|---|---|---|
| Long support period | ||||
| Clear security updates | ||||
| Mandatory access control | ||||
| Small footprint | ||||
| Easy automatic updates | ||||
| Container base fit |
Editorial assessment as of 31 October 2026. Scores from 1 to 5, higher is better. Your weights only change the order. Read the full comparison
Tools for this section
