Settings » Domain Manager » Cloudflare Connection and Settings
Link: https://support.brilliantdirectories.com/support/solutions/articles/12000109759
The Cloudflare tab connects a Cloudflare-managed domain to Domain Manager. A connected account can support website pointing, DNS record management, email-authentication publication, and Cloudflare settings from the BD admin area.
Before starting
- Use a custom domain that exists in an accessible Cloudflare account.
- Have permission to authorize that account and domain.
- Keep a record of the current DNS and email settings.
- Use Sign in with Cloudflare to authorize the Cloudflare account and connect the domain to Domain Manager. For a free directoryup.com address, use the domain connection wizard to authorize Cloudflare and choose a custom domain.
For creating the Cloudflare zone and moving nameservers, see Connecting a Site to Cloudflare. Authorizing Domain Manager is separate from registering a domain or changing its nameservers.
Connect a domain while changing the website address
- Open the domain connection wizard.
- Select Use a domain from my Cloudflare account.
- Sign in and authorize the intended account.
- Filter the domain list and select the intended domain.
- Choose the main address or enter the required subdomain.
- Click Use this address to prepare its DNS records.
- Review Switch Over, then complete its separate confirmation.
A domain whose main address is already in use can still offer an available subdomain. Selecting the main address also points the root domain; selecting a subdomain leaves other addresses on that domain unchanged.

The Cloudflare connection wizard offers the main domain or a subdomain after authorization.
Alternative: connect an account for the current domain
Use these steps when the website already has its domain and Cloudflare still needs to be connected. If the wizard above already connected the account, continue to the next section.
- Open Settings > Domain Manager > Cloudflare.
- Click Sign in with Cloudflare.
- Sign in to the appropriate Cloudflare account.
- Review and authorize the requested access. It includes permission to manage the domain's security rules, which Apply BD security rules needs.
- Return to Domain Manager.
- Confirm that Connected to Cloudflare shows the intended domain.
If sign-in cannot find the domain or authorization is unavailable, check the account and domain access before making changes. Do not continue using a connection associated with a different domain. A connection made earlier with a Cloudflare API token shows An API token under Signed in using, with a Switch to signing in with Cloudflare link. New connections use Cloudflare sign-in only.

A successful authorization identifies demotailwind.com as the connected Cloudflare domain.
Point the website and publish email records
- Review the connected domain and the website's displayed target.
- Use Point my domain at my website when that action is needed.
- Review the resulting connection status.
- Under Email delivery records, use Add my email records to Cloudflare when offered.
- Open Emails and recheck sender authentication.
For changing the website to a different domain, follow the separate connection wizard. Pointing records and switching the website's primary address are distinct actions.
Manage DNS records
Use the DNS tab to inspect, add, edit, or delete supported records. Through Cloudflare sends supported website traffic through the Cloudflare proxy. Direct exposes the underlying DNS destination. Email-related records must use the mode required by the mail provider; sender-authentication CNAME records should remain Direct. See DNS Records.
Review Cloudflare settings
Set recommended defaults applies the Domain Manager's recommended configuration. Review the current settings and the confirmation before applying it, especially when the domain already has a custom configuration.
- Always use https controls redirection to HTTPS.
- Security level & bot fighting controls the available security level.
- Minimum encryption version sets the lowest accepted TLS version.
The recommended defaults enable Always use https and insecure-image HTTPS rewrites, select Full encryption, set minimum TLS to 1.2 and security to Medium, enable HTTP/3, faster repeat visits, Brotli, Early Hints, and Smart Tiered Cache, and turn off Hotlink protection. Bot Fight Mode is not changed by this action. Check the result for any setting the Cloudflare account does not allow to be updated.

The Settings card shows each setting's current value beside its recommended default. In this example Always use https is off and the minimum is TLS 1.0, so Set recommended defaults, marked, would turn Always use https on and raise the minimum to TLS 1.2 in one step.
Page caching
- Find Page caching.
- Review the displayed caching behavior.
- Set the offered cache lifetime within the supported 30–3600 second range.
- Click Turn on page caching.
- Review the saved status.
Use Clear cached pages when cached pages need to be refreshed. Check important public and signed-in workflows after changing caching behavior.

Page caching has its own lifetime and activation controls. This example shows caching turned off.
Security rules
The Security rules card applies BD's recommended Cloudflare security rules (custom WAF rules) to the connected domain. They let the website's own requests, payment notifications, image delivery, and SSL certificate checks through, and ask outdated browsers, WordPress scanners, and traffic from hosting companies to prove they are real visitors. Rules on the domain that BD did not create are kept.
Reconnect an older Cloudflare connection
A connection made with Sign in with Cloudflare before security rules were available does not include permission to manage them. The card then shows Reconnect to Cloudflare to allow security rules in place of the Apply BD security rules button. DNS records, settings, and page caching keep working until the connection is renewed.
- Click Reconnect to Cloudflare in the prompt.
- Sign in to the Cloudflare account that holds the domain and approve the requested access, including the new security-rules permission.
- Return to the Cloudflare tab. The Security rules card then shows its current status, usually a preview of the changes.

A connection made before security rules were available shows the reconnect prompt, marked, instead of the Apply BD security rules button.
The same prompt, with a Sign in with Cloudflare link, also appears when Cloudflare reports that the current connection is not allowed to manage the domain's security rules, for example a connection made earlier with an API token that lacks that permission.
Preview and apply the rules
- Open Settings > Domain Manager > Cloudflare and find Security rules, below Page caching.
- Review the list under Applying will make these changes in Cloudflare. Each line names a rule and what applying does to it, such as add, update the rule, turn it on, rename it, or move to the top.

- Click Apply BD security rules.
- In the Apply our security rules confirmation, click Yes, continue. Cancel closes it without changing anything.

- Check for the message Our security rules are on and up to date.
The preview uses these names for BD's rules:
- Let Brilliant Directories, payment and certificate requests through
- Let verified search engines through
- Challenge outdated browsers and WordPress scanners
- Challenge browsers that report a suspicious version
- Challenge traffic from hosting networks
A domain that already carries BD's older combined rule shows Challenge outdated browsers, WordPress scanners and hosting networks instead of the first and third challenge rules. In the Cloudflare dashboard, BD's rules are listed under Security > Security rules with names that begin with BD:.
How the rules are applied
- BD's two allow rules are placed first in the domain's rule list, so anything they let through also passes the domain's other rules. New challenge rules are added after the existing rules.
- Rules that BD did not create are never changed or removed. When the domain has any, the card says they stay exactly as they are.
- BD rules applied earlier, including older versions of them, are updated in place instead of being added a second time.
- When everything already matches, the card reads Our recommended security rules are on and up to date. and the Apply BD security rules button is hidden. Applying again when nothing differs changes nothing in Cloudflare. When BD updates its recommended rules, the card lists the updates the next time it is opened.
- If Cloudflare refuses a change partway through, the error message says how many changes were made before that. Click Apply BD security rules again to finish.
Not enough room for the rules
Each Cloudflare plan allows a limited number of custom security rules; a Free plan allows 5. When BD's rules would not fit beside the domain's existing rules, the card shows Not enough room for our security rules, hides the Apply button, and states how many rules the plan allows, how many the domain already uses, and how many more BD's rules need. Nothing is changed. Remove or combine some of the domain's own rules in Cloudflare under Security > Security rules, then reload the Cloudflare tab.
Advanced settings
Click Show beside Advanced settings to inspect HTTP/3, faster repeat visits, compression, Early Hints, Smart Tiered Cache, encryption mode, insecure-image handling, Bot Fight Mode, and hotlink protection. Availability and allowed changes can depend on the Cloudflare account and the current site configuration.
Full (strict) requires a trusted certificate for the website hostname on the origin server. Review SSL > Certificate on your server before changing encryption mode. If the panel refuses an unsafe change, resolve the stated prerequisite instead of forcing the setting at another screen.

Show expands the advanced settings. Encryption mode, marked, is the one setting here that can take the website offline if it is wrong; Full is recommended. Unavailable controls depend on the Cloudflare connection.
Disconnect
Disconnect stops Domain Manager from managing Cloudflare. Existing DNS records remain in place, and existing Cloudflare settings and proxying continue until separately changed. Reconnect the account to resume management from Domain Manager.
The wizard can publish website sender-authentication records without creating incoming mailboxes or their MX records. Review Mailboxes separately if the domain will receive email.
A completed setup shows the correct connected domain, the expected website connection, and verified email-authentication records. Test the website and email after applying any settings.
