Hs
Security · 1st of 96

Websites using HSTS

www.rfc-editor.org/rfc/rfc6797#section-6.1

We detect HSTS on 5,048,799 websites, 37.8% of the 13.4 million live sites we have crawled — and 69.7% of the 11,809 most popular, from google.com to cloudflare.com.

Free with a verified account · up to 3 samples a month · CSV or JSON · rank, version, tech stack, contact pages, e-mails

Live sites
5.0M
websites using it
Market share
37.8%
of the 13.4 million live sites we have crawled
Popular sites
69.7%
of the 11,809 most popular sites use it
Rank
#1
Of 96 in Security
Ranked by popularity. Click a site to see what we know about it.
+5,048,789 more sites using HSTS

Filter by rank and language. Version, full tech stack, contact pages and e-mails included.

Download a free sample →
Last scan = our latest crawl of the site.

Where it is used

From the domain extension, not from where the site is hosted. (estimated from a sample of 19,937 sites.)

.com
commercial
≈ 2.3M
45.2%
.org
organizations
≈ 348.4k
6.9%

Country domains

  • Germany.de≈ 219.1k
  • Switzerland.ch≈ 127.1k
  • United Kingdom.uk≈ 125.4k
  • Netherlands.nl≈ 124.6k
  • Australia.au≈ 106.6k
  • France.fr≈ 100k

Languages

  • English
  • German
  • French
  • Spanish
  • Japanese

HSTS at a glance

We detect HSTS on 5,048,799 websites, 37.8% of the 13.4 million live sites we have crawled. It is the most used of the 96 technologies in the Security category. Among the most popular sites, 69.7% of the top 11,809 use it (8,230), and 39.6% of the top 1.3 million (533,410). Sites using it often also use jQuery, Cloudflare and PHP. Its main alternatives in Security are Cloudflare Bot Management, reCAPTCHA and Really Simple SSL & Security. The sites using it are most often in English, followed by German and French.

Most popular sites: domains in the top 10,000 or the top 1 million of at least one public ranking (Tranco, Majestic, Open PageRank).

HSTS (HTTP Strict Transport Security) is a web security policy mechanism that helps protect websites against protocol downgrade attacks and cookie hijacking. Defined in RFC 6797, it allows web servers to declare that browsers should only interact with them using secure HTTPS connections. When a browser receives an HSTS header, it automatically converts all HTTP requests to HTTPS for the specified domain and duration. This prevents man-in-the-middle attacks where attackers might intercept initial HTTP requests before the HTTPS redirect occurs. HSTS headers can include directives like max-age (how long to enforce the policy), includeSubDomains (apply to all subdomains), and preload (for inclusion in browser HSTS preload lists). Major browsers maintain preload lists of domains that should always use HTTPS, even on first visit. Implementing HSTS is considered a security best practice and is required for compliance with many security standards and frameworks.

Adoption over time

Live sites detected, monthly · LargerIO registry.

Jul 2026 · 3,588,355 sitesAug 2026 · 3,595,336 sitesSep 2026 · 3,600,816 sitesOct 2026 · 4,998,640 sitesNov 2026 · 5,050,118 sites5,050,118 0 Jul 2026Aug 2026Sep 2026Oct 2026Nov 2026

Counts follow the sites we crawl. Our crawl grew sharply in October 2026, so part of that month's rise reflects coverage, not adoption.

Same data in your code or your AI assistant: REST API and MCP server →