> 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/managed-cloudflare-account/domains.md).
# Domains
Manage the Cloudflare settings for each website in your Elements Hosting account.
The Domains Overview page lists all of the websites that have been added to your Elements Hosting account.
Each domain listed here represents a website that you can manage using Cloudflare. From here, you can open an individual domain to configure features such as caching, performance, security, SSL/TLS settings, analytics, and more.
To manage a website:
1. Locate the domain you want to manage.
2. Select the domain name to open its Cloudflare dashboard.
3. Choose the Cloudflare feature you want to configure from the navigation menu.
Each website has its own independent Cloudflare settings, allowing you to customize performance and security on a per-domain basis.
{% hint style="info" %}
If your hosting account includes multiple websites, each one will appear separately in the Domains list. Changes made to one website do not affect any other websites in your account.
{% endhint %}
---
# 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/managed-cloudflare-account/domains.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.
