---
title: "Cloudflare for a site"
url: https://docs.corefinity.com/guides/sites/go-live/cloudflare-for-a-site
type: guide
last_updated: 2026-11-13
feature: cloudflare
related:
  - https://docs.corefinity.com/api/reference/domains/get-company-cloudflare.md
  - https://docs.corefinity.com/api/reference/domains/connect-company-cloudflare.md
  - https://docs.corefinity.com/api/reference/domains/disconnect-company-cloudflare.md
  - https://docs.corefinity.com/api/reference/domains/refresh-company-cloudflare-zones.md
  - https://docs.corefinity.com/api/reference/domains/update-site-cloudflare-zone.md
  - https://docs.corefinity.com/api/reference/domains/update-site-cloudflare-ssl-mode.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_cloudflare_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_cloudflare_connect.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_cloudflare_disconnect.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_cloudflare_refresh_zones.md
  - https://docs.corefinity.com/mcp/tools/corestack_site_cloudflare_zone_set.md
  - https://docs.corefinity.com/mcp/tools/corestack_site_cloudflare_ssl_set.md
---
# Cloudflare for a site

Have a site's DNS records written for you and set SSL for its domains in a connected Cloudflare zone.

## Before you start

- You can open the site in **Managed Websites**. Anyone who can open a site can use its Cloudflare zone.
- Your organisation's Cloudflare account is connected: see [Connect Cloudflare](/guides/organisation/hosting-defaults/cloudflare-connection).
- The site's domain is in a zone that connection can see.

## What the connection adds to a site

| Where                                      | What you get                                                                                      |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| **Hostnames**                              | A hostname in a connected zone reads **Proxied by Cloudflare** and names the zone.                |
| Attaching a domain, **Change primary URL** | **Point DNS for me** writes one proxied `A` record for each hostname, so you copy no records.     |
| **Domains & HTTPS**                        | Advice when the zone's SSL/TLS mode would stop the site working, and the **Per-domain SSL** card. |
| The platform's section                     | **Purge Cloudflare cache**, for the whole zone or up to 30 addresses.                             |

## Have the DNS records written

1. **Tick Point DNS for me**

   At the DNS check of [Add a domain](/guides/sites/go-live/add-a-domain), tick **Point DNS for me**. Each hostname reads **Will be pointed**.

   _Screenshot: The DNS check of the attach dialog with Point DNS for me ticked and each hostname marked Will be pointed._

2. **Confirm**

   Finish the dialog. The records are written in the connected zone and checked again.

Tick **Replace the existing records** when a hostname already points somewhere else.

## Set SSL for chosen domains

The zone's SSL/TLS mode should be **Full** while a certificate is issued, then **Full (strict)**. With **Flexible**, visitors are sent round in a loop.

1. **Open Per-domain SSL**

   In **Domains & HTTPS**, find **Per-domain SSL**. It sets SSL for the domains you choose with a Cloudflare rule; every other name in the zone keeps the zone's own mode.

   _Screenshot: The Per-domain SSL card: a table of domains with their SSL mode, status and who set it, and Add a rule with the domains to tick, the SSL choice, Check access and Add rule._

2. **Add a rule**

   Under **Add a rule**, tick the **Domains**, choose **Full** or **Full (strict)** under **SSL**, then choose **Add rule**. **Check access** asks Cloudflare whether your token may do this and changes nothing.

The rule's **Status** reads **Waiting for Cloudflare**, then **Active**. **Remove…** deletes the rule, and those domains use the zone's own mode again.

A rule needs one more permission on your Cloudflare token: Zone, Config Rules, Edit. A rule names up to 50 domains in one zone.

## Automate this

**API:** [Update a site's Cloudflare zone](https://docs.corefinity.com/api/reference/domains/update-site-cloudflare-zone.md), scope `write`

```bash
curl -X PUT https://manage.corefinity.com/api/corestack/sites/1042/cloudflare-zone \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "auto"
  }'
```

**MCP:** [`corestack_site_cloudflare_zone_set`](https://docs.corefinity.com/mcp/tools/corestack_site_cloudflare_zone_set.md), scope `write`

```json
{
  "name": "corestack_site_cloudflare_zone_set",
  "arguments": {
    "site_id": 4211,
    "mode": "auto"
  }
}
```

**Control Panel:** Organisation › Organisations › your organisation › Hosting › Cloudflare ([https://manage.corefinity.com/go/cloudflare](https://manage.corefinity.com/go/cloudflare))

## Related

- [Connect Cloudflare](/guides/organisation/hosting-defaults/cloudflare-connection): Connect your Cloudflare account.
- [Check and point DNS](/guides/sites/go-live/check-and-point-dns): Point a hostname at a site.
- [Platform tools](/guides/sites/create-and-manage/platform-tools): Run your platform's maintenance commands.
