There are three ways to connect domains to PrivateFlare: add a single domain manually, add a whole batch of domains as a list, or import domains from your Cloudflare account using an API token. Which method to choose depends on how many domains you are connecting and where they currently live.

Before connecting, we recommend preparing DNS in advance — see the “Adding Domains” section about pre-configuring A records. This speeds up certificate issuance and traffic switching.

Method 1. A single domain#

Best when you need to quickly connect a separate domain.

1. Open the add-domains form.
2. Enter the backend IP address — the server you are hiding (web server, AlterCPA, Binom, Keitaro, etc.).
3. If needed, set tags, enable certificate generation and http-to-https redirect, specify a mask (if domains are proxied to a single backend domain — more details in the “Adding Domains” section).
4. In the domain list field, enter one domain.
5. Check the task preview on the right and click the add button.

The domain will appear in the list and start being processed by the nodes. Further protection settings are available in the domain card on the “Protection” tab.

Method 2. Bulk adding (as a list)#

The main method for affiliate marketing and domain networks — connect dozens and hundreds of domains at once.

The form is the same as for a single domain, but in the list field you enter one domain per line:

domain1.com
domain2.com
domain3.com
shop.domain4.com

All domains in the list receive the same settings selected in the form: the same backend IP, tags, the certificate-generation flag, redirect, and mask. This is convenient when hundreds of domains point to a single tracker.

• Tags are applied to the whole batch at once — afterwards it is easy to filter the domain list by them.
• Mask applies to all domains in the list. For example, if tracker.team is configured on the backend, enter it in the Mask field — and all added domains will be proxied to it.
• The preview on the right shows exactly how the domains will be added: settings, checkboxes, masking. Check it before launching.

Tip: if some domains need different settings (different backends or masks), add them in separate batches — one settings group at a time.

Method 3. Import from Cloudflare#

If your domains are already in Cloudflare, there is no need to copy them manually — PrivateFlare will pull the list of zones directly from your account using an API token.

Step 1. Create an API token in Cloudflare#

1. Log in to the Cloudflare dashboard → My Profile → API Tokens → Create Token.
2. The easiest option is to use the Edit zone DNS template or create a custom token with the following permissions:
   • Zone → Zone → Read — to read the list of your domains (zones);
   • Zone → DNS → Read — to read DNS records (if needed for import/verification).
3. In the Zone Resources section, select All zones (or specific zones if you want to limit the import).
4. Create the token and copy it — Cloudflare shows the value only once.

Read permissions are enough for the token. Edit permissions are not required unless you want PrivateFlare to change records in Cloudflare.

Step 2. Run the import in PrivateFlare#

1. In the connect-domains form, select import from Cloudflare.
2. Paste the API token you created.
3. PrivateFlare will reach out to Cloudflare and pull the list of available zones (domains).
4. Check the domains you want to connect — you can select all or only some.
5. Set the common settings for the imported domains: backend IP, tags, certificates, redirect, mask — just like with bulk adding.
6. Check the preview and confirm the import.

After the import, the domains will appear in the common list and will be processed by the nodes just like those added manually.

Important: the import brings the domains and proxying settings into PrivateFlare. For traffic to flow through the nodes, the domains’ DNS records must point to PrivateFlare node IPs. Make sure the A/NS records are configured correctly (see the pre-configuration section in “Adding Domains”).

Which method to choose#

In all three cases, the individual protection settings of each domain are available after connecting, in its card on the “Protection” tab.