Version history for TLS/SSL support in web browsers tracks the implementation of Transport Layer Security protocol versions in major web browsers.
TLS/SSL support history of web browsers| Browseror OS API | Version | Platforms | SSL protocols | TLS protocols | Certificate support | Vulnerability | Protocol selection by user | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV | SHA-2 | ECDSA | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | |||||
| Google Chrome(Chrome for Android) | 1–9 | Windows (10+)macOS (11+)LinuxAndroid (8.0+)iOS (16+)ChromeOS | Disabled by default | Yes | Yes | No | No | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Vulnerable(HTTPS) | Vulnerable | Vulnerable | Vulnerable(except Windows) | Vulnerable | Yes | |
| 10–20 | No | Yes | Yes | No | No | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Vulnerable(HTTPS/SPDY) | Vulnerable | Vulnerable | Vulnerable(except Windows) | Vulnerable | Yes | |||
| 21 | No | Yes | Yes | No | No | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Mitigated | Vulnerable | Vulnerable | Vulnerable(except Windows) | Vulnerable | Yes | |||
| 22–29 | No | Yes | Yes | Yes | No | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Mitigated | Vulnerable | Vulnerable | Vulnerable(except Windows) | Vulnerable | Temporary | |||
| 30–32 | No | Yes | Yes | Yes | Yes | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Mitigated | Vulnerable | Vulnerable | Vulnerable(except Windows) | Vulnerable | Temporary | |||
| 33–37 | No | Yes | Yes | Yes | Yes | No | Yes(only desktop) | Requires SHA-2 compatible OS | Needs ECC compatible OS | Not affected | Mitigated | Partly mitigated | Lowest priority | Vulnerable(except Windows) | Vulnerable | Temporary | |||
| 38, 39 | No | Yes | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Partly mitigated | Lowest priority | Vulnerable(except Windows) | Vulnerable | Temporary | |||
| 40 | No | Disabled by default | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Mitigated | Lowest priority | Vulnerable(except Windows) | Vulnerable | Yes | |||
| 41, 42 | No | Disabled by default | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Mitigated | Lowest priority | Mitigated | Vulnerable | Yes | |||
| 43 | No | Disabled by default | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Mitigated | Only as fallback | Mitigated | Vulnerable | Yes | |||
| 44–47 | No | No | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Not affected | Only as fallback | Mitigated | Mitigated | Temporary | |||
| 48, 49 | No | No | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Needs ECC compatible OS | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 50–53 | No | No | Yes | Yes | Yes | No | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 54–66 | No | No | Yes | Yes | Yes | Disabled by default(draft version) | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 67–69 | No | No | Yes | Yes | Yes | Yes(draft version) | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 70–83 | No | No | Yes | Yes | Yes | Yes | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 84–90 | No | No | Warn by default | Warn by default | Yes | Yes | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| 91–135 | No | No | No | No | Yes | Yes | Yes(only desktop) | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Mitigated | Mitigated | Temporary | |||
| ESC 136 | 137 | ||||||||||||||||||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Microsoft Edge(Chromium-based)OS-independent | 79–83 | Windows (10+)macOS (11+)Linux Android (8.0+)iOS (16+) | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | Yes | |
| 84–90 | No | No | Warn by default | Warn by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | Yes | |||
| 91-135 | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | Yes | |||
| ESC 136 | 137 | ||||||||||||||||||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Mozilla Firefox(Firefox for mobile) | 1.0, 1.5 | Windows (10+)macOS (10.15+)LinuxAndroid (5.0+)iOS (15+)Firefox OSMaemoESR 115 only for:Windows (7–8.1)macOS (10.12–10.14)ESR 128+ only for:Windows (10+)macOS (10.15+)Linux | Yes | Yes | Yes | No | No | No | No | Yes | No | Not affected | Not affected | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |
| 2 | Disabled by default | Yes | Yes | No | No | No | No | Yes | Yes | Not affected | Not affected | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 3–7 | Disabled by default | Yes | Yes | No | No | No | Yes | Yes | Yes | Not affected | Not affected | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 8–10ESR 10 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Not affected | Not affected | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 11–14 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Not affected | Vulnerable(SPDY) | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 15–22ESR 17.0–17.0.10 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| ESR 17.0.11 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Lowest priority | Not affected | Vulnerable | Yes | |||
| 23 | No | Yes | Yes | Disabled by default | No | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 24, 25.0.0ESR 24.0–24.1.0 | No | Yes | Yes | Disabled by default | Disabled by default | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Vulnerable | Not affected | Vulnerable | Yes | |||
| 25.0.1, 26ESR 24.1.1–24.8.1 | No | Yes | Yes | Disabled by default | Disabled by default | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Lowest priority | Not affected | Vulnerable | Yes | |||
| 27–33ESR 31.0–31.2.0 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Vulnerable | Lowest priority | Not affected | Vulnerable | Yes | |||
| 34, 35ESR 31.3.0–31.7.0 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Mitigated | Lowest priority | Not affected | Vulnerable | Yes | |||
| ESR 31.8.0 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Mitigated | Lowest priority | Not affected | Mitigated | Yes | |||
| 36–38ESR 38.0–38.0.1 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Mitigated | Only as fallback | Not affected | Vulnerable | Yes | |||
| ESR 38.1.0–38.8.0 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Mitigated | Only as fallback | Not affected | Mitigated | Yes | |||
| 39–43 | No | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Only as fallback | Not affected | Mitigated | Yes | |||
| 44–48ESR 45 | No | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Not affected | Mitigated | Yes | |||
| 49–59ESR 52 | No | No | Yes | Yes | Yes | Disabled by default(draft version) | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Not affected | Mitigated | Yes | |||
| 60–62ESR 60 | No | No | Yes | Yes | Yes | Yes(draft version) | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Not affected | Mitigated | Yes | |||
| 63–77ESR 68 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Not affected | Mitigated | Yes | |||
| 78–138ESR 78–115.23ESR 128.0–128.10 | No | No | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Not affected | Mitigated | Not affected | Disabled by default | Not affected | Mitigated | Yes | |||
| ESR 115.24 | |||||||||||||||||||
| ESR 128.11 | |||||||||||||||||||
| 139 | |||||||||||||||||||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Microsoft Internet Explorer(1–10)Windows Schannel | 1.x | Windows 3.1, 95, NT,Mac OS 7, 8 | No SSL/TLS support | ||||||||||||||||
| 2 | Yes | No | No | No | No | No | No | No | No | No SSL 3.0 or TLS support | Vulnerable | Vulnerable | Vulnerable | — | |||||
| 3 | Yes | Yes | No | No | No | No | No | No | No | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | ? | |||
| 4, 5, 6 | Windows 3.1, 95, 98, NT, 2000Mac OS 7.1, 8, X,Solaris, HP-UX | Yes | Yes | Disabled by default | No | No | No | No | No | No | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | Yes | ||
| 6 | Windows XP | Yes | Yes | Disabled by default | No | No | No | No | Yes (Since SP3) | No | Mitigated | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | Yes | ||
| 7, 8 | Disabled by default | Yes | Yes | No | No | No | Yes | Yes (Since SP3) | No | Mitigated | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | Yes | |||
| 6 | Server 2003 | Yes | Yes | Disabled by default | No | No | No | No | Yes(KB938397+KB968730) | No | Mitigated | Not affected | Vulnerable | Vulnerable | Mitigated | Mitigated | Yes | ||
| 7, 8 | Disabled by default | Yes | Yes | No | No | No | Yes | Yes(KB938397+KB968730) | No | Mitigated | Not affected | Vulnerable | Vulnerable | Mitigated | Mitigated | Yes | |||
| 7, 8, 9 | Windows Vista | Disabled by default | Yes | Yes | No | No | No | Yes | Yes | Yes | Mitigated | Not affected | Vulnerable | Vulnerable | Mitigated | Mitigated | Yes | ||
| 7, 8, 9 | Server 2008 | Disabled by default | Yes | Yes | Disabled by default(KB4019276) | Disabled by default(KB4019276) | No | Yes | Yes | Yes | Mitigated | Not affected | Vulnerable | Vulnerable | Mitigated | Mitigated | Yes | ||
| 8, 9, 10 | 7, 8Server 2008 R2Server 2012 | Disabled by default | Yes | Yes | Disabled by default | Disabled by default | No | Yes | Yes | Yes | Mitigated | Not affected | Vulnerable | Lowest priority | Mitigated | Mitigated | Yes | ||
| Internet Explorer 11Windows Schannel | 11 | 7, 8.1Server 2008 R2Server 2012Server 2012 R2 | Disabled by default | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Microsoft Edge(12–18)(EdgeHTML-based)Client onlyInternet Explorer 11Windows Schannel | 11 | 12–13 | Windows 10 1507–1511 | Disabled by default | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes |
| 11 | 14–18(client only) | Windows 10 1607–2004Windows Server (SAC)1709–2004 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |
| Internet Explorer 11Windows Schannel | 11 | Windows 10 20H2–21H2Windows Server (SAC)20H2 | No | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |
| Windows 10 22H2 | |||||||||||||||||||
| Windows Schannel | Windows 11 21H2 | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | ||
| Windows 11 22H2(Home/Pro) | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows 11 22H2(Ent/Edu) | |||||||||||||||||||
| Windows 11 23H2(Home/Pro) | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows 11 23H2(Ent/Edu) | |||||||||||||||||||
| Windows 11 24H2 | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Internet Explorer 11LTSB/LTSCWindows SchannelLTSB/LTSC | 11 | Windows 10LTSB 2015 (1507) | Disabled by default | Yes | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |
| Windows 10LTSB 2016 (1607) | No | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows Server 2016(LTSB/1607) | No | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows 10LTSC 2019 (1809)Windows Server 2019(LTSC/1809) | No | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows 10LTSC 2021 (21H2) | No | Disabled by default | Disabled by default | Disabled by default | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows Server 2022(LTSC/21H2) | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Windows SchannelLTSC | Windows 11LTSC 2024 (24H2) | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | ||
| Windows Server 2025(LTSC/24H2) | No | Disabled by default | Disabled by default | Disabled by default | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | Yes | |||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Microsoft Internet Explorer Mobile | 7–9 | Windows Phone 7, 7.5, 7.8 | Disabled by default | Yes | Yes | No | No | No | No | Yes | Yes | ? | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | Only with 3rd party tools | |
| 10 | Windows Phone 8 | Disabled by default | Yes | Yes | Disabled by default | Disabled by default | No | No | Yes | Yes | Mitigated | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | Only with 3rd party tools | ||
| 11 | Windows Phone 8.1 | Disabled by default | Yes | Yes | Yes | Yes | No | No | Yes | Yes | Mitigated | Not affected | Vulnerable | Only as fallback | Vulnerable | Vulnerable | Only with 3rd party tools | ||
| Microsoft Edge(13–15)(EdgeHTML-based) | 13 | Windows 10 Mobile 1511 | Disabled by default | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | No | |
| 14, 15 | Windows 10 Mobile1607–1709 | No | Disabled by default | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Disabled by default | Mitigated | Mitigated | No | ||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Apple Safari | 1 | Mac OS X 10.2, 10.3 | No | Yes | Yes | No | No | No | No | No | No | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | |
| 2–5 | Mac OS X 10.4, 10.5, Win XP | No | Yes | Yes | No | No | No | Yes (Since v3.2) | No | No | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 3–5 | Vista, Win 7 | No | Yes | Yes | No | No | No | Yes (Since v3.2) | No | Yes | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 4–6 | Mac OS X 10.6, 10.7 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 6 | OS X 10.8 | No | Yes | Yes | No | No | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Vulnerable | Mitigated | Vulnerable | No | ||
| 7, 9 | OS X 10.9 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Vulnerable | Mitigated | Vulnerable | No | ||
| 8–10 | OS X 10.10 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Lowest priority | Mitigated | Mitigated | No | ||
| 9–11 | OS X 10.11 | No | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Lowest priority | Mitigated | Mitigated | No | ||
| 10–15 | macOS10.12, 10.13,10.14, 10.15 | No | No | Yes | Yes | Yes | Yes (Since macOS 10.14.4) | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| 14–17 | macOS 11, 12 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| 16, 17 | 18 | macOS 13 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | |
| 17 | 18 | macOS 14 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | |
| 18 | macOS 15 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| 26 | macOS 26 | No | No | ? | ? | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Apple Safari(mobile) | 3 | iPhone OS 1, 2 | No | Yes | Yes | No | No | No | No | No | No | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | |
| 4, 5 | iPhone OS 3, iOS 4 | No | Yes | Yes | No | No | No | Yes | Yes | Yes (Since iOS 4) | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 5, 6 | iOS 5, 6 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Vulnerable | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 7 | iOS 7 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| 8 | iOS 8 | No | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Mitigated | Lowest priority | Mitigated | Mitigated | No | ||
| 9 | iOS 9 | No | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Lowest priority | Mitigated | Mitigated | No | ||
| 10, 11 | iOS 10, 11 | No | No | Yes | Yes | Yes | No | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| 12 | iOSiOS 12 | No | No | Yes | Yes | Yes | Yes (Since iOS 12.2) | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| 13–16 | iOS13, 14, 15, 16 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| iPadOS13, 14, 15, 16 | |||||||||||||||||||
| 17 | iOS 17 | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| iPadOS 17 | |||||||||||||||||||
| 18 | iOS 18 | No | No | ? | ? | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| iPadOS 18 | |||||||||||||||||||
| 26 | iOS 26 | No | No | ? | ? | Yes | Yes | Yes | Yes | Yes | Mitigated | Not affected | Not affected | Disabled by default | Mitigated | Mitigated | No | ||
| iPadOS 26 | |||||||||||||||||||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV | SHA-2 | ECDSA | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Google Android OS | Android 1.0–4.0.4 | No | Yes | Yes | No | No | No | ? | Yes | Yes (Since 3.0) | ? | ? | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | ||
| Android 4.1–4.4.4 | No | Yes | Yes | Disabled by default | Disabled by default | No | ? | Yes | Yes | ? | ? | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | |||
| Android 5.0–5.0.2 | No | Yes | Yes | Yes | Yes | No | ? | Yes | Yes | ? | ? | Vulnerable | Vulnerable | Vulnerable | Vulnerable | No | |||
| Android 5.1–5.1.1 | No | Disabled by default | Yes | Yes | Yes | No | ? | Yes | Yes | ? | ? | Not affected | Only as fallback | Mitigated | Mitigated | No | |||
| Android 6.0–7.1.2 | No | Disabled by default | Yes | Yes | Yes | No | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 8.0–9 | No | No | Yes | Yes | Yes | No | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 10–12L | No | No | Yes | Yes | Yes | Yes | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 13 | No | No | Yes | Yes | Yes | Yes | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 14 | No | No | Yes | Yes | Yes | Yes | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 15 | No | No | ? | ? | Yes | Yes | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Android 16 | No | No | ? | ? | Yes | Yes | ? | Yes | Yes | ? | ? | Not affected | Disabled by default | Mitigated | Mitigated | No | |||
| Browseror OS API | Version | Platforms | SSL 2.0 (insecure) | SSL 3.0 (insecure) | TLS 1.0 (deprecated) | TLS 1.1 (deprecated) | TLS 1.2 | TLS 1.3 | EV certificate | SHA-2 certificate | ECDSA certificate | BEAST | CRIME | POODLE (SSLv3) | RC4 | FREAK | Logjam | Protocol selection by user | |
| Color or Note | Significance | |
|---|---|---|
| Browser version | Platform | |
| Browser version | Operating system | Future release; under development |
| Browser version | Operating system | Current latest release |
| Browser version | Operating system | Former release; still supported |
| Browser version | Operating system | Former release; long-term support still active, but will end in less than 12 months |
| Browser version | Operating system | Former release; no longer supported |
| — | Operating system | Mixed/Unspecified |
| Operating system (Version+) | Minimum required operating system version (for supported versions of the browser) | |
| Operating system | No longer supported for this operating system | |
References
Note actual security depends on other factors such as negotiated cipher, encryption strength, etc. (see § Cipher table). ↩
Whether a user or administrator can choose the protocols to be used or not. If yes, several attacks such as BEAST (vulnerable in SSL 3.0 and TLS 1.0) or POODLE (vulnerable in SSL 3.0) can be avoided. ↩
Whether EV SSL and DV SSL (normal SSL) can be distinguished by indicators (green lock icon, green address bar, etc.) or not. ↩
"What browsers support Extended Validation (EV) and display an EV indicator?". Symantec. Archived from the original on 2015-12-31. Retrieved 2014-07-28. https://web.archive.org/web/20151231171309/https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=SO10090&actp=search&viewlocale=en_US&searchid=1406590748892 ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
e.g. 1/n-1 record splitting. ↩
e.g. Disabling header compression in HTTPS/SPDY. /wiki/HTTPS ↩
Complete mitigations; disabling SSL 3.0 itself, "anti-POODLE record splitting". "Anti-POODLE record splitting" is effective only with client-side implementation and valid according to the SSL 3.0 specification, however, it may also cause compatibility issues due to problems in server-side implementations. Partial mitigations; disabling fallback to SSL 3.0, TLS_FALLBACK_SCSV, disabling cipher suites with CBC mode of operation. If the server also supports TLS_FALLBACK_SCSV, the POODLE attack will fail against this combination of server and browser, but connections where the server does not support TLS_FALLBACK_SCSV and does support SSL 3.0 will still be vulnerable. If disabling cipher suites with CBC mode of operation in SSL 3.0, only cipher suites with RC4 are available, RC4 attacks become easier. When disabling SSL 3.0 manually, POODLE attack will fail. /wiki/Block_cipher_mode_of_operation#Cipher-block_chaining_(CBC) ↩
Complete mitigation; disabling cipher suites with RC4. Partial mitigations to keeping compatibility with old systems; setting the priority of RC4 to lower. ↩
"Tracking the FREAK Attack". Archived from the original on 2015-03-06. Retrieved 2015-03-08. https://freakattack.com ↩
"FREAK: Factoring RSA Export Keys". Archived from the original on 2015-03-11. Retrieved 2015-03-08. https://www.smacktls.com/#freak ↩
Google Chrome (and Chromium) supports TLS 1.0, and TLS 1.1 from version 22 (it was added, then dropped from version 21). TLS 1.2 support had been added, then dropped from Chrome 29.[6][7][8] /wiki/Google_Chrome ↩
Uses the TLS implementation provided by BoringSSL for Android, OS X, and Windows[9] or by NSS for Linux. Google is switching the TLS library used in Chrome to BoringSSL from NSS completely. /wiki/BoringSSL ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
"Chrome Stable Release". Chrome Releases. 2011-10-25. Archived from the original on 2015-02-20. Retrieved 2015-02-01. http://googlechromereleases.blogspot.jp/2011/10/chrome-stable-release.html ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"SVN revision log on Chrome 10.0.648.127 release". Archived from the original on 2014-06-19. Retrieved 2014-06-19. https://archive.today/20140619142454/http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&range=72316:67679&mode=html ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
"ImperialViolet – CRIME". 2012-09-22. Archived from the original on 2015-01-10. Retrieved 2014-10-18. https://www.imperialviolet.org/2012/09/21/crime.html ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"SSL/TLS Overview". 2008-08-06. Archived from the original on 2013-07-03. Retrieved 2013-03-29. https://sites.google.com/site/tlsssloverview/ssl-v-tls/tls-versions-and-browser-compatability ↩
"SSL/TLS Overview". 2008-08-06. Archived from the original on 2013-07-03. Retrieved 2013-03-29. https://sites.google.com/site/tlsssloverview/ssl-v-tls/tls-versions-and-browser-compatability ↩
"Chromium Issue 90392". 2008-08-06. Archived from the original on 2013-08-03. Retrieved 2013-06-28. https://code.google.com/p/chromium/issues/detail?id=90392 ↩
"Issue 23503030 Merge 219882". 2013-09-03. Archived from the original on 2014-02-26. Retrieved 2013-09-19. https://codereview.chromium.org/23503030 ↩
"Issue 278370: Unable to submit client certificates over TLS 1.2 from Windows". 2013-08-23. Archived from the original on 2013-10-05. Retrieved 2013-10-03. https://code.google.com/p/chromium/issues/detail?id=278370 ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"Chromium Issue 90392". 2008-08-06. Archived from the original on 2013-08-03. Retrieved 2013-06-28. https://code.google.com/p/chromium/issues/detail?id=90392 ↩
"Issue 23503030 Merge 219882". 2013-09-03. Archived from the original on 2014-02-26. Retrieved 2013-09-19. https://codereview.chromium.org/23503030 ↩
"Issue 278370: Unable to submit client certificates over TLS 1.2 from Windows". 2013-08-23. Archived from the original on 2013-10-05. Retrieved 2013-10-03. https://code.google.com/p/chromium/issues/detail?id=278370 ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
TLS_FALLBACK_SCSV is implemented.[17] Fallback to SSL 3.0 is disabled since version 39.[18] ↩
"Stable Channel Update". Mozilla Developer Network. 2014-02-20. Archived from the original on 2014-10-24. Retrieved 2014-11-14. http://googlechromereleases.blogspot.com/2014/02/stable-channel-update_20.html ↩
"Changelog for Chrome 33.0.1750.117". Google. Archived from the original on 2014-01-16. Retrieved 2014-11-14. https://archive.today/20140116153037/http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&range=232870:241107&mode=html ↩
"Issue 318442: Update to NSS 3.15.3 and NSPR 4.10.2". Archived from the original on 2015-03-15. Retrieved 2014-11-14. https://code.google.com/p/chromium/issues/detail?id=318442 ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"An update on SSLv3 in Chrome". Security-dev. 2014-10-31. Retrieved 2014-11-04. https://groups.google.com/a/chromium.org/forum/#!topic/security-dev/Vnhy9aKM_l4 ↩
"Issue 693963003: Add minimum TLS version control to about:flags and Finch gate it. – Code Review". Archived from the original on 2015-04-16. Retrieved 2015-01-22. https://codereview.chromium.org/693963003 ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
In addition to TLS_FALLBACK_SCSV and disabling a fallback to SSL 3.0, SSL 3.0 itself is disabled by default.[18] ↩
Configure the minimum version of enabling protocols via chrome://flags[22] (the maximum version can be configured with command-line option). ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
Configure the minimum version of enabling protocols via chrome://flags[22] (the maximum version can be configured with command-line option). ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Issue 375342: Drop RC4 Support". Archived from the original on 2015-09-12. Retrieved 2015-05-22. https://code.google.com/p/chromium/issues/detail?id=375342 ↩
Configure the minimum version of enabling protocols via chrome://flags[22] (the maximum version can be configured with command-line option). ↩
"Issue 436391: Add info on end of life of SSLVersionFallbackMin & SSLVersionMin policy in documentation". Archived from the original on 2015-04-18. Retrieved 2015-04-19. https://code.google.com/p/chromium/issues/detail?id=436391 ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Issue 490240: Increase minimum DH size to 1024 bits (tracking bug)". Archived from the original on 2015-09-12. Retrieved 2015-05-29. https://code.google.com/p/chromium/issues/detail?id=490240 ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
"Chrome Enterprise release notes - Google Chrome Enterprise Help". https://support.google.com/chrome/a/answer/7679408?hl=en ↩
"Chrome Enterprise release notes - Google Chrome Enterprise Help". https://support.google.com/chrome/a/answer/7679408?hl=en ↩
All RC4 cipher suites are disabled by default. ↩
"Intent to deprecate: RC4". Retrieved 2015-12-21. https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/kVfCywocUO8/2BW3INFdDwAJ ↩
"An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21. https://googleonlinesecurity.blogspot.com/2015/12/an-update-on-sha-1-certificates-in.html ↩
configure the maximum and the minimum version of enabling protocols with command-line option. /wiki/Command-line ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"Microsoft Edge Browser Policy Documentation | Microsoft Docs". Docs.microsoft.com. 2021-10-15. Retrieved 2022-02-15. https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#sslversionmin ↩
"Microsoft Edge Browser Policy Documentation | Microsoft Docs". Docs.microsoft.com. 2021-10-15. Retrieved 2022-02-15. https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#sslversionmin ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Uses the TLS implementation provided by NSS. As of Firefox 22, Firefox supports only TLS 1.0 despite the bundled NSS supporting TLS 1.1. Since Firefox 23, TLS 1.1 can be enabled, but was not enabled by default due to issues. Firefox 24 has TLS 1.2 support disabled by default. TLS 1.1 and TLS 1.2 have been enabled by default in Firefox 27 release. /wiki/Network_Security_Services ↩
"Security in Firefox 2". 2008-08-06. Archived from the original on 2014-07-14. Retrieved 2009-03-31. https://developer.mozilla.org/en-US/Firefox/Releases/2/Security_changes ↩
"Security in Firefox 2". 2008-08-06. Archived from the original on 2014-07-14. Retrieved 2009-03-31. https://developer.mozilla.org/en-US/Firefox/Releases/2/Security_changes ↩
"Security in Firefox 2". 2008-08-06. Archived from the original on 2014-07-14. Retrieved 2009-03-31. https://developer.mozilla.org/en-US/Firefox/Releases/2/Security_changes ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"Attack against TLS-protected communications". Mozilla Security Blog. Mozilla. 2011-09-27. Archived from the original on 2015-03-04. Retrieved 2015-02-01. https://blog.mozilla.org/security/2011/09/27/attack-against-tls-protected-communications ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"Security in Firefox 2". 2008-08-06. Archived from the original on 2014-07-14. Retrieved 2009-03-31. https://developer.mozilla.org/en-US/Firefox/Releases/2/Security_changes ↩
"Introduction to SSL". MDN. Archived from the original on 2014-07-14. Retrieved 2014-06-19. https://developer.mozilla.org/en-US/docs/Introduction_to_SSL ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"Introduction to SSL". MDN. Archived from the original on 2014-07-14. Retrieved 2014-06-19. https://developer.mozilla.org/en-US/docs/Introduction_to_SSL ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"ImperialViolet – CRIME". 2012-09-22. Archived from the original on 2015-01-10. Retrieved 2014-10-18. https://www.imperialviolet.org/2012/09/21/crime.html ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"NSS 3.15.3 Release Notes". Mozilla Developer Network. Mozilla. Archived from the original on 2014-06-05. Retrieved 2014-07-13. https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.15.3_release_notes ↩
"MFSA 2013-103: Miscellaneous Network Security Services (NSS) vulnerabilities". Mozilla. Archived from the original on 2014-07-14. Retrieved 2014-07-13. https://www.mozilla.org/security/announce/2013/mfsa2013-103.html ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"Bug 565047 – (RFC4346) Implement TLS 1.1 (RFC 4346)". Retrieved 2013-10-29. https://bugzilla.mozilla.org/show_bug.cgi?id=565047 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Bug 480514 – Implement support for TLS 1.2 (RFC 5246)". Retrieved 2013-10-29. https://bugzilla.mozilla.org/show_bug.cgi?id=480514 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"NSS 3.15.3 Release Notes". Mozilla Developer Network. Mozilla. Archived from the original on 2014-06-05. Retrieved 2014-07-13. https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.15.3_release_notes ↩
"MFSA 2013-103: Miscellaneous Network Security Services (NSS) vulnerabilities". Mozilla. Archived from the original on 2014-07-14. Retrieved 2014-07-13. https://www.mozilla.org/security/announce/2013/mfsa2013-103.html ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Bug 733647 – Implement TLS 1.1 (RFC 4346) in Gecko (Firefox, Thunderbird), on by default". Retrieved 2013-12-04. https://bugzilla.mozilla.org/show_bug.cgi?id=733647 ↩
"Firefox Notes – Desktop". 2014-02-04. Archived from the original on 2014-02-07. Retrieved 2014-02-04. https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/27.0/releasenotes ↩
"Bug 861266 – Implement TLS 1.2 (RFC 5246) in Gecko (Firefox, Thunderbird), on by default". Retrieved 2013-11-18. https://bugzilla.mozilla.org/show_bug.cgi?id=861266 ↩
"Firefox Notes – Desktop". 2014-02-04. Archived from the original on 2014-02-07. Retrieved 2014-02-04. https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/27.0/releasenotes ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"The POODLE Attack and the End of SSL 3.0". Mozilla blog. Mozilla. 2014-10-14. Archived from the original on 2014-10-18. Retrieved 2014-10-28. https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0 ↩
"Firefox — Notes (34.0) — Mozilla". mozilla.org. 2014-12-01. Archived from the original on 2015-04-09. Retrieved 2015-04-03. https://www.mozilla.org/en-US/firefox/34.0/releasenotes ↩
SSL 3.0 itself is disabled by default.[40] In addition, fallback to SSL 3.0 is disabled since version 34,[42] and TLS_FALLBACK_SCSV is implemented since 35.0 and ESR 31.3.0.[40][43] ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Bug 1166031 – Update to NSS 3.19.1". bugzilla.mozilla.org. Retrieved 2015-05-29. https://bugzilla.mozilla.org/show_bug.cgi?id=1166031 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Bug 1088915 – Stop offering RC4 in the first handshakes". bugzilla.mozilla.org. Retrieved 2014-11-04. https://bugzilla.mozilla.org/show_bug.cgi?id=1088915 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Bug 1166031 – Update to NSS 3.19.1". bugzilla.mozilla.org. Retrieved 2015-05-29. https://bugzilla.mozilla.org/show_bug.cgi?id=1166031 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Firefox — Notes (39.0) — Mozilla". mozilla.org. 2015-06-30. Archived from the original on 2015-07-03. Retrieved 2015-07-03. https://www.mozilla.org/en-US/firefox/39.0/releasenotes ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Bug 1166031 – Update to NSS 3.19.1". bugzilla.mozilla.org. Retrieved 2015-05-29. https://bugzilla.mozilla.org/show_bug.cgi?id=1166031 ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
All RC4 cipher suites are disabled by default. ↩
"Google, Microsoft, and Mozilla will drop RC4 encryption in Chrome, Edge, IE, and Firefox next year". VentureBeat. 2015-09-01. Archived from the original on 2015-09-05. Retrieved 2015-09-05. https://venturebeat.com/2015/09/01/google-microsoft-and-mozilla-will-drop-rc4-support-in-chrome-edge-ie-and-firefox-next-year ↩
"Intent to ship: RC4 disabled by default in Firefox 44". Archived from the original on 2011-01-22. Retrieved 2015-10-18. https://groups.google.com/forum/#!searchin/mozilla.dev.platform/rc4/mozilla.dev.platform/JIEFcrGhqSM/CIjtpwxoLQAJ ↩
"RC4 is now allowed only on whitelisted sites (Reverted)". Retrieved 2015-11-02. https://www.fxsitecompat.com/en-US/docs/2015/rc4-is-now-allowed-only-on-whitelisted-sites ↩
"Firefox — Notes (44.0) — Mozilla". mozilla.org. 2016-01-26. Archived from the original on 2016-03-04. Retrieved 2016-03-09. https://www.mozilla.org/en-US/firefox/44.0/releasenotes ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Bug 1342082 – Disable TLS 1.3 for FF52 Release". Retrieved 2017-03-29. https://bugzilla.mozilla.org/show_bug.cgi?id=1342082 ↩
All RC4 cipher suites are disabled by default. ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
All RC4 cipher suites are disabled by default. ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
All RC4 cipher suites are disabled by default. ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
"Firefox 78.0, See All New Features, Updates and Fixes". https://www.mozilla.org/en-US/firefox/78.0/releasenotes ↩
"Firefox 78.0, See All New Features, Updates and Fixes". https://www.mozilla.org/en-US/firefox/78.0/releasenotes ↩
All RC4 cipher suites are disabled by default. ↩
Configure the maximum and the minimum version of enabling protocols via about:config. ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
Windows NT 3.1 supports IE 1–2, Windows NT 3.5 supports IE 1–3, Windows NT 3.51 and Windows NT 4.0 supports IE 1–6. /wiki/Windows_NT_3.1 ↩
Windows XP as well as Server 2003 and older support only weak ciphers like Triple DES and RC4 out of the box.[58] The weak ciphers of these Schannel version are not only used for IE, but also for other Microsoft products running on this OS, like Microsoft Office or Windows Update. Only Windows Server 2003 can get a manual update to support AES ciphers by KB948963[59] /wiki/Triple_DES ↩
"What browsers only support SSLv2?". Retrieved 2014-06-19. https://stackoverflow.com/q/881563 ↩
Windows NT 3.1 supports IE 1–2, Windows NT 3.5 supports IE 1–3, Windows NT 3.51 and Windows NT 4.0 supports IE 1–6. /wiki/Windows_NT_3.1 ↩
Windows XP as well as Server 2003 and older support only weak ciphers like Triple DES and RC4 out of the box.[58] The weak ciphers of these Schannel version are not only used for IE, but also for other Microsoft products running on this OS, like Microsoft Office or Windows Update. Only Windows Server 2003 can get a manual update to support AES ciphers by KB948963[59] /wiki/Triple_DES ↩
"What browsers only support SSLv2?". Retrieved 2014-06-19. https://stackoverflow.com/q/881563 ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Windows XP as well as Server 2003 and older support only weak ciphers like Triple DES and RC4 out of the box.[58] The weak ciphers of these Schannel version are not only used for IE, but also for other Microsoft products running on this OS, like Microsoft Office or Windows Update. Only Windows Server 2003 can get a manual update to support AES ciphers by KB948963[59] /wiki/Triple_DES ↩
MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit). ↩
"SHA2 and Windows – Windows PKI blog – Site Home – TechNet Blogs". 2010-09-30. Archived from the original on 2014-07-16. Retrieved 2014-07-29. https://blogs.technet.com/b/pki/archive/2010/09/30/sha2-and-windows.aspx ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29. https://msdn.microsoft.com/en-us/library/bb250503.aspx ↩
"HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29. https://msdn.microsoft.com/en-us/library/bb250503.aspx ↩
MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit). ↩
"SHA2 and Windows – Windows PKI blog – Site Home – TechNet Blogs". 2010-09-30. Archived from the original on 2014-07-16. Retrieved 2014-07-29. https://blogs.technet.com/b/pki/archive/2010/09/30/sha2-and-windows.aspx ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
Windows XP as well as Server 2003 and older support only weak ciphers like Triple DES and RC4 out of the box.[58] The weak ciphers of these Schannel version are not only used for IE, but also for other Microsoft products running on this OS, like Microsoft Office or Windows Update. Only Windows Server 2003 can get a manual update to support AES ciphers by KB948963[59] /wiki/Triple_DES ↩
MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit). ↩
"SHA2 and Windows – Windows PKI blog – Site Home – TechNet Blogs". 2010-09-30. Archived from the original on 2014-07-16. Retrieved 2014-07-29. https://blogs.technet.com/b/pki/archive/2010/09/30/sha2-and-windows.aspx ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29. https://msdn.microsoft.com/en-us/library/bb250503.aspx ↩
"HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29. https://msdn.microsoft.com/en-us/library/bb250503.aspx ↩
MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit). ↩
"SHA2 and Windows – Windows PKI blog – Site Home – TechNet Blogs". 2010-09-30. Archived from the original on 2014-07-16. Retrieved 2014-07-29. https://blogs.technet.com/b/pki/archive/2010/09/30/sha2-and-windows.aspx ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"Update to add support for TLS 1.1 and TLS 1.2 in Windows Server 2008 SP2, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009". Retrieved 2017-07-19. https://support.microsoft.com/kb/4019276 ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
"Update to add support for TLS 1.1 and TLS 1.2 in Windows Server 2008 SP2, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009". Retrieved 2017-07-19. https://support.microsoft.com/kb/4019276 ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
"Windows 7 adds support for TLSv1.1 and TLSv1.2 – IEInternals – Site Home – MSDN Blogs". Archived from the original on 2013-12-26. Retrieved 2013-10-29. https://blogs.msdn.com/b/ieinternals/archive/2009/06/19/windows-7-support-for-tls-and-ciphers.aspx ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
"Windows 7 adds support for TLSv1.1 and TLSv1.2 – IEInternals – Site Home – MSDN Blogs". Archived from the original on 2013-12-26. Retrieved 2013-10-29. https://blogs.msdn.com/b/ieinternals/archive/2009/06/19/windows-7-support-for-tls-and-ciphers.aspx ↩
Thomlinson, Matt (2014-11-11). "Hundreds of Millions of Microsoft Customers Now Benefit from Best-in-Class Encryption". Microsoft Security. Archived from the original on 2014-11-14. Retrieved 2014-11-14. https://blogs.microsoft.com/cybertrust/2014/11/11/hundreds-of-millions-of-microsoft-customers-now-benefit-from-best-in-class-encryption ↩
RC4 can be disabled except as a fallback (Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback).[66] ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
IE11 will continue to support these operating systems if they are with ESUs until at least October 13, 2026. ↩
"Internet Explorer 11 for Windows Server 2012 and Windows Embedded 8 Standard". Microsoft Support. 2019-04-16. https://support.microsoft.com/en-us/help/4492872/update-for-internet-explorer-april-16-2019 ↩
"Internet Explorer 11 for Windows Server 2012 and Windows Embedded 8 Standard". Microsoft Support. 2019-04-16. https://support.microsoft.com/en-us/help/4492872/update-for-internet-explorer-april-16-2019 ↩
Fallback to SSL 3.0 is sites blocked by default in Internet Explorer 11 for Protected Mode.[68][69] SSL 3.0 is disabled by default in Internet Explorer 11 since April 2015.[70] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
Microsoft (2013-09-24). "IE11 Changes". Archived from the original on 2013-10-30. Retrieved 2013-11-01. https://blogs.msdn.com/b/ieinternals/archive/2013/09/24/internet-explorer-11-changelist-change-log.aspx ↩
Fallback to SSL 3.0 is sites blocked by default in Internet Explorer 11 for Protected Mode.[68][69] SSL 3.0 is disabled by default in Internet Explorer 11 since April 2015.[70] ↩
All RC4 cipher suites are disabled by default. ↩
MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 – via Microsoft Docs. /wiki/Microsoft_Security_Response_Center ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
"Protocols in TLS/SSL (Schannel SSP) - Win32 apps". learn.microsoft.com. Retrieved 2022-02-20. https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016". Microsoft. 2017-03-21. Archived from the original on 2017-03-30. Retrieved 2017-03-29. https://web.archive.org/web/20170330011044/https://technet.microsoft.com/en-us/windows-server-docs/security/tls/tls-schannel-ssp-changes-in-windows-10-and-windows-server-2016 ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
IE11 ran out of support for GAC (formerly CB and SAC) editions of Windows 10 since June 15, 2022.[75][76] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
"Protocols in TLS/SSL (Schannel SSP) - Win32 apps". learn.microsoft.com. Retrieved 2022-02-20. https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
"Protocols in TLS/SSL (Schannel SSP) - Win32 apps". learn.microsoft.com. Retrieved 2022-02-20. https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
DTLS protocol counterpart version, however, is not supported.[63] /wiki/DTLS ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016". Microsoft. 2017-03-21. Archived from the original on 2017-03-30. Retrieved 2017-03-29. https://web.archive.org/web/20170330011044/https://technet.microsoft.com/en-us/windows-server-docs/security/tls/tls-schannel-ssp-changes-in-windows-10-and-windows-server-2016 ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
"TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016". Microsoft. 2017-03-21. Archived from the original on 2017-03-30. Retrieved 2017-03-29. https://web.archive.org/web/20170330011044/https://technet.microsoft.com/en-us/windows-server-docs/security/tls/tls-schannel-ssp-changes-in-windows-10-and-windows-server-2016 ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
"Protocols in TLS/SSL (Schannel SSP) - Win32 apps". learn.microsoft.com. Retrieved 2022-02-20. https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72] ↩
All RC4 cipher suites are disabled by default. ↩
Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers). ↩
IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54] /wiki/Schannel ↩
"HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29. https://msdn.microsoft.com/en-us/library/bb250503.aspx ↩
"What browsers work with Universal SSL". Archived from the original on 2016-03-04. Retrieved 2015-06-15. https://support.cloudflare.com/hc/en-us/articles/203041594-What-browsers-work-with-Universal-SSL ↩
Could be disabled via registry editing but need 3rd Party tools to do this.[78] ↩
"What TLS version is used in Windows Phone 8 for secure HTTP connections?". Microsoft. Archived from the original on 2016-03-04. Retrieved 2014-11-07. https://social.msdn.microsoft.com/Forums/windowsapps/en-US/2ddee177-5086-4453-987b-d02b6a7ec62d/what-tls-version-is-used-in-windows-phone-8-for-secure-http-connections?forum=wpdevelop ↩
"What TLS version is used in Windows Phone 8 for secure HTTP connections?". Microsoft. Archived from the original on 2016-03-04. Retrieved 2014-11-07. https://social.msdn.microsoft.com/Forums/windowsapps/en-US/2ddee177-5086-4453-987b-d02b6a7ec62d/what-tls-version-is-used-in-windows-phone-8-for-secure-http-connections?forum=wpdevelop ↩
"Qualys SSL Labs – Projects/User Agent Capabilities: Unknown". Archived from the original on 2017-03-01. https://www.ssllabs.com/ssltest/viewClient.html?name=IE%20Mobile&version=10&platform=Win%20Phone%208.0 ↩
Could be disabled via registry editing but need 3rd Party tools to do this.[78] ↩
"Platform Security". TechNet. Microsoft Docs. 2014-06-25. Retrieved 2021-10-24. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-phone/dn756283(v=technet.10) ↩
"Platform Security". TechNet. Microsoft Docs. 2014-06-25. Retrieved 2021-10-24. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-phone/dn756283(v=technet.10) ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Release Notes: Important Issues in Windows 8.1 Preview". TechNet. Microsoft Docs. 2013-06-24. Retrieved 2021-10-24. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/dn303404(v=ws.11) ↩
"W8.1(IE11) vs RC4". Qualys Community. Archived from the original on 2014-11-04. Retrieved 2014-11-04. https://community.qualys.com/thread/12092 ↩
Could be disabled via registry editing but need 3rd Party tools to do this.[78] ↩
Edge (formerly known as Project Spartan) is based on a fork of the Internet Explorer 11 rendering engine. ↩
All RC4 cipher suites are disabled by default. ↩
"TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016". Microsoft. 2017-03-21. Archived from the original on 2017-03-30. Retrieved 2017-03-29. https://web.archive.org/web/20170330011044/https://technet.microsoft.com/en-us/windows-server-docs/security/tls/tls-schannel-ssp-changes-in-windows-10-and-windows-server-2016 ↩
All RC4 cipher suites are disabled by default. ↩
Safari uses the operating system implementation on Mac OS X, Windows (XP, Vista, 7)[84] with unknown version,[85] Safari 5 is the last version available for Windows. OS X 10.8 on have SecureTransport support for TLS 1.1 and 1.2[86] Qualys SSL report simulates Safari 5.1.9 connecting with TLS 1.0 not 1.1 or 1.2.[87] ↩
"Apple Secures Mac OS X with Mavericks Release". eSecurity Planet. 2013-10-25. Archived from the original on 2014-07-08. Retrieved 2014-06-23. http://www.esecurityplanet.com/mac-os-security/apple-secures-mac-os-x-with-mavericks-release.html ↩
"What browsers work with Universal SSL". Archived from the original on 2016-03-04. Retrieved 2015-06-15. https://support.cloudflare.com/hc/en-us/articles/203041594-What-browsers-work-with-Universal-SSL ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
In September 2013, Apple implemented BEAST mitigation in OS X 10.8 (Mountain Lion), but it was not turned on by default, resulting in Safari still being theoretically vulnerable to the BEAST attack on that platform.[89][90] BEAST mitigation has been enabled by default from OS X 10.8.5 updated in February 2014.[91] ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"About Security Update 2015-002". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-16. Retrieved 2015-03-09. https://support.apple.com/en-us/HT204413 ↩
"About the security content of OS X Mavericks v10.9". Archived from the original on 2014-07-04. Retrieved 2014-06-20. http://support.apple.com/kb/HT6011 ↩
"About the security content of OS X Mavericks v10.9". Archived from the original on 2014-07-04. Retrieved 2014-06-20. http://support.apple.com/kb/HT6011 ↩
Ristić, Ivan (2013-10-31). "Apple enabled BEAST mitigations in OS X 10.9 Mavericks". Archived from the original on 2013-11-07. Retrieved 2013-11-07. http://blog.ivanristic.com/2013/10/apple-enabled-beast-mitigations-in-mavericks.html ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"About Security Update 2015-002". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-16. Retrieved 2015-03-09. https://support.apple.com/en-us/HT204413 ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"User Agent Capabilities: Safari 8/OS X 10.10". Qualys SSL Labs. Archived from the original on 2015-09-06. Retrieved 2015-03-07. https://www.ssllabs.com/ssltest/viewClient.html?name=Safari&version=8&platform=OS%20X%2010.10 ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"About Security Update 2015-002". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-16. Retrieved 2015-03-09. https://support.apple.com/en-us/HT204413 ↩
"About the security content of OS X Yosemite v10.10.4 and Security Update 2015-005". Archived from the original on 2015-07-02. Retrieved 2015-07-03. https://support.apple.com/en-us/HT204942 ↩
Pauly, Tommy (2019-01-29). "TLS 1.3 in iOS". [email protected] (Mailing list). https://mailarchive.ietf.org/arch/msg/tls/5QjzTilqjomSyzENtgfaAqQOhbA ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
Mobile Safari and third-party software utilizing the system UIWebView library use the iOS operating system implementation, which supports TLS 1.2 as of iOS 5.0.[99][100][101] /wiki/IOS ↩
"Secure Transport Reference". Archived from the original on 2014-06-04. Retrieved 2014-06-23.kSSLProtocol2 is deprecated in iOS https://developer.apple.com/library/mac/documentation/security/Reference/secureTransportRef/Reference/reference.html#//apple_ref/c/tdef/SSLProtocol ↩
"iPhone 3.0: Mobile Safari Gets Enhanced Security Certificate Visualization". The iPhone Blog. 2009-03-31. Archived from the original on 2009-04-03. https://web.archive.org/web/20090403074546/http://www.theiphoneblog.com/2009/03/31/iphone-30-mobile-safari-enhanced-security-certificate-visualization ↩
"What browsers work with Universal SSL". Archived from the original on 2016-03-04. Retrieved 2015-06-15. https://support.cloudflare.com/hc/en-us/articles/203041594-What-browsers-work-with-Universal-SSL ↩
"Technical Note TN2287 – iOS 5 and TLS 1.2 Interoperability Issues". Apple. 2011-10-14. Archived from the original on 2011-09-07. Retrieved 2012-12-10. https://developer.apple.com/library/ios/#technotes/tn2287/_index.html ↩
"Technical Note TN2287 – iOS 5 and TLS 1.2 Interoperability Issues". Apple. 2011-10-14. Archived from the original on 2011-09-07. Retrieved 2012-12-10. https://developer.apple.com/library/ios/#technotes/tn2287/_index.html ↩
"Projects/User Agent Capabilities: Safari 7/iOS 7.1". Qualys SSL Labs. Archived from the original on 2017-03-13. https://www.ssllabs.com/ssltest/viewClient.html?name=Safari&version=7&platform=iOS%207.1 ↩
"SOAP Request fails randomly on one Server but works on another on iOS7". Stack Overflow. 2013-10-11. Retrieved 2014-01-05. https://stackoverflow.com/q/19221568 ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"User Agent Capabilities: Safari 8/iOS 8.1.2". Qualys SSL Labs. Archived from the original on 2016-03-04. Retrieved 2015-03-07. https://www.ssllabs.com/ssltest/viewClient.html?name=Safari&version=8&platform=iOS%208.1.2 ↩
Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0. ↩
"About the security content of iOS 8.2". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-09. Retrieved 2015-03-09. https://support.apple.com/en-us/HT204423 ↩
"About the security content of iOS 8.4". Archived from the original on 2015-07-03. Retrieved 2015-07-03. https://support.apple.com/en-us/HT204941 ↩
All RC4 cipher suites are disabled by default. ↩
Pauly, Tommy (2019-01-29). "TLS 1.3 in iOS". [email protected] (Mailing list). https://mailarchive.ietf.org/arch/msg/tls/5QjzTilqjomSyzENtgfaAqQOhbA ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
All RC4 cipher suites are disabled by default. ↩
Whether EV SSL and DV SSL (normal SSL) can be distinguished by indicators (green lock icon, green address bar, etc.) or not. ↩
e.g. 1/n-1 record splitting. ↩
e.g. Disabling header compression in HTTPS/SPDY. /wiki/HTTPS ↩
Complete mitigations; disabling SSL 3.0 itself, "anti-POODLE record splitting". "Anti-POODLE record splitting" is effective only with client-side implementation and valid according to the SSL 3.0 specification, however, it may also cause compatibility issues due to problems in server-side implementations. Partial mitigations; disabling fallback to SSL 3.0, TLS_FALLBACK_SCSV, disabling cipher suites with CBC mode of operation. If the server also supports TLS_FALLBACK_SCSV, the POODLE attack will fail against this combination of server and browser, but connections where the server does not support TLS_FALLBACK_SCSV and does support SSL 3.0 will still be vulnerable. If disabling cipher suites with CBC mode of operation in SSL 3.0, only cipher suites with RC4 are available, RC4 attacks become easier. When disabling SSL 3.0 manually, POODLE attack will fail. /wiki/Block_cipher_mode_of_operation#Cipher-block_chaining_(CBC) ↩
Complete mitigation; disabling cipher suites with RC4. Partial mitigations to keeping compatibility with old systems; setting the priority of RC4 to lower. ↩
"Tracking the FREAK Attack". Archived from the original on 2015-03-06. Retrieved 2015-03-08. https://freakattack.com ↩
"FREAK: Factoring RSA Export Keys". Archived from the original on 2015-03-11. Retrieved 2015-03-08. https://www.smacktls.com/#freak ↩
"SSLSocket|Android Developers". Archived from the original on 2015-03-18. Retrieved 2015-03-11. https://developer.android.com/reference/javax/net/ssl/SSLSocket.html ↩
"SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility ↩
"What browsers work with Universal SSL". Archived from the original on 2016-03-04. Retrieved 2015-06-15. https://support.cloudflare.com/hc/en-us/articles/203041594-What-browsers-work-with-Universal-SSL ↩
"ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13. https://support.globalsign.com/customer/portal/articles/1995283-ecc-compatibility ↩
"SSLSocket|Android Developers". Archived from the original on 2016-03-04. Retrieved 2015-12-17. https://developer.android.com/reference/javax/net/ssl/SSLSocket.html ↩
"SSLSocket|Android Developers". Archived from the original on 2016-03-04. Retrieved 2015-12-17. https://developer.android.com/reference/javax/net/ssl/SSLSocket.html ↩
"SSLSocket|Android Developers". Archived from the original on 2016-03-04. Retrieved 2015-12-17. https://developer.android.com/reference/javax/net/ssl/SSLSocket.html ↩
"Android 5.0 Behavior Changes|Android Developers". Archived from the original on 2015-03-09. Retrieved 2015-03-11. https://developer.android.com/about/versions/android-5.0-changes.html#ssl ↩
"SSLSocket|Android Developers". Archived from the original on 2016-03-04. Retrieved 2015-12-17. https://developer.android.com/reference/javax/net/ssl/SSLSocket.html ↩
"Android 5.0 Behavior Changes|Android Developers". Archived from the original on 2015-03-09. Retrieved 2015-03-11. https://developer.android.com/about/versions/android-5.0-changes.html#ssl ↩
Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback. ↩
"Android 8.0 Behavior Changes". Archived from the original on 2017-12-01. https://developer.android.com/about/versions/oreo/android-8.0-changes.html ↩