Skip to content
C CountdownFlow Help Center Sign in

Connecting custom domains

Verify domain ownership and set up routing to use your own hostname with campaigns.

2 min read

Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.

Requirements for custom domains

Custom-domain setup has three steps: prove ownership with TXT, upload the generated proxy files to the domain's PHP hosting, and confirm that HTTPS works. TXT verification alone does not install files or issue a certificate.

Ensure your workspace plan supports custom domains. The hosting must support PHP cURL and Apache mod_rewrite.

Custom domain setup screen before a real hostname is connected
Add a hostname you control and follow the records generated for that domain. DNS ownership, hosting readiness and HTTPS are separate checks. View full-size screenshot (opens in a new tab)

Connect a custom domain

  1. 1Navigate to Branding & domains to register the hostname you control.
  2. 2Copy the provided TXT ownership name and value, then add them via your DNS provider.
  3. 3Add the exact TXT ownership record shown in CountdownFlow at your DNS provider. Keep the hostname pointed at the PHP hosting where you will upload the files.
  4. 4After the TXT record propagates, select Verify ownership.
  5. 5Download index.php and .htaccess from the domain card and upload both to that hostname's web root.
  6. 6Enable HTTPS at the hosting provider, then select Check HTTPS.

Troubleshooting common setup errors

  • Many providers append the root domain to records automatically; ensure you are not duplicating the entry.
  • Existing conflicting records at the target hostname can interfere with proper routing.
  • The PHP proxy must be uploaded to the web root for the exact hostname registered in CountdownFlow.
  • Some hosting plans disable PHP cURL or Apache mod_rewrite; confirm both are available.
  • The domain must have a valid HTTPS certificate before it can be connected.

Workspace access constraints

Using a custom domain does not override existing workspace access or security protocols. Users who are not members of the workspace associated with the domain may still face access denials. Maintain an official login URL for testing and wait to switch live domains until HTTPS and routing are verified.

Related articles