Topic starter
11/11/2026 5:59 pm
TL;DR: 1,489,396,284 sites across 304,146,307 domains and 14,653,771 web-facing computers were found in Netcraft's June 2026 survey, with Cloudflare and Google gaining while OpenResty and Apache lost share. Hosting concentration and platform churn change where defenders must look for drift, exposure, and dependency risk.
Editorial analysis by NHI Mgmt Group, based on content published by Netcraft: “June 2026 Web Server Survey”.
By the numbers:
- The June 2026 survey received responses from 1,489,396,284 sites across 304,146,307 domains and 14,653,771 web-facing computers.
Key questions
Q: Why does web server churn create configuration drift risk?
A: Web server churn creates configuration drift risk because frequent redeployments, scaling events and image rebuilds can leave TLS settings, headers, modules and access rules inconsistent with the approved baseline.
Q: How do reverse proxies affect identity and access controls?
A: Reverse proxies sit in front of applications and can terminate TLS, enforce authentication and relay requests, so they directly shape access control decisions.
Q: How should teams reconcile web server exposure with asset inventory?
A: Teams should reconcile internet-facing web servers against the asset inventory by matching externally reachable domains, proxies and origin hosts to an authoritative list of owners, environments and services.
Practitioner guidance
- Reconcile external exposure against your asset inventory Compare internet-facing domains, reverse proxies, and origin systems against your authoritative inventory, then close any gaps where ownership is unclear.
- Revalidate hardening baselines after hosting changes Review TLS settings, access modules, logging, and update ownership whenever a site moves between server families or managed hosting layers.
- Inventory identity-adjacent paths on the edge Map admin panels, authentication endpoints, API tokens, and delegated access paths that sit behind web servers, then confirm they are covered by review and monitoring.
Bottom line: Web server market share shifts matter because they change the shape of the exposed runtime, not just the vendor leaderboard.
Glossary terms: Web Server Survey, Configuration Drift, Internet-Facing Asset, Reverse Proxy
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
Hosting concentration is a governance issue, not just a market statistic. When one platform gains or loses millions of sites, the real question is whether organisations can still prove who owns the exposed runtime, who patches it, and who can change its edge configuration. That is a control problem at internet scale, and it becomes more acute when services are fronting identity flows or admin paths.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: When should patch ownership change after a platform migration?
A: Patch ownership should change as soon as the migration cutover makes a new team operationally responsible for the platform, including patch deployment, rollback and emergency maintenance. The old owner should retain no standing responsibility once the service, host or cluster has been handed over, because split ownership leads to missed patches and unclear accountability.
👉 Read our full editorial: Web server market shifts expose hosting concentration and churn