Skip to content
PeekWellThe Handbook
Join now

HSTS and HTTPS under UK GDPR: what the ICO asks

At a glance

UK-17MediumUK GDPR Art. 32(1)(a); Art. 5(1)(f); ICO encryption guidance

Peeky checks how your site's connection is set up: a move from http to https on every address, a valid TLS identity, TLS 1.2 or newer, nothing loaded or sent over http, and HSTS.

Last checked against the source:

I need to fix thisI need the rule

The rule

Article 32 of the UK GDPR is headed security of processing. It’s risk-based and names no technology. The ICO’s penalty notice to DPP Law Ltd sets out its core text.

Article 32(1) reads: “Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk”. Article 32(2) adds that in assessing the appropriate level of security, account is to be taken “in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed”.

The word “transmitted” matters for a website. It brings data on its way between a visitor’s browser and your server inside the article. Article 32(1) also lists “the pseudonymisation and encryption of personal data” among its examples.

The ICO’s encryption guidance states that “if you provide a website, you should use HTTPS across all its pages. This is especially important for safeguarding personal information.” It relays the NCSC’s statement that SSL “must not be used” on a public-facing HTTPS site, says TLS 1.3 and 1.2 provide strong protection when configured correctly, and recommends HTTP Strict Transport Security (HSTS) “to force all connections to use HTTPS instead of unencrypted HTTP”.

That makes the ICO the most direct of the regulators this check draws on about HSTS. It’s still a recommendation in guidance, not a line in the Act.

Article 83(4) allows fines “up to £8,700,000, or in the case of an undertaking, up to 2 % of the total worldwide annual turnover of the preceding financial year, whichever is higher” for infringements of, among others, “the obligations of the controller and the processor pursuant to Articles 8, 11, 25 to 39 and 42 and 43”, which includes Article 32.

What PeekWell checks and how

UK-17 asks one question: does every visit to your site travel over a properly set up encrypted connection? It looks at what your servers show anyone, and nothing else.

The scan is automated. It fails if any of these turns up on the addresses it visited:

  • an address that answers on plain http without a permanent move to https, including the www and bare-domain versions and any language addresses
  • a TLS identity that has expired, doesn’t match the address or can’t be traced to a trusted issuer
  • a connection older than TLS 1.2
  • a page on HTTPS that loads scripts, frames or other active content over plain http
  • a form that sends what people type to an http address
  • no HSTS header

Each one follows the ICO’s encryption guidance: HTTPS across all pages, no SSL, recent TLS, and HSTS to force the encrypted version. Images or video pulled in over http are left out. The report has one line for each address it checked, saying what it found there.

The scan has limits, and the report says so. It reads the connection setup of the public addresses it visited and nothing more. It doesn’t port-scan, try to get in where it isn’t allowed, run any security test or open addresses nobody linked to. It can’t see how data is stored or what happens on a server after a form is sent. A Passed means the expected setup was seen on the addresses scanned. It doesn’t say the site complies.

The browser protections a server sends with each page, such as Content-Security-Policy, are a separate check, UK-15. EU-19 and US-16 ask this question under European and American law.

Why it matters for a company

We found no ICO decision that turns on a site served over http or an expired TLS identity. The ICO’s security decisions we read all followed an incident in which data was exposed or taken, as the ones on UK-15 show.

Other regulators have acted on these facts alone. The Garante fined an Italian water utility 15,000 euros in 2022 because its customer area ran over http, and the Spanish AEPD opened a case against a town council whose TLS identity had expired years earlier. Those decisions, on EU-19, apply an Article 32 worded the same way as the UK’s.

What the ICO has said is in its guidance, and the guidance is specific: HTTPS on every page, no SSL, and HSTS. Its data security guide also asks for “a process for regularly testing, assessing and evaluating the effectiveness of any measures you put in place”. A browser warning on your own site is exactly the kind of thing a test like that should catch first.

Smaller companies and larger companies

Article 32 has no size threshold, and the ICO weighs turnover only when it sets a fine. The risk to the people whose data passes through counts more than the headcount.

In a smaller company the site is often a hosted builder or a plugin-heavy content system. The main address has HTTPS, and the gaps are at the edges: an old subdomain on plain http, a contact form that still posts to an http address, a TLS identity that expired because the renewal was tied to one person’s card, and a host whose default sends no HSTS header.

In a larger company the same problems multiply. There are many hostnames, agency microsites and legacy portals, each with its own TLS settings, and the customer area doesn’t always match the main site. One forgotten host is enough to fail the check.

Enforcement cases

Published decisions about other companies, listed for context. Each links to the authority's own page. They say nothing about any particular website.

The Officer, squinting at a file.

Larger companies

No decision is listed here yet.

Smaller companies

As of 3 November 2026 we found no ICO decision about an organisation of any size that turns on a site served over plain http, an expired TLS identity, an old TLS version or a missing HSTS header. The ICO's website security reprimands and penalties, listed on UK-15, concern access controls, unpatched software and changed scripts. Decisions by EU authorities on the same facts as this check are listed on EU-19.

How to fix it

The order follows the ICO’s guidance: HTTPS across all pages, no SSL, recent TLS versions, and HSTS to force the encrypted version.

  1. List every hostname. Write down the main domain, www, the shop, the customer area, the blog and any subdomain your pages link to, including ones an agency built.
  2. Redirect http to https everywhere. Use a permanent redirect on every hostname, to the same host.
  3. Allow only TLS 1.2 and 1.3. Switch off SSL and older TLS versions in the server, load balancer or CDN settings.
  4. Automate renewal and watch the dates. Let the TLS identity renew by itself and send expiry warnings to a shared mailbox.
  5. Fix active mixed content and form addresses. Search templates, the database and the page builder for http:// links to scripts and frames, and for forms that post to http://. Change them to https:// or to relative paths.
  6. Add HSTS, then raise it. Start with a short max-age, check nothing breaks, then extend it. Add includeSubDomains only when every subdomain answers over HTTPS.
  7. Test on a schedule. The ICO’s guide asks for regular testing of the measures. Put a dated re-scan in the calendar, and run one now to check every address passes.
server {
  listen 80;
  server_name example.co.uk www.example.co.uk;
  return 301 https://$host$request_uri;
}
# inside the HTTPS server block
ssl_protocols TLSv1.2 TLSv1.3;
add_header Strict-Transport-Security "max-age=86400" always;

The snippet is a starting point. Whether it meets your obligations is a question for your adviser, and Peeky reports only what it sees.

Questions

What is HSTS and does the ICO ask for it?

HSTS is a header that tells a browser to always use the encrypted version of your site, even when someone types http. The ICO's encryption guidance recommends it "to force all connections to use HTTPS instead of unencrypted HTTP".

It's a recommendation, and no ICO decision we found turns on it. UK-17 still fails without it, because it's the setting that keeps visitors on HTTPS.

Does the ICO say a website should use HTTPS?

Yes. The ICO's guidance on encryption says that if you provide a website, you should use HTTPS across all its pages, and that this is especially important for safeguarding personal information. It relays the NCSC's statement that SSL "must not be used" on a public-facing HTTPS site.

What happens if a site's TLS setup has expired?

Visitors see a browser warning, and the connection can no longer be trusted until the site renews it. An expiry date that has passed fails UK-17. The fix is usually a renewal that runs by itself, with warnings sent to a shared mailbox.

What is mixed content?

It's a page that opens over HTTPS but pulls some of its parts over plain http. When those parts are scripts or frames, someone on the network could change them, so UK-17 fails a page that loads them. Images or video over http are left out of the check.

Should I add my site to the HSTS preload list?

It's optional. Preloading puts your domain on a list built into browsers, so even a first visit goes straight to HTTPS. The ICO's guidance doesn't mention it and UK-17 doesn't ask for it.

If you do it, wait until every subdomain works over HTTPS, because the list covers all of them.

Filed with

The rule

UK GDPR (retained Regulation (EU) 2016/679), Arts. 5(1)(f), 32 and 83(4)

Read the rule (UK GDPR (retained Regulation (EU) 2016/679), Arts. 5(1)(f), 32 and 83(4))

Your site

Is your website affected? Join now to find out.

Join now

Sources

The law

  1. legislation.gov.uk, UK GDPR Art. 32 (security of processing)
  2. legislation.gov.uk, UK GDPR Art. 5 (principles, including integrity and confidentiality in 5(1)(f))
  3. legislation.gov.uk, UK GDPR Art. 83 (administrative fines), revised version in force

Guidance

  1. ICO, Encryption and data transfer (transport layer encryption)
  2. ICO, A guide to data security
  3. NCSC, Using TLS to protect data
  4. NCSC, Small organisations guide to cyber security

Decisions and cases

  1. ICO, Penalty notice: DPP Law Ltd, 14 April 2025

Last checked against the source:

For information only. Not legal advice.