62,682
edits
Changes
no edit summary
| 2017 || || Standard || TLS 1.3 || Protocol || The standard for TLS 1.3 is under discussion, but not finalized. Browsers support it for a while as the default but then stop due to issues. See [[w:Transport Layer Security#TLS_1.3_.28draft.29]] for more. As of the end of 2017, TLS 1.3 is still not ready.<ref>{{cite web|url = https://blog.cloudflare.com/why-tls-1-3-isnt-in-browsers-yet/|title = Why TLS 1.3 isn't in browsers yet|last = Sullivan|first = Nick|date = December 26, 2017|accessdate = January 28, 2018|publisher = Cloudflare}}</ref>
|-
| 2017 || {{dts|December 30}} || || || || <code>nonhttps.com<code/> is registered.<ref>{{cite web |title=nonhttps.com |url=https://who.is/whois/nonhttps.com |website=who.is |accessdate=24 February 2020}}</ref> Similar to <code>neverssl.com</code>, the site is created to for websites to "guarantee that they will always remain accessible by HTTP".<ref>{{cite web |title=HTTPS |url=https://wikivisually.com/wiki/HTTPS |website=wikivisually.com |accessdate=24 February 2020}}</ref>
|-
| 2018 || {{dts|February 27}} || Certificate authority || Let's Encrypt || Wildcard support || Let's Encrypt plans to make wildcard support fully available on this date, after launching a public test API endpoint for the ACME v2 protocol and wildcard support on January 4, 2018.<ref>{{cite web|url = https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html|title = Wildcard Certificates Coming January 2018|last = Aas|first = Josh|date = July 6, 2017|accessdate = January 28, 2018|publisher = Let's Encrypt}}</ref>
