
HTTP vs HTTPS: what the FTC expects of your website
At a glance
US-16Medium15 U.S.C. §45; FTC, Start with Security
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:
The rule
The United States has no single website security statute. The federal rule that reaches a company’s website is section 5 of the FTC Act, and it doesn’t mention encryption or HTTPS. The FTC builds the expectation case by case.
Section 45(a)(1) declares “unfair or deceptive acts or practices in or affecting commerce” unlawful. Section 45(n) limits the unfairness half: the Commission may not declare an act or practice unfair “unless the act or practice causes or is likely to cause substantial injury to consumers which is not reasonably avoidable by consumers themselves and not outweighed by countervailing benefits to consumers or to competition.”
So a security case under section 5 rests on injury or likely injury that consumers couldn’t avoid, weighed against the benefits. It can also be a deception case, when a company tells consumers its security is better than it is. The FTC’s own account of the Third Circuit’s ruling in FTC v. Wyndham, of 25 August 2015, says the court “upheld” that the FTC could use the unfairness power to challenge the data security lapses alleged.
“Start with Security” tells businesses to “use strong cryptography to secure confidential material during storage and transmission”, and names Transport Layer Security (TLS) encryption as one possibility. A lesson on configuration describes companies that used SSL encryption in their mobile apps but “turned off a critical process”, which left the apps open to interception.
That’s as far as the FTC goes. Its guidance names TLS for data in transit and names no headers, HSTS included. HSTS is in this check on the strength of the British and French regulators: the ICO recommends it “to force all connections to use HTTPS”, and the CNIL’s 2020 sheet mentions it. State laws add their own security duties, and differ from state to state.
What PeekWell checks and how
US-16 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
The first five follow the FTC’s line on protecting data in transit with TLS. The last one goes beyond what the FTC has said, for the reason in the rule. 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, and the check for sensitive files left open, are US-15. EU-19 and UK-17 ask this question under European and British law.
Why it matters for a company
The FTC’s clearest transport case is about apps, and the lesson carries straight over to websites.
In March 2014 the FTC settled with Fandango and Credit Karma. It alleged that both had turned off the SSL check that confirms an app is talking to the genuine server, so card details, Social Security numbers, passwords and other data sent over the connection could be intercepted. Fandango’s iOS app ran that way from March 2009 to February 2013. The orders require security programs and independent assessments every two years for 20 years.
GoDaddy is the recent one. In the matter finalized on 21 May 2025, the FTC alleged that the company claimed award-winning security while not using multi-factor authentication, not monitoring for threats and not securing connections to consumer data. The order bars misrepresenting its security and requires a security program and an independent assessor.
A gap in the connection is easy for anyone to see, a regulator included: the browser says “Not secure” on the page. And a company that also tells customers its site is secure turns the gap into a question about the claim, as GoDaddy shows.
Smaller companies and larger companies
Section 5 has no size threshold. The FTC looks at injury and at what the company could have done at reasonable cost, and a redirect and a renewing TLS identity cost very little.
In a small company the site is on HTTPS, but a subdomain from an old campaign still answers on plain http, or a contact form built years ago still posts to an http address. A TLS identity expires because the renewal went to someone who has left.
In a larger company the problem is scale. There are many hosts, staging sites that were never taken down, agency microsites and a CDN with different rules for different paths. One of them 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.

Larger companies
Fandango, LLC and Credit Karma, Inc.
The FTC alleged that both companies turned off the SSL check that confirms an app is talking to the genuine server, so card details, Social Security numbers, passwords and other data sent over the connection could be intercepted. It said Fandango's iOS app ran this way from March 2009 to February 2013, and that Credit Karma released its Android app with the same setting a month after being warned about its iOS app.
Read the FTC (United States) publication about Fandango, LLC and Credit Karma, Inc.GoDaddy Inc.
The FTC alleged that GoDaddy claimed to provide award-winning security while not using multi-factor authentication, not monitoring for security threats and not securing connections to consumer data. The order finalized in May 2025 requires a comprehensive security program, independent assessments and no misrepresentation of its security.
Read the FTC (United States) publication about GoDaddy Inc.
Smaller companies
As of 3 November 2026 we found no FTC or state action against a smaller company that turns on a website served over plain http, an expired TLS identity or a missing HSTS header. The smaller-company security cases on US-15 concern files and databases left open to anyone, not the connection.
How to fix it
The steps follow the FTC’s lesson to protect data in transit with TLS and to check that the setup works.
- List every hostname. Write down the main domain, www, the shop, the customer area, the blog and any subdomain your pages link to, including staging and campaign sites.
- Redirect http to https everywhere. Use a permanent (301) redirect on every hostname, to the same host.
- Allow only TLS 1.2 and 1.3. Switch off older versions in the server, load balancer or CDN settings. NIST’s TLS guidelines, SP 800-52, set the same floor for federal systems.
- Automate renewal and watch the dates. Let the TLS identity renew by itself and send expiry warnings to a shared mailbox.
- 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 tohttp://. Change them tohttps://or to relative paths. - Add HSTS, then raise it. Start with a short
max-age, check nothing breaks, then extend it. AddincludeSubDomainsonly when every subdomain answers over HTTPS. - Re-scan. Run a scan again and check that every address passes.
server {
listen 80;
server_name example.com www.example.com;
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;
This is a starting point. Whether it’s enough for your data is a question for your adviser, and Peeky reports only what it sees.
Questions
HTTP vs HTTPS: does US law require HTTPS on a website?
No federal statute says HTTPS. The FTC applies section 5 of the FTC Act, and its Start with Security guide tells businesses to use strong cryptography to protect sensitive data in transit, naming TLS. HTTPS is TLS applied to a website. Some states add their own security duties, such as New York's.
Is HTTP secure for a form that asks for personal details?
No. Over plain http, whatever someone types into the form travels unencrypted, so anyone on the network path can read or change it. US-16 fails a form that sends to an http address, and any address that doesn't move visitors to https.
Why does my website say not secure?
Browsers show "Not secure" when a page loads over plain http, and a full warning page when the TLS identity has expired or doesn't match the address. Both fail US-16. The usual fix is a permanent redirect to https and a TLS identity that renews by itself.
Does the FTC require HSTS?
No. HSTS is a header that tells browsers to use the encrypted version of your site every time. The FTC's guidance names TLS but no headers.
US-16 includes HSTS anyway, because it's the setting that keeps visitors on HTTPS, and the British and French data protection regulators recommend it.
How do I redirect http to https?
Add a permanent (301) redirect from every http address to the same address on https, in your web server, CDN or hosting settings. Cover the www and bare-domain versions and every subdomain. The snippet in How to fix it shows it for nginx.
Filed with
The rule
FTC Act section 5, 15 U.S.C. § 45(a)(1) and (n)
Read the rule (FTC Act section 5, 15 U.S.C. § 45(a)(1) and (n))Sources
The law
- 15 U.S.C. § 45, FTC Act section 5 on unfair or deceptive acts or practices (United States Code, 2023 edition, govinfo)
- 15 U.S.C. § 45, FTC Act section 5 (Cornell Legal Information Institute)
Guidance
- FTC, Start with Security: A Guide for Business
- FTC, Protecting Personal Information: A Guide for Business (October 2016; TLS for data in transit)
- NIST SP 800-52 Rev. 2, Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations
Decisions and cases
- U.S. Court of Appeals for the Third Circuit, FTC v. Wyndham Worldwide Corp., No. 14-3514, opinion of 24 August 2015
- FTC, Third Circuit rules in FTC v. Wyndham case, 25 August 2015
- FTC, FTC Finalizes Order with GoDaddy over Data Security Failures, 21 May 2025
- FTC, Fandango and Credit Karma settle FTC charges over failing to securely transmit sensitive information, 28 March 2014
Last checked against the source:
For information only. Not legal advice.
