Update: The Typekit embed code is now relative to the protocol, so you no longer have to specify when the fonts should be served as SSL. Details are available in this blog post.

Until now, SSL support has only been available on Typekit’s Performance Plan and higher. But starting today, we’re making SSL support available to all plans — including the Free Plan.

Why the change? When we launched Typekit, SSL was primarily a requirement of ecommerce sites. Since then, the risks of insecure cookies have become clear, and SSL is now generally recommended for any site with a login: whether commerce is involved or not.

We’ve recently updated the Typekit website to use SSL at all times, and we want to make sure our customers are also able to do so without the burden of an additional fee. So today we’re making SSL available to everyone, regardless of your subscription level.

If you’re on the Free, Personal, or Portfolio Plan, you can now republish your kits to get SSL access. If you intend to use SSL, you’ll also need to update the embed code on your sites, from http:// to https://. (Users on the Performance Plan and higher already had SSL access, so there is no need for action on your part.)

If you have any questions about this change, please drop a line to support@typekit.com. We’ll get back to you right away.