Webarchitects are able to provide HTTPS certificates for shared hosting sites and also for virtual servers.
Transport Layer Security (TLS) certificates and properly configured webservers can ensure that all communication between a website and a site user is encrypted. This is now strongly recommended for all websites, and it is essential to protect passwords and other confidential data.
Our latest WordPress, Discourse, MediaWiki, Nextcloud and Web Hosting packages come with free Let's Encrypt multi-domain, domain verified certificates, one per site.
We are also able to provide commercial certificates because there are some devices and platforms which don't work with Let's Encrypt certificates, see the limitations listed below.
If your site is hosted on one of our older servers which doesn't provide Let's Encrypt certificates please get in touch to discuss migrating your site onto a server which does.
Let's Encrypt doesn't (yet) provide wildcard certificates or extended verification certificates, we can provide and install these for clients who need them.
The following prices for domain name verified certificates include the installation of the certificates. If you need an extended verification certificate please get in touch to discuss your needs.
www. prefixwww. counts as one)www. counts as one)These prices are based on what the certificates cost us, plus 15 mins of our time to set them up, rounded to the nearest 50p.
The free TLS certificates provided by Let's Encrypt are subject to their terms and conditions and certificate request rate limits. While these are quite high it is possible that we will reach them and this could have an impact on how many certs we can generate.
Some combinations of platforms and browsers don't work with Let's Encrypt certificates, for example the BlackBerry 10 and Windows XP, so if you have users with these devices / platforms then consider a commercial certificate.
For modern web browsers a dedicated IP address is no longer needed for HTTPS due to the widespread support for Server Name Indication, (see the Wikipedia page on SNI). However some older platforms, such as Internet Explorer on Windows XP, don't support SNI, so you might want to consider having a dedicated IP address to go with a certificate. We can provide dedicated IP addresses for shared hosting sites and also for virtual servers.
If you have a site at www.example.org then a single domain
certificate can be used to secure it, and it will also work with
example.org (both domains are automatically added to the
certificate).
If you are doing something like hosting a WordPress multi-site and want all
the blogs you host to have a valid certificate then you need a wildcard cert covering
*.example.org. This secures example.org
and anything.example.org where 'anything' is any
combination of letters, numbers and dashes (but not starting or ending with a
dash).
If your site has several domains, or you want to share a certificate between
several sites, then the multiple domain certificate can be used. A 5 domain certificate is typically
used for example.org, www.example.org,
example.co.uk, www.example.co.uk and
dev.example.org. Multiple domain certificates cannot contain wildcards
and are ideal when you have limited IP addresses and need to support
clients which don't have SNI support.
Last updated:
