---
id: CP-206
slug: https-tls-browser-padlock
lang: en
title: HTTPS and the browser padlock
description: What HTTPS and TLS really protect, why the padlock does not prove a site is honest, and how to read a web address.
canonical_url: https://startbrain.io/cyberpedia/en/articles/https-tls-browser-padlock/
markdown_url: https://startbrain.io/cyberpedia/en/articles/https-tls-browser-padlock.md
publisher: Brain (https://startbrain.io)
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
cite_as: Brain, "HTTPS and the browser padlock", Cyberpedia, 2026. https://startbrain.io/cyberpedia/en/articles/https-tls-browser-padlock/ (CC BY 4.0)
wing: 3
theme: understand_cyberspace
reflex: cr-060
schema: G2
updated: "2026-11-10"
translations:
  en: https://startbrain.io/cyberpedia/en/articles/https-tls-browser-padlock/
  fr: https://startbrain.io/cyberpedia/fr/articles/https-tls-cadenas-navigateur/
  de: https://startbrain.io/cyberpedia/de/articles/https-tls-schloss-browser/
  es: https://startbrain.io/cyberpedia/es/articles/https-tls-candado-navegador/
  it: https://startbrain.io/cyberpedia/it/articles/https-tls-lucchetto-browser/
  nl: https://startbrain.io/cyberpedia/nl/articles/https-tls-hangslot-browser/
  pl: https://startbrain.io/cyberpedia/pl/articles/https-tls-klodka-przegladarka/
  pt: https://startbrain.io/cyberpedia/pt/articles/https-tls-cadeado-navegador/
  ja: https://startbrain.io/cyberpedia/ja/articles/https-tls-kagi-maaku-burauza/
sources:
  - "n": 1
    title: Transport Layer Security - OWASP Cheat Sheet Series
    publisher: OWASP
    url: https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html
    accessed: "2026-11-10"
  - "n": 2
    title: TLS/SSL overview (Schannel SSP)
    publisher: Microsoft
    url: https://learn.microsoft.com/en-us/windows-server/security/tls/tls-ssl-schannel-ssp-overview
    accessed: "2026-11-10"
  - "n": 3
    title: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations
    publisher: NIST
    url: https://csrc.nist.gov/pubs/sp/800/52/r2/final
    accessed: "2026-11-10"
  - "n": 4
    title: Adversary-in-the-Middle, Technique T1557 - Enterprise | MITRE ATT&CK®
    publisher: MITRE ATT&CK
    url: https://attack.mitre.org/techniques/T1557/
    accessed: "2026-11-10"
  - "n": 5
    title: "Phishing: Spearphishing Link, Sub-technique T1566.002 - Enterprise | MITRE ATT&CK®"
    publisher: MITRE ATT&CK
    url: https://attack.mitre.org/techniques/T1566/002/
    accessed: "2026-11-10"
  - "n": 6
    title: Recognize and Report Phishing | CISA
    publisher: CISA
    url: https://www.cisa.gov/secure-our-world/recognize-and-report-phishing
    accessed: "2026-11-10"
  - "n": 7
    title: "Phishing scams: how to spot and report them"
    publisher: NCSC (UK)
    url: https://www.ncsc.gov.uk/collection/phishing-scams
    published: "2021-11-26"
    accessed: "2026-11-10"
  - "n": 8
    title: "Phishing attacks: defending your organisation"
    publisher: NCSC (UK)
    url: https://www.ncsc.gov.uk/guidance/phishing
    published: "2018-02-05"
    accessed: "2026-11-10"
---

# HTTPS and the browser padlock

When a site's address starts with https and the browser shows a padlock, the connection is encrypted. Many employees conclude that the site is safe. That conclusion is wrong: encryption protects the journey of the data, and says nothing about the honesty of whoever runs the site.

This page explains what HTTPS and TLS protect, what the certificate proves, and what it leaves out. It then gives the habits to keep for reading an address and reacting to an alert.

## In 30 seconds

- Where it happens: on every visit to a website, and in links received in messages.
- What the attacker wants: to make you believe a padlock is a certificate of good conduct, so that you enter a password or data on their site.
- The reflex: read the full address, do not rely on the padlock alone, never click past a certificate alert, and report the suspicious site.
- If it is already done: tell the IT department without delay, explaining what you entered.

## Straight answers

### What do HTTPS and TLS mean?

HTTPS is the web protected by TLS (Transport Layer Security). SSL is the old name of the protocol, and the two terms are often used interchangeably [1]. SSL versions 2 and 3 have serious cryptographic weaknesses and must no longer be used [1]. TLS has had versions 1.0, 1.1, 1.2 and 1.3 [1].

### What does TLS protect?

According to the OWASP cheat sheet, TLS provides three things [1]. Confidentiality: an attacker cannot read the content of the exchanges. Integrity: they cannot modify or replay intercepted requests. Authentication: the client can confirm that it is connected to the legitimate server [1]. OWASP specifies that the client's identity, for its part, is not verified without a client certificate [1].

### Does the padlock prove that the site is honest?

No. The certificate links the server to a domain name, not to an intention. All publicly issued certificates must at minimum be validated on the domain (DV): the authority checks that the applicant controls the requested name, for example through a DNS exchange or an email to an official address [1]. The Let's Encrypt authority issues this type of certificate for free, and all major browsers recognize it [1]. What is proven is control of the name, not the good faith of its holder.

### Does a more expensive certificate change anything?

Not for the employee. Extended validation (EV) certificates used to display the company name or a green icon in the address bar. Since 2019, no major browser displays them this way, because they see no additional protection in them [1]. OWASP judges them equivalent to basic certificates in terms of security [1].

### Where is TLS used, outside the browser?

Microsoft cites transactions on an online shopping site, remote access, SQL access and email [2]. The protocol is used to authenticate servers and then to encrypt messages between the authenticated parties [2].

## How it works

A certificate associates a key with a domain name. For users to trust it, it must be signed by a certification authority recognized by systems and browsers [1]. The certificate's domain name must match the name of the server presenting it [1]. A certificate error can appear when the application's certificate does not match the one the host expects [4].

As for versions, OWASP states that web applications must use TLS 1.3 by default and may accept TLS 1.2 for compatibility [1]. TLS 1.0 and 1.1 are officially deprecated by RFC 8996 (March 2021) and removed from all major browsers [1]. NIST, in its August 2019 publication, for its part requires that US government servers and clients support TLS 1.2 and, by 1 January 2024 at the latest, TLS 1.3 [3].

On Windows, no configuration step is needed to enable TLS or Schannel, the component that implements it [2]. The employee has nothing to set up: their role is to read carefully what the browser shows them.

## What you do

- Read the full address before entering anything, not just the beginning or the padlock. CISA gives "amazan.com" as an example of an incorrect address [6].
- Be wary of addresses that imitate a known site with special characters. MITRE describes these "IDN homograph attack" cases that make a harmless-looking link resemble a legitimate site [5].
- Do not click the link in a message that looks doubtful to you. Look for the site in the browser or type the address yourself if you know it [6].
- Faced with a certificate alert, stop. MITRE recommends training users to be wary of certificate errors, because an attacker can use their own certificate to intercept HTTPS traffic [4]. An error can appear when the application's certificate does not match the one the host expects [4].
- Report the suspicious site. The UK NCSC can investigate fraudulent sites and have them removed [7]. In the company, use the reporting channel provided: the NCSC recommends that it be clear, simple and fast [8].

## Pitfalls

People first believe that "secure" means "trustworthy". The padlock describes the connection, not the site. A fraudster's site can have a perfectly valid encrypted connection, since basic validation only covers control of the domain [1].

Another pitfall: reading the address too quickly. MITRE also notes that some URLs are scrambled by exploiting quirks of their syntax, such as the text before an "@" being ignored [5]. The example given by MITRE, neutralized here, illustrates the principle:

```text
Illustration: scrambled address (neutralized)
hxxp://exemple[.]invalid@1157586937
[the text before the @ is ignored, the real destination is what follows]
```

Another pitfall: clicking "continue anyway" on a certificate alert. This message signals that the server is not presenting the expected certificate, which can happen during an interception [4]. An attacker in an intermediary position can also try to force the negotiation of a weaker TLS version [4].

Another pitfall: fear of reporting. The NCSC recommends not blaming users for their mistakes, because those who fear sanctions do not report, or report too late [8]. Reporting a click that has already happened also provides useful information about ongoing attacks [8].

Finally, CISA notes that bad spelling used to be a common sign of phishing, but that in the era of artificial intelligence some phishing emails now have perfect grammar and spelling [6]. Other signs: an urgent tone, a request for personal or financial information, shortened addresses from a dubious source [6].

## Sources

1. OWASP, "Transport Layer Security - OWASP Cheat Sheet Series". https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html (accessed 10 November 2026)
2. Microsoft, "TLS/SSL overview (Schannel SSP)". https://learn.microsoft.com/en-us/windows-server/security/tls/tls-ssl-schannel-ssp-overview (accessed 10 November 2026)
3. NIST, "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations". https://csrc.nist.gov/pubs/sp/800/52/r2/final (accessed 10 November 2026)
4. MITRE ATT&CK, "Adversary-in-the-Middle, Technique T1557 - Enterprise | MITRE ATT&CK®". https://attack.mitre.org/techniques/T1557/ (accessed 10 November 2026)
5. MITRE ATT&CK, "Phishing: Spearphishing Link, Sub-technique T1566.002 - Enterprise | MITRE ATT&CK®". https://attack.mitre.org/techniques/T1566/002/ (accessed 10 November 2026)
6. CISA, "Recognize and Report Phishing | CISA". https://www.cisa.gov/secure-our-world/recognize-and-report-phishing (accessed 10 November 2026)
7. NCSC (UK), "Phishing scams: how to spot and report them", 26 November 2021. https://www.ncsc.gov.uk/collection/phishing-scams (accessed 10 November 2026)
8. NCSC (UK), "Phishing attacks: defending your organisation", 5 February 2018. https://www.ncsc.gov.uk/guidance/phishing (accessed 10 November 2026)

---

Original source: Cyberpedia, the public cybersecurity and AI encyclopedia published by Brain. Canonical version: https://startbrain.io/cyberpedia/en/articles/https-tls-browser-padlock/
You may reuse this text freely under the CC BY 4.0 license (https://creativecommons.org/licenses/by/4.0/), provided you credit "Brain, Cyberpedia" with a link to the canonical URL above.
