{"id":15807,"date":"2026-11-19T07:50:00","date_gmt":"2026-11-19T06:50:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=15807"},"modified":"2026-11-14T23:38:46","modified_gmt":"2026-11-14T22:38:46","slug":"enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/","title":{"rendered":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends"},"content":{"rendered":"<p>HSTS tells a browser to require HTTPS for a host while the policy is active. It can prevent an HTTP request from leaving the browser at all. It is not the only mechanism that starts a visit securely: modern browsers can prefer HTTPS for typed addresses, and HTTPS-only settings or a preload entry can already enforce it.<\/p>\n<p>A historical check on 6 September 2026 queried twenty domains at four entry points each: the base host and www, over HTTP and HTTPS. These eighty first-response samples reveal where headers appeared and where redirects pointed. They do not establish the browser&#8217;s stored policy, preload membership or the behaviour of every page and subdomain.<\/p>\n<figure class=\"lw-diagram\"><img decoding=\"async\" src=\"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/diagrams\/dia-15807-hsts-20261025.png?v=20261114\" width=\"1120\" height=\"580\" loading=\"lazy\" alt=\"Historical first responses: two base-host HSTS records, ten www-only records, eight without a header; eleven same-host HTTPS redirects, eight changed hosts, one retained HTTP. Preload status was not checked.\"><figcaption>Saved results from 6 September 2026; first-response headers and browser-enforced policy are separate evidence.<\/figcaption><\/figure>\n<h2>The host matters, and scope can extend downwards<\/h2>\n<p>A valid Strict-Transport-Security header is learned from an error-free HTTPS response for the responding host. A header from <code>www.example.com<\/code> does not establish a policy for <code>example.com<\/code>. With <code>includeSubDomains<\/code>, however, the policy also covers descendants: on www that includes <code>a.www.example.com<\/code>; on the base host it includes www and other subdomains.<\/p>\n<p>This is host scope, not a restriction to one URL path. A header on an HTTPS redirect can establish the policy before the browser follows the Location value. HTTP responses cannot establish HSTS. The max-age duration is counted from receipt and refreshed by later accepted headers; ordinary dynamic HSTS, learned from a website response rather than a browser preload list, is not automatically permanent.<\/p>\n<h2>What the twenty-domain sample recorded<\/h2>\n<p>Two HTTPS base-host responses contained HSTS: GitHub declared 31,536,000 seconds with includeSubDomains and preload; Allegro declared 15,552,000 seconds, or 180 days, without those flags. Allegro&#8217;s response was 403, which does not itself prevent an otherwise valid HSTS header from being processed over valid HTTPS.<\/p>\n<p>Ten records contained HSTS only in the sampled www HTTPS response. Eight contained none in either sampled HTTPS response. \u201cNone in these responses\u201d is narrower than \u201cnowhere on the domain\u201d: redirects were not followed, and later paths might send a header. Existing browser policies and preload coverage were not checked.<\/p>\n<p>Eleven initial HTTP base-host responses redirected to HTTPS on the same host. Eight changed to another HTTPS host; this includes Bund redirecting to <code>verwaltung.bund.de<\/code>, so not all eight targeted www. One Google response redirected to www while retaining HTTP. Three www HTTP samples returned status 200. HEAD retrieves headers without the response body. Because the tool used HEAD, that status does not prove that page content was actually downloaded or that all browsers would use HTTP.<\/p>\n<h2>A redirect is not itself HSTS<\/h2>\n<p>A same-host HTTP-to-HTTPS redirect creates an opportunity to learn HSTS if the HTTPS response actually carries an acceptable header. The redirect alone establishes no policy. A direct HTTP-base-to-HTTPS-www redirect cannot make a www header apply upwards to the base host. But it also does not prove that every visit began over HTTP: prior policy, preload and browser HTTPS upgrades can change the route.<\/p>\n<p>The assertion that most visitors type the base host was not measured. A private window or a new profile also does not imply an unavoidable plaintext request. The relevant distinction is whether HTTPS is enforced or preferred in that browser before the network request starts.<\/p>\n<h2>Preload is a separate decision<\/h2>\n<p>A preload entry can supply an HSTS policy before the first visit in a browser that ships that entry. The preload token in a header is not proof of inclusion, and a favourable local check is not proof either. The current hstspreload.org guidance recommends HSTS but does not generally recommend preloading, citing its limited additional benefit alongside modern HTTPS upgrades.<\/p>\n<p>The submission requirements include a valid certificate, HTTPS support for all relevant subdomains including internal ones, and an appropriate base-domain HSTS header: at least 31,536,000 seconds, includeSubDomains and preload. If port 80 is served, the first redirect must go to HTTPS on the same host. An additional redirect from the base HTTPS endpoint must itself carry HSTS.<\/p>\n<p>The historical checker marked one record, GitHub, as ready according to its local tests. It did not test every subdomain or query a preload list. There is no basis for concluding that the other nineteen were absent from all browser lists. Header directives are case-insensitive, so includeSubdomains with a lowercase d is not an error.<\/p>\n<p>Preload inclusion and removal depend on distribution to browsers. Removal is not an immediate rollback; the service describes delays of months and cannot guarantee timing for other browsers. The flag should therefore not be an automatic last step in an HSTS tutorial.<\/p>\n\n\n<!-- lw-flux-illu 15807-a4 -->\n<figure class=\"lw-illu\"><img src=\"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/illustrationen\/flux-15807-a4.webp\" width=\"1120\" height=\"630\" loading=\"lazy\" decoding=\"async\" alt=\"Young apple trees stand planted in a row, while one sapling with the same ribbon still waits in its pot. Likewise, the preload flag alone does not prove a site is on the browsers&#039; preload list.\"><figcaption>Young apple trees stand planted in a row, while one sapling with the same ribbon still waits in its pot. Likewise, the preload flag alone does not prove a site is on the browsers&#039; preload list.<\/figcaption><\/figure>\n\n\n<h2>The historical finding for this site<\/h2>\n<p>The saved first responses for lukaswojcik.com contained no HSTS header. The HTTP base address redirected directly to HTTPS www; the HTTPS www root then redirected to <code>\/en\/<\/code>. That final language path was outside the four-response test. This is a dated observation, not a claim that every current response on this site lacks HSTS.<\/p>\n<p>A base-host HTTPS redirect can carry its own policy. Subdomain coverage requires includeSubDomains explicitly; adding a base-host header alone does not cover all subdomains. The historical sample contains no inventory proving the current status of retired or internal hosts.<\/p>\n<h2>A transparent four-response check<\/h2>\n<p>The following Bash example deliberately makes four HEAD requests without following redirects. The example.com addresses are placeholders. It preserves full headers, reports connection failures and continues through all four entry points. TLS certificate verification remains enabled.<\/p>\n<figure style=\"--cbb-digits:2\" class=\"cbb cbb--wrap cbb--numbers wp-block-code-beautifier-block-code\" data-lang=\"bash\"><figcaption class=\"cbb-head\"><span class=\"cbb-lang\">Shell<\/span><span class=\"cbb-actions\"><button type=\"button\" class=\"cbb-button cbb-button--wrap\" data-cbb-action=\"wrap\" aria-pressed=\"true\" title=\"Wrap long lines\"><svg aria-hidden=\"true\" focusable=\"false\" width=\"16\" height=\"16\" viewBox=\"0 0 16 16\"><path d=\"M2 4h12M2 8h9.5a2.5 2.5 0 0 1 0 5H8m0 0 1.5-1.5M8 13l1.5 1.5M2 12h3\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/><\/svg><span class=\"cbb-sr\">Wrap long lines<\/span><\/button><button type=\"button\" class=\"cbb-button cbb-button--copy\" data-cbb-action=\"copy\" aria-label=\"Copy code\" data-cbb-status-done=\"Code copied to the clipboard.\" data-cbb-status-failed=\"Copying failed. The code is selected for copying with Ctrl+C or \u2318+C.\" data-cbb-status-noselect=\"Copying failed.\"><svg aria-hidden=\"true\" focusable=\"false\" width=\"16\" height=\"16\" viewBox=\"0 0 16 16\"><rect x=\"5.5\" y=\"5.5\" width=\"8\" height=\"8.5\" rx=\"1.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\"\/><path d=\"M10.5 3.5V3A1.5 1.5 0 0 0 9 1.5H4A1.5 1.5 0 0 0 2.5 3v6.5A1.5 1.5 0 0 0 4 11h.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\"\/><\/svg><span class=\"cbb-button-label\">Copy<\/span><\/button><\/span><\/figcaption><pre class=\"cbb-pre\" tabindex=\"0\" role=\"region\" aria-label=\"Code example: Shell\"><code class=\"cbb-code language-bash\" style=\"counter-reset:cbb-line 0;\"><span class=\"cbb-line\"><span class=\"cbb-comment\">#!\/usr\/bin\/env bash<\/span>\n<\/span><span class=\"cbb-line\"><span class=\"cbb-keyword\">set<\/span> <span class=\"cbb-attr\">-u<\/span>\n<\/span><span class=\"cbb-line\">out=<span class=\"cbb-variable\">$(<\/span>mktemp <span class=\"cbb-attr\">-d<\/span>) <span class=\"cbb-operator\">||<\/span> <span class=\"cbb-keyword\">exit<\/span> <span class=\"cbb-number\">1<\/span>\n<\/span><span class=\"cbb-line\">failed=<span class=\"cbb-number\">0<\/span>\n<\/span><span class=\"cbb-line\">index=<span class=\"cbb-number\">0<\/span>\n<\/span><span class=\"cbb-line\"><span class=\"cbb-keyword\">for<\/span> url <span class=\"cbb-keyword\">in<\/span> http:\/\/example.com\/ https:\/\/example.com\/ \\\n<\/span><span class=\"cbb-line\">           http:\/\/www.example.com\/ https:\/\/www.example.com\/<span class=\"cbb-operator\">;<\/span> <span class=\"cbb-keyword\">do<\/span>\n<\/span><span class=\"cbb-line\">  index=<span class=\"cbb-variable\">$((<\/span>index + <span class=\"cbb-number\">1<\/span>))\n<\/span><span class=\"cbb-line\">  <span class=\"cbb-function\">printf<\/span> <span class=\"cbb-string\">'\\n%s\\n'<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$url<\/span><span class=\"cbb-string\">\"<\/span>\n<\/span><span class=\"cbb-line\">  <span class=\"cbb-keyword\">if<\/span> <span class=\"cbb-function\">curl<\/span> <span class=\"cbb-attr\">--silent<\/span> <span class=\"cbb-attr\">--show-error<\/span> <span class=\"cbb-attr\">--head<\/span> <span class=\"cbb-attr\">--proto<\/span> <span class=\"cbb-string\">'=http,https'<\/span> \\\n<\/span><span class=\"cbb-line\">      <span class=\"cbb-attr\">--connect-timeout<\/span> <span class=\"cbb-number\">10<\/span> <span class=\"cbb-attr\">--max-time<\/span> <span class=\"cbb-number\">20<\/span> \\\n<\/span><span class=\"cbb-line\">      <span class=\"cbb-attr\">-D<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$out<\/span><span class=\"cbb-string\">\/<\/span><span class=\"cbb-variable\">$index<\/span><span class=\"cbb-string\">.headers\"<\/span> <span class=\"cbb-attr\">-o<\/span> \/dev\/null \\\n<\/span><span class=\"cbb-line\">      <span class=\"cbb-attr\">-w<\/span> <span class=\"cbb-string\">'status=%{http_code}\\n'<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$url<\/span><span class=\"cbb-string\">\"<\/span><span class=\"cbb-operator\">;<\/span> <span class=\"cbb-keyword\">then<\/span>\n<\/span><span class=\"cbb-line\">    <span class=\"cbb-function\">cat<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$out<\/span><span class=\"cbb-string\">\/<\/span><span class=\"cbb-variable\">$index<\/span><span class=\"cbb-string\">.headers\"<\/span>\n<\/span><span class=\"cbb-line\">  <span class=\"cbb-keyword\">else<\/span>\n<\/span><span class=\"cbb-line\">    <span class=\"cbb-function\">printf<\/span> <span class=\"cbb-string\">'Request failed: %s\\n'<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$url<\/span><span class=\"cbb-string\">\"<\/span> <span class=\"cbb-operator\">&gt;<\/span>&amp;<span class=\"cbb-number\">2<\/span>\n<\/span><span class=\"cbb-line\">    failed=<span class=\"cbb-number\">1<\/span>\n<\/span><span class=\"cbb-line\">  <span class=\"cbb-keyword\">fi<\/span>\n<\/span><span class=\"cbb-line\"><span class=\"cbb-keyword\">done<\/span>\n<\/span><span class=\"cbb-line\"><span class=\"cbb-function\">printf<\/span> <span class=\"cbb-string\">'\\nSaved first-response headers: %s\\n'<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$out<\/span><span class=\"cbb-string\">\"<\/span>\n<\/span><span class=\"cbb-line\"><span class=\"cbb-keyword\">exit<\/span> <span class=\"cbb-string\">\"<\/span><span class=\"cbb-variable\">$failed<\/span><span class=\"cbb-string\">\"<\/span><\/span><\/code><\/pre><span class=\"cbb-status\" role=\"status\"><\/span><\/figure>\n<p>HEAD can differ from GET in a particular deployment. A fuller audit follows every relevant redirect with method and host recorded, checks GET responses as needed, validates header syntax, and inspects browser policy and current preload status separately. An HTTP 200, a missing header or a transport failure is not interchangeable evidence.<\/p>\n<p>The <a href=\"https:\/\/www.lukaswojcik.com\/blog\/en\/toolbox\/hsts-preload-readiness-checker\/\">HSTS and Preload Readiness Checker<\/a> provides this initial inventory. The reviewed implementation makes four first-response HEAD probes, not a complete redirect-chain audit. Its readiness label is preliminary, and its simple header parser does not fully validate every malformed or duplicate directive case.<\/p>\n<div class=\"lw-faq\"><h2>Questions and answers<\/h2><h3>Why is HSTS ignored over HTTP?<\/h3><p>An unauthenticated response could be modified on the network. HSTS is therefore accepted only through a valid secure connection; a header received over HTTP cannot establish or delete the policy.<\/p><h3>Does an expired certificate cause an outage for the whole max-age?<\/h3><p>No. An active HSTS policy prevents the usual certificate-warning bypass, but repairing the certificate and TLS configuration can restore access immediately. Waiting for policy expiry is not the required remedy. Monitoring certificate renewal remains important for every covered host.<\/p><h3>How can deployment proceed gradually?<\/h3><p>First, HTTPS and certificate handling must work on the intended hosts. A short policy such as max-age=300 can limit the duration of a new dynamic setting; it does not shorten an already cached longer policy until the browser receives the update. Longer stages require monitoring and time for the previous stage to expire. includeSubDomains needs an inventory of affected hosts. Preloading remains an independent, deliberate decision.<\/p><h3>What does max-age=0 remove?<\/h3><p>Received over valid HTTPS, it removes that host&#8217;s dynamic policy. Simply omitting the header does not remove an existing policy. A parent policy covering subdomains, a separately stored child policy or preload coverage can still require HTTPS. Preload removal follows a separate process.<\/p><h3>Must the base host be visited as the main page?<\/h3><p>No. A valid HTTPS response from the base host can establish its policy even when obtained as a resource, subject to the browser actually making and processing that request. Preload or an applicable parent policy can also provide coverage. A request to www alone cannot teach the browser an unknown base-host policy.<\/p><h3>What happens to explicit HTTP ports?<\/h3><p>For a covered host, HSTS upgrades HTTP to HTTPS. An explicit port 80 becomes 443; another explicit port is retained. An HTTP-only service on port 8080 therefore does not automatically move to HTTPS port 443 and may fail after the upgrade.<\/p><\/div>\n<div class=\"lw-quellen\"><h2>Sources<\/h2><ul><li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc6797.html\" target=\"_blank\" rel=\"noopener noreferrer\">IETF RFC 6797: HTTP Strict Transport Security<\/a><\/li><li><a href=\"https:\/\/hstspreload.org\/\" target=\"_blank\" rel=\"noopener noreferrer\">Chromium HSTS preload service: Recommendations, requirements and removal<\/a><\/li><li><a href=\"https:\/\/blog.chromium.org\/2021\/03\/a-safer-default-for-navigation-https.html\" target=\"_blank\" rel=\"noopener noreferrer\">Chromium: HTTPS as the default for typed navigation<\/a><\/li><li><a href=\"https:\/\/support.mozilla.org\/en-US\/kb\/https-only-prefs\" target=\"_blank\" rel=\"noopener noreferrer\">Mozilla Support: HTTPS-Only Mode in Firefox<\/a><\/li><li><a href=\"https:\/\/curl.se\/docs\/manpage.html\" target=\"_blank\" rel=\"noopener noreferrer\">curl: Command-line reference<\/a><\/li><\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"<p>A historical check of twenty domains separates HSTS host scope, redirects and preload eligibility. Eighty first-response samples show headers, but do not establish browser policy or actual preload membership.<\/p>\n","protected":false},"author":1,"featured_media":31125,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[137],"tags":[91243,91219,91115],"class_list":["post-15807","post","type-post","status-publish","format-standard","hentry","category-tutorials-en-it-networks","tag-networking","tag-tutorial","tag-web-security"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik<\/title>\n<meta name=\"description\" content=\"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik\" \/>\n<meta property=\"og:description\" content=\"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/\" \/>\n<meta property=\"og:site_name\" content=\"Lukas Wojcik - Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-19T06:50:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Lukas Wojcik\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Lukas Wojcik\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/\"},\"author\":{\"name\":\"Lukas Wojcik\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#\\\/schema\\\/person\\\/895f7604f9b6b71aad9bba33af28d0f9\"},\"headline\":\"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends\",\"datePublished\":\"2026-11-19T06:50:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/\"},\"wordCount\":1368,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#\\\/schema\\\/person\\\/895f7604f9b6b71aad9bba33af28d0f9\"},\"image\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/klarheit-20261111-15807.png\",\"keywords\":[\"Networking\",\"Tutorial\",\"Web Security\"],\"articleSection\":[\"Tutorials\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/\",\"url\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/\",\"name\":\"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/klarheit-20261111-15807.png\",\"datePublished\":\"2026-11-19T06:50:00+00:00\",\"description\":\"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/klarheit-20261111-15807.png\",\"contentUrl\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/klarheit-20261111-15807.png\",\"width\":1200,\"height\":630,\"caption\":\"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/en\\\/it-networks\\\/tutorials-en-it-networks\\\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/de\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/\",\"name\":\"Lukas Wojcik - Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#\\\/schema\\\/person\\\/895f7604f9b6b71aad9bba33af28d0f9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/#\\\/schema\\\/person\\\/895f7604f9b6b71aad9bba33af28d0f9\",\"name\":\"Lukas Wojcik\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/lw-x2.jpg\",\"url\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/lw-x2.jpg\",\"contentUrl\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/lw-x2.jpg\",\"width\":424,\"height\":636,\"caption\":\"Lukas Wojcik\"},\"logo\":{\"@id\":\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/lw-x2.jpg\"},\"sameAs\":[\"https:\\\/\\\/www.lukaswojcik.com\\\/blog\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik","description":"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/","og_locale":"en_US","og_type":"article","og_title":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik","og_description":"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.","og_url":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/","og_site_name":"Lukas Wojcik - Blog","article_published_time":"2026-11-19T06:50:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png","type":"image\/png"}],"author":"Lukas Wojcik","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Lukas Wojcik","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#article","isPartOf":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/"},"author":{"name":"Lukas Wojcik","@id":"https:\/\/www.lukaswojcik.com\/blog\/#\/schema\/person\/895f7604f9b6b71aad9bba33af28d0f9"},"headline":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends","datePublished":"2026-11-19T06:50:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/"},"wordCount":1368,"commentCount":0,"publisher":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/#\/schema\/person\/895f7604f9b6b71aad9bba33af28d0f9"},"image":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#primaryimage"},"thumbnailUrl":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png","keywords":["Networking","Tutorial","Web Security"],"articleSection":["Tutorials"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/","url":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/","name":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends | Lukas Wojcik","isPartOf":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#primaryimage"},"image":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#primaryimage"},"thumbnailUrl":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png","datePublished":"2026-11-19T06:50:00+00:00","description":"Why HSTS has to be measured on four addresses, what ten www-only headers actually protect, and which single domain of twenty meets all preload conditions.","breadcrumb":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#primaryimage","url":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png","contentUrl":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/11\/klarheit-20261111-15807.png","width":1200,"height":630,"caption":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends"},{"@type":"BreadcrumbList","@id":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/tutorials-en-it-networks\/enforcing-https-in-the-browser-how-hsts-works-and-where-its-protection-ends\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.lukaswojcik.com\/blog\/de\/"},{"@type":"ListItem","position":2,"name":"Enforcing HTTPS in the Browser: How HSTS Works and Where Its Protection Ends"}]},{"@type":"WebSite","@id":"https:\/\/www.lukaswojcik.com\/blog\/#website","url":"https:\/\/www.lukaswojcik.com\/blog\/","name":"Lukas Wojcik - Blog","description":"","publisher":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/#\/schema\/person\/895f7604f9b6b71aad9bba33af28d0f9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.lukaswojcik.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.lukaswojcik.com\/blog\/#\/schema\/person\/895f7604f9b6b71aad9bba33af28d0f9","name":"Lukas Wojcik","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/07\/lw-x2.jpg","url":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/07\/lw-x2.jpg","contentUrl":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/07\/lw-x2.jpg","width":424,"height":636,"caption":"Lukas Wojcik"},"logo":{"@id":"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/2026\/07\/lw-x2.jpg"},"sameAs":["https:\/\/www.lukaswojcik.com\/blog"]}]}},"_links":{"self":[{"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/posts\/15807","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/comments?post=15807"}],"version-history":[{"count":8,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/posts\/15807\/revisions"}],"predecessor-version":[{"id":33974,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/posts\/15807\/revisions\/33974"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/media\/31125"}],"wp:attachment":[{"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/media?parent=15807"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/categories?post=15807"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lukaswojcik.com\/blog\/wp-json\/wp\/v2\/tags?post=15807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}