How to Enable HTTPS

At Twitter, our security team is always working to guide you toward a safer Twitter experience.

• If you enable Always use HTTPS in your Account Preferences, your browser will use SSL encryption any time you access twitter.com.
  • This improves the security of your account and better protects you from eavesdropping if you’re using Twitter over an unsecured Internet connection, such as a public WiFi network.
• Twitter will use HTTPS to protect your password when you log in, whether or not you’ve enabled Always use HTTPS.

How to Set up HTTPS Encryption

• Log in to your Twitter account
• Click the drop-down menu on the right hand side of your screen
• Click Settings to visit your Accounts Settings Page
• Scroll down and check the box next to Always use HTTPS
• Click Save to save your changes

• Your browser's URL bar will show an "https://" before twitter.com, and a green "Twitter, Inc." next to the URL.
• All traffic between you and Twitter will be more secure.

Why wouldn't I check Always use HTTPS?

• We encourage you to enable Always use HTTPS in your Settings.
• Some users may find Twitter over HTTPS slightly slower than plain old HTTP, especially if using an Internet connection that’s already slow. We're working to make Twitter just as fast on HTTPS as it is on HTTP.
• Sometimes, when you are accessing Twitter over HTTPS, opening the details pane to view an image or video will cause a browser warning about mixed content. We're working on reducing the number of these errors as well.

Mobile Twitter and Apps

• On the official Twitter for iPhone and iPad applications, your communications are always encrypted via HTTPS, regardless of whether you have checked Always use HTTPS.
• When you visit mobile.twitter.com from your browser, your communications will be encrypted only if you specifically log in via https://mobile.twitter.com/.
  • We’re working on sharing the HTTPS checkbox between twitter.com and mobile.twitter.com.
• When using third-party applications, on your phone or computer, the encryption of your communications is up to the application’s author. Please check with them to see if they use HTTPS for all connections.