At the end of 2013, all Browsers and Certificate Authorities will no longer support 1024 bits RSA certificates to be compliant to National Institute of Standards and Technology (NIST) guidelines.

The SSL certificate currently used on api.twitter.com is signed with the older Verisign G2 root CA certificate.Read more…

If you use our streaming APIs, you should be aware of a change that’s coming in a couple months: We are updating the SSL certificates for userstream.twitter.com and stream.twitter.com on November 4, 2013.Read more…

Updates:

The sitestream.twitter.com SSL certificate will be changing from the current VeriSign certificate to a DigiCert certificate within the next month. Read more…

The SSL Certificate for api.twitter.com is currently signed against the Verisign G2 Root CA certificate. Verisign (recently acquired by Symantec) is no longer issuing new certificates against the G2 root (it expires in 2019.) They are only currently issuing certificates against the Verisign G3 and G5 roots (for EV certificates).

As the certificate for api.twitter.com is due to expire soon, we will be upgrading our servers with a new SSL Certificate that will be signed against the Verisign G3 root.Read more…

Today we are pleased to announce SSL support for our Tweet and Follow Button widgets. That means that now you can add these widgets to your secure https pages, enabling users to easily share your content and follow your accounts without leaving your site.Read more…

All our Streaming API products are now supporting SSL and we’ve just updated the Site streams, User streams and The Streaming APIs documentation pages accordingly. As we’re planning to sunset HTTP support in about a month, we strongly encourage you to switch to SSL (HTTPS) as soon as possible, especially if you’re still authenticating your Streaming API requests with Basic Auth. Read more…