--- title: Configuring SSL --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). The **Secure Sockets Layer (SSL)** / **Transport Layer Security (TLS)** protocol is used to encrypt Internet communication. This is important for protecting the privacy of your users and for safekeeping sensitive information that is being sent. If you do not protect the sensitive information on your website, you can become susceptible to man-in-the-middle attacks. Such attacks happen when an attacker intercepts communication between two systems (e.g., a server and a client web browser). Attackers can eavesdrop on messages being sent and also possibly alter them without being detected. We recommend using a secured protocol (HTTPS) _**for all websites**_. ## How to start using SSL on your website 1. Obtain a certificate from a certificate authority or [create a self-signed certificate](#creating-a-self-signed-certificate-in-iis). 2. [Bind the certificate to your website through IIS server](#binding-a-certificate-to-a-website). 3. [Configure your website to use secured URLs](#configuring-the-live-site-to-use-https). ## What are SSL certificates SSL certificates are electronic documents, which use a digital signature to bind a public key (needed to establish a secure connection) with a server. The digital signature is provided either by the certificate itself (a self-signed certificate) or by a Certificate Authority: **Self-signed certificates** - You can create them easily by yourself, but they are less secure than those signed by a Certificate Authority. - Great for testing servers and suitable for collecting personal (non-financial) information. - You should not use a self-signed certificate on an e-commerce site. **Certificates signed by a Certificate Authority** - Must be issued by a Certificate Authority, which verifies that the subject (server) of the certificate is what it claims to be. - Can be expensive, but provide high security. - It is generally recommended to use this type of certificate. ## Creating a self-signed certificate in IIS 1. Open IIS Manager. 2. Click on the name of your server in the **Connections** column on the left. 3. Double-click the **Server certificates**. ![Click on the server name and open Server certificates](https://docs.kentico.com/docsassets/13/configuring-ssl/IIS_server_certificates.png "Click on the server name and open Server certificates") 4. In the **Actions** pane, click **Create Self-Signed Certificate**. ![In the Actions pane, click Create Self-Signed Certificate](https://docs.kentico.com/docsassets/13/configuring-ssl/IIS_create_certificate.png "In the Actions pane, click Create Self-Signed Certificate") 5. Type a friendly name for the certificate in the **Specify a friendly name for the certificate** box, and click **OK**. ![Type a friendly name for the certificate in the Specify a friendly name for the certificate box, and click OK](https://docs.kentico.com/docsassets/13/configuring-ssl/Friendly_name.png "Type a friendly name for the certificate in the Specify a friendly name for the certificate box, and click OK") The IIS server creates a new self-signed certificate with the name of your server as its common name. ## Binding a certificate to a website If you already have an SSL certificate (self-signed or from a Certificate authority), you need to configure the IIS server so that it can use it for incoming secure connections. > **Note:** **Note**: You need to configure SSL (HTTPS) separately for both your live site and the Xperience administration application. 1. Open IIS Manager. 2. Select a website, you want to bind the certificate to, in the **Connections** column on the left. 3. Click **Bindings...** in the **Actions** column. ![Select your website and click Bindings...](https://docs.kentico.com/docsassets/13/configuring-ssl/IIS_bindings.png "Select your website and click Bindings...") 4. Click **Add...** 5. Change the **Type** to _**https**_. 6. Select the certificate from the list. ![Select the certificate from the list](https://docs.kentico.com/docsassets/13/configuring-ssl/IIS_select_the_certificate.png "Select the certificate from the list") 7. Click **OK** and close the **Site bindings** dialog. The IIS server is now ready for using the assigned certificate with SSL handshake for incoming connections. ## Configuring the live site to use HTTPS To enable the live site to use HTTPS, you need to ensure the following: - In the IIS, configure the live site application to [use SSL](https://support.microsoft.com/en-us/help/324069/how-to-set-up-an-https-service-in-iis). - The [presentation URL](https://docs.kentico.com/13/configuring-xperience/managing-sites/setting-domain-names-for-sites.md) of the site needs to use the HTTPS protocol, e.g. _**https**://example.com_. - If the live site and administration application are hosted on separate domains, you need to set up the [multiple domain environment](https://docs.kentico.com/13/developing-websites/working-with-cookies/configuring-cookie-samesite-mode.md#multi-domain-environment) correctly. - If you use a self-signed certificate (for example in a development environment), you need to set the value of _CMSSchedulerAcceptAllCertificates_ [application key](https://docs.kentico.com/13/configuring-xperience/reference-web-config-application-keys.md) to _true_. Developers can ensure that pages are only accessible over a secured protocol (HTTPS) by using the [RequireHttpsAttribute](https://docs.microsoft.com/en-us/dotnet/api/system.web.mvc.requirehttpsattribute). You can either secure individual controllers or register the attribute as a global filter for the entire website.