Frequently asked questions


Do you support HTTPS (SSL/TLS) for web?


HTTPS (SSL/TLS) enables encrypted connections between the webserver and the web browser. Among other things, HTTPS is used for secure transfer of credit card details or other sensitive information over the internet.

In order to use HTTPS with us, you need to have one of our Webhotel packages for your domain.

We do not offer certificates for use with other providers, we are not a certificate authority. Certificates served by us are only for use with web hosting with us.

As of December 6, 2017, HTTPS is enabled by default, with some exceptions listed at the bottom of this page.

Free-of-charge HTTPS with Let's Encrypt

Let's Encrypt is a free, automated and open certificate provider (CA) that issues simple SSL-certificates for your domain. A certificate from Let's Encrypt will give you full connection encryption, and the green lock in your browser indicating HTTPS-encryption:

To activate Let's Encrypt, follow these instructions after logging in to the control panel:

  1. Go to My domains
  2. Click the domain name you want to activate Let's Encrypt for. The domain must have the Web hosting service
  3. Click the Web hosting tab
  4. Click View/change next to HTTPS
  5. Choose Let's Encrypt in the drop-down menu for Free HTTPS and then click Change

The certificate will automatically be installed within the next 20 minutes, and will include all domains on your user account that are connected to the website you are activating HTTPS for. Due to DNS changes, it may take a few hours before HTTPS will begin working for your domain.

A certificate from Let's Encrypt does not contain information about the identity of the company behind the domain name. If you must have this, you need your own certificate (see below).

HTTPS with own/dedicated certificate

Before automated certificates were possible with Let's Encrypt, we had a free-of-charge offer to manually create a CSR and manually install the corresponding certificate to a webhotel.

This is not technically necessary with websites hosted by us, and is therefore no longer an ordinary service offered by us.


Even so, some customers may need a manually handled certificate on web hosting with us.

  • Customers who must have an EV certificate
  • Customers with DNS service hosted by a third party and frontend proxy (e.g. DDoS protection) hosted by a third party (e.g. CloudFlare, Fastly), but where our server still must have HTTPS
  • Customers requiring more than 100 domains/subdomains on the same certificate with us.

Please contact support if you have such needs, and follow the below procedure.

Procedure for manual handling

  1. The domain must have Web hosting Medium or larger.

  2. Let us know if you want your certificate to be valid for something other than your webhotel's configured addresses.

  3. Also send us the following information for use with the certificate, and specify if they differ from the domain holder's info:

    • Company name (website owner)
    • Locality/city and country
    • E-mail address

    Any other contact information is unnecessary, the certificate does not need street/postal addresses, zip codes or names.

    Please note that some CAs will refuse to provide a certificate when the above mentioned company name is different from the domain holder's name.

  4. We'll create a CSR (Certificate Signing Request) for you.

  5. You then send the CSR to a certificate authority (CA), and make sure to note that the server type is Apache/mod_ssl. When ordering, most vendors will let you specify whether your certificate will work both with and without www. Below are a couple of example certificate authorities for EV certificates, depending on your needs and finances:

  6. The certificate authority will send you a so-called CA bundle and a certificate, usually in the form of a zip file, e.g., or in separate files, all of which must be in the PEM format. Send these files to us.

  7. Please do not send us the certificate as pasted or forwarded text.

  8. We will check the certificate, install it on our server, and let you know when it's ready.

  9. Your webhotel is now manually configured, and you must not change the primary address, DNS, or www forwarding setup for the webhotel without checking with customer support.

Remember to renew your certificate before it expires, and send the new certificate file to us. You may reuse the CSR you originally received from us.

HTTPS som standard - notes and exceptions

HTTPS is, as of December 6, 2017, the default, with automatic redirect from HTTP to HTTPS, for the following customers:

  • anyone upgrading from no webhotel to one of our webhotel packages
  • anyone registering a new domain and orders Webhotel
  • anyone upgrading from Webhotel Starter, to Medium or greater

Additionally, HTTPS is enabled for almost all existing Webhotel Starter since December 7, 2017.

HTTPS is not enabled by default for the following webhotel customers, who must enable HTTPS themselves:

  • customers transfering their domain and services to Domainnameshop and simultaneously orders a webhotel
  • customers who already have Webhotel, who have not yet enabled HTTPS

The maximum number of domains and subdomains that can be handled with HTTPS on the same webhotel, is 100.

See also:

© 2024 Domeneshop AS · About us · Terms · Privacy policy