Web Servers · HTTPS · Information Security · Web Infrastructure · Comparison BriefVersions and figures as of 27 October 2026
Three servers, one job: hold the certificate and speak TLS
Apache, Nginx and Caddy: which HTTPS web server
A web server that speaks HTTPS has to hold a certificate, negotiate TLS and pass requests on to the site behind it. Apache, Nginx and Caddy all do this well, but differently. Caddy gets and renews certificates by itself and turns HTTP/3 on by default. Nginx is the fastest and lightest of the three, though its HTTP/3 is still marked experimental. Apache has no official HTTP/3, but its per-folder configuration and its modules keep it at the centre of shared hosting. Meanwhile the ground is moving: Let’s Encrypt certificates are getting shorter and its OCSP service is gone.
What Happened
Three releases, a round of fixes, and shorter certificates October 2026, graded by how far each item is established
- 1.30.6Nginx stable, 14 October 2026, fixing five flaws; mainline 1.31.8 followed on 21 October
- 2.4.69Apache, 1 October 2026, fixing 20 CVEs
- 2.11.7Caddy, 3 October 2026
- 64 daysDefault Let’s Encrypt lifetime from 10 February 2027, down from 90
Confirmed
The three releases and their fixes come from each project’s own pages. nginx.org rates all five October flaws “medium”; one lets a forged TLS session skip a client-certificate check when session tickets are used. The certificate timetable and the end of OCSP come from Let’s Encrypt.
Reported by third parties
Speed and memory figures come from GetMind’s own test and from Tech Insider, not from the projects.
Not in official releases
HTTP/3 for Apache. A third-party repository, CodeIT, packages an experimental mod_http3, but it needs a patch to Apache that had not been merged upstream when CodeIT wrote on 8 October 2026.
Timeline
From Caddy’s first release to 45-day certificates Dates as each source gives them; the last three are scheduled
- 28 Apr 2015Caddy’s first release; it has issued certificates automatically since it was feasible that year (Wikipedia; Caddy).
- 5 Dec 2024Let’s Encrypt announces it will end OCSP (Let’s Encrypt).
- 7 May 2025OCSP URLs are dropped from its certificates (Let’s Encrypt).
- 6 Aug 2025Its OCSP responders are turned off (Let’s Encrypt).
- 11 Sep 2025Native ACME support comes to Nginx as a module written in Rust (Let’s Encrypt).
- 11 Nov 2025Kubernetes announces that the community ingress-nginx controller will retire, with no fixes after March 2026 (Kubernetes).
- 2 Dec 2025Let’s Encrypt says its 90-day certificates will be cut to 45 days by 2028 (Let’s Encrypt).
- 20 Mar 2026Ingress2Gateway 1.0 is released to help clusters move to Gateway API (Kubernetes).
- Apr 2026Nginx 1.30 becomes the stable branch, adding sticky sessions and ECH and keeping upstream connections alive by default (nginx; Help Net Security).
- 13 May 2026Let’s Encrypt’s opt-in tlsserver profile starts issuing 45-day certificates (Let’s Encrypt).
- 1 Oct 2026Apache 2.4.69 is released (Apache).
- 3 Oct 2026Caddy 2.11.7 is released (Wikipedia).
- 14 Oct 2026Nginx 1.30.6 and 1.31.7 fix five vulnerabilities (nginx).
- 10 Feb 2027Scheduled: the default classic profile moves to 64-day certificates (Let’s Encrypt).
- 16 Feb 2028Scheduled: the classic profile moves to 45 days (Let’s Encrypt).
- 15 Mar 2029Scheduled: industry rules cap certificate lifetimes at 47 days (Let’s Encrypt).
The Argument
Caddy for simplicity, Nginx for scale, Apache for compatibility What the projects’ own documents support, and what complicates it
All three now default to sound TLS, but they get there differently. Nginx has used TLS 1.2 and 1.3 by default since 1.27.3, and Caddy’s protocols run from TLS 1.2 to 1.3. Apache’s mod_ssl defaults to SSLProtocol all -SSLv3, so what is actually enabled depends on the OpenSSL underneath, and it is safer to name the versions outright. The real differences lie around TLS. Caddy obtains and renews certificates, redirects HTTP to HTTPS, and serves HTTP/3 without being asked. Nginx can do the first through its ACME module, though not for wildcard names, and nginx.org still calls its HTTP/3 module “experimental”. Apache’s mod_md handles ACME but is labelled experimental, and for wildcard names its documentation says Apache “cannot do that on its own”. None of the three adds the HSTS header for you.
- ~2×Nginx’s lead over Caddy on static files in GetMind’s test
- ~30%Its lead as a reverse proxy, where the app behind usually sets the pace
- 45 daysLet’s Encrypt’s default lifetime from 16 February 2028
What complicates it
Speed rankings come from third parties, and they are not unanimous. GetMind found Nginx about twice as fast on static files and about 30% faster as a proxy. Tech Insider reports Caddy ahead by 23% with HTTP/3 on, and Nginx using about a quarter of Caddy’s memory at 10,000 idle connections, 89 MB against 340 MB. For most sites, as GetMind puts it, the difference does not matter, because both handle far more requests than a normal site will see. And the market is no longer a two-horse race: on 27 October 2026 W3Techs counted Cloudflare’s own server on 32.9% of sites, ahead of Nginx on 30.1%.
What Others Add
Certificates, OCSP and Kubernetes Each item as the named source gives it
| Question | What the record shows | Source |
|---|---|---|
| How should renewal work now? | Let’s Encrypt recommends ACME Renewal Information (ARI), which tells a client when to renew. A fixed renewal schedule written for 90-day certificates will stop fitting as lifetimes shrink. | Let’s Encrypt |
| Is OCSP stapling still worth turning on? | Not for Let’s Encrypt certificates. Their OCSP URLs were removed on 7 May 2025 and the responders turned off on 6 August 2025, so there is nothing to staple. That conclusion is ours, drawn from those dates. | Let’s Encrypt |
| What about Nginx on Kubernetes? | The community ingress-nginx controller retired after March 2026, with “no further releases, no bugfixes, and no updates to resolve any security vulnerabilities”. Kubernetes points users to Gateway API, and Ingress2Gateway 1.0 helps convert. Nginx itself is unaffected. | Kubernetes |
Wildcards
Wildcard certificates need DNS
- Caddy needs a build that includes a DNS provider module.
- Apache’s mod_md needs a script you supply to update DNS.
- Nginx’s ACME module does not support wildcards, so a separate ACME client is used.
Internal sites
Private certificates
- Caddy’s
tls internalissues certificates from its own local CA. - Apache’s mod_md can point at your own ACME server instead of Let’s Encrypt.
- Caddy’s
Conclusion
Which server suits which site Each card: who it is for, its strongest point, and the trade-off
Caddy
Small and medium sites, home labs, teams without an operations person
- Best at: HTTPS that runs itself, with certificates, redirects and HTTP/3 on by default.
- Trade-off: more memory and less raw speed than Nginx under heavy load.
Nginx
Busy sites, load balancers, reverse proxies in front of many apps
- Best at: the highest throughput and lowest memory use of the three.
- Trade-off: HTTP/3 is still experimental, and certificates usually need a separate tool.
Apache
Shared hosting, older PHP applications, setups built on Apache modules
- Best at: per-folder .htaccess files and the largest library of modules.
- Trade-off: no official HTTP/3, so put Nginx, Caddy or a CDN in front for it.
- Upgrade this month. Nginx to 1.30.6 or later, Apache to 2.4.69, Caddy to 2.11.7.
- Automate renewal with ARI, and watch expiry dates. A fixed schedule will break as lifetimes shrink.
- Add HSTS yourself, and drop OCSP stapling for Let’s Encrypt certificates.
Quick notes
- nginx.org, news, security advisories, “Configuring HTTPS servers”, ngx_http_v3_module, ngx_http_acme_module and Changes with nginx 1.30
- Help Net Security, “What changed in nginx 1.30.0”, 15 Apr 2026
- Apache HTTP Server Project, download page, 2.4 vulnerabilities, mod_md, mod_ssl and event MPM
- pkg.go.dev, caddyserver/caddy/v2
- Wikipedia, “Caddy (web server)” and “Nginx”
- Caddy documentation, Automatic HTTPS, tls directive and global options
- Matthew McPherrin, “Decreasing Certificate Lifetimes to 45 Days”, Let’s Encrypt, 2 Dec 2025
- Let’s Encrypt, “Certificate Lifetime Rationale and Plans”
- Josh Aas, “Ending OCSP Support in 2025”, 5 Dec 2024
- Josh Aas, “Native ACME Support Comes to NGINX”, 11 Sep 2025
- Tabitha Sable, “Ingress NGINX Retirement: What You Need to Know”, Kubernetes, 11 Nov 2025
- Beka Modebadze and Steven Jin, “Announcing Ingress2Gateway 1.0”, Kubernetes, 20 Mar 2026
- W3Techs, web server usage, 27 Oct 2026
- Fabian Budde, “Caddy vs Nginx: Benchmarks and Real-World Use With 139 Sites”, GetMind, 26 Sep 2026
- Sofia Lindström, “Caddy vs Nginx 2026”, Tech Insider, 30 Apr 2026
- CodeIT, “Apache HTTP/3 Is Live”, 8 Oct 2026. All read 27 Oct 2026.
Reliable
Worth believing
Sharing a subject
- 9 Billion Requests a Day, Moved Without Rebuilding a FileInformation Security · Web Infrastructure
- AI Reasoning Traces: Encrypted, Not HiddenInformation Security
- Sophistication Stopped Telling You WhoInformation Security
- A race in Linux's TCP handshake, open since kernel 4.4Information Security
- REST, SOAP, gRPC, GraphQL and MCP: pick by who callsWeb Infrastructure
Sharing a source domain
- REST, SOAP, gRPC, GraphQL and MCP: pick by who callstech-insider.org · wikipedia.org
- The Fubon Arts Court Skybridge — What It Means for Zhongxiao Fuxing Stationwikipedia.org
- 9 Billion Requests a Day, Moved Without Rebuilding a Filew3techs.com
- Grok Build Shipped Whole Repos to xAI's Cloudwikipedia.org
- China, North Korea and the Tumen River Sea Outletwikipedia.org
- The Spark That Starts a Fire — Anonymous Tip-Offs and Singapore's CPIBwikipedia.org
- Enough, or Less? Context Engineering Said Both in One Weekwikipedia.org
- It Began as Tuning an Agent. By March It Meant Everything but the Model.wikipedia.org
- The Tricks Moved Into the Model. The Writing Stayed.wikipedia.org
- Signed in Pencilwikipedia.org
- The Polyamory Words, and the One Nobody Can Datewikipedia.org
- Nineteen Numbers, Three Forces of Fourwikipedia.org
- Three Cuts Into the Uncuttablewikipedia.org
- Eighteen Hells, Ten Dates, and the Seams Between Themwikipedia.org
- Two Routes to Godhood, and What Each Leaves in the Archivewikipedia.org
- Abrahamic Religions, and the Historians Who Dispute the Labelwikipedia.org
- Not a Ladder, a Palimpsestwikipedia.org
- The Dying, Not the Bereavedwikipedia.org
- Anchored, Not Canonwikipedia.org
- The Colour Is the Vitaminwikipedia.org
- Three Legal Systems: Malaysia, Singapore and Taiwanwikipedia.org
- Dairy in East and Southeast Asiawikipedia.org
- Binance’s BNB: many chains, one coinwikipedia.org
- Brazil and Serbia: two upsets on one Sundaywikipedia.org
- Rewrite, preserve or police: three agencies that run timewikipedia.org
- Active investing: who decides, and where the reason comes fromwikipedia.org
- Passive investing: the whole market, by its valuewikipedia.org