> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/hosting/elements-hosting-reactor-panel/websites/manage-websites/security.md).
# Security
Secure your websites with automatic Let's Encrypt SSL certificates
The Security section focuses on managing SSL certificates for your website(s). SSL certificates encrypt traffic between your site and its visitors, helping protect data and ensuring browsers mark your site as secure. On Elements Hosting, SSL certificates are handled automatically to reduce setup and ongoing maintenance.
Once Elements Hosting detects that your domain’s DNS is correctly pointed to our service, a free Let’s Encrypt SSL certificate is automatically issued and installed for your site. If the domain’s DNS has not been pointed yet, or DNS changes are still propagating, a temporary self-signed SSL certificate is used instead. As soon as the DNS is detected correctly, the Let’s Encrypt certificate is issued automatically and replaces the temporary certificate. No manual action is required.
From the Security section, you can also manage additional SSL-related options, such as:
1. Install a custom SSL certificate if you have purchased one separately
2. Force all web traffic to use HTTPS for improved security and consistency
3. Manually request or renew a Let’s Encrypt certificate if needed, as well as view your current SSL certificate's details.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.realmacsoftware.com/elements-docs/hosting/elements-hosting-reactor-panel/websites/manage-websites/security.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
