Why use HTTPS
Strong encryption is critical to ensure your privacy and security while using WordPress.com. We encrypt all possible traffic, including custom domains hosted on WordPress.com. We consider strong encryption so important that we do not allow you to compromise the security of your site by disabling it. We also 301 redirect all insecure HTTP requests to the secure HTTPS version.
Frequently Asked Questions
Does HTTPS make my site slower?
This used to be true, but technologies like HTTP/2 have significantly improved performance. In some cases, encrypted HTTP/2 traffic even outperforms its un-encrypted counterpart. We invest heavily to make sure our servers are globally distributed and compatible with the latest emerging technologies to ensure the best possible user experience.
How do I get those annoying security warnings to go away?
In general, you should never see security warnings while using WordPress.com. If you do, please contact support and let us know the details.
Why do I see tls.automattic.com in my certificate’s common name (CN)?
If you have a custom domain on WordPress.com, we secure it using a SSL certificate from the Let’s Encrypt Certificate Authority. To improve the performance and simplicity of this process, we use the same Common Name, tls.automattic.com, for all certificates and store the unique domain names in the SubjectAltName attribute. All modern browsers honor this attribute and will not display any warnings or errors to you or your visitors.
Yes, currently we send a Strict-Transport-Security header with our HTTPS responses. HPKP is currently not supported, but may be in the future.