Tak jeste prestat podporovat TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA a mohlo by z toho vyjit A+ :)pic.twitter.com/yxkoUKrMx8
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
Tak jeste prestat podporovat TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA a mohlo by z toho vyjit A+ :)pic.twitter.com/yxkoUKrMx8
No, you need HSTS (and no warnings) for A+
I think @Scott_Helme must have a reason why his own site allows TLS 1.0 and 1.1. Happy to learn from you experts. 

I have checked my logs some time ago in 2018, found no valid traffic using legacy browsers that do not support TLS 1.2 or 1.3 for a few months back, have disabled both TLS 1.0 and 1.1, wrote a blog post, in that order
https://www.michalspacek.com/disable-tls-1.0-and-1.1-today …
So now I am capped to B, because I don't want to cut access from legacy devices (e.g. Android 4.1 from Prestigio) spread among people or production sensors not accessible remotely (4 years old Axis firmware contained old openssh/curl and nobody will pay for onsite servicing).
Some of those devices still uses TLS 1.0, even when they were released long after 1.2 was done. How did that happen to large vendors as Google or Axis?
Apache HTTPD: SSLProtocol -All +TLSv1.2 Nginx: Switch to Apache HTTPD, then see above
Sorry, what?
Will they stop doing that in March when all browsers stop supporting 1.0 and 1.1?
No info on that but I don't think so.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.