How to Set Up Domains in Sparkforge (Whitelabel, API, Email, Sites, Client Portal)

Domains are the backbone of your Sparkforge presence — websites, branded links, email sending, the client portal, and your whitelabel app all run on them. This guide covers what to connect where, the difference between root and subdomains, and how to handle DNS manually when Domain Connect isn't an option.

Domain basics

Root domain

Example: mywebsite.com. The primary address of your site, before the www. prefix.

Subdomain

Example: help.mywebsite.com. An extension of the root domain that points to its own destination — useful when the root is already in use.

Important: avoid pointing a root domain at Sparkforge if it's already serving a website or email. Use a subdomain instead. Adding the wrong root domain is the most common cause of broken mailboxes and offline sites.

Connect with Domain Connect

If your registrar is Google, Cloudflare, or GoDaddy, Sparkforge can configure DNS for you automatically. Use this for branded domains, sites, dedicated email domains, and the client portal — no manual records.

Manual DNS

For any other registrar, Sparkforge generates the record values you need. The flow is the same everywhere:

1. Open your DNS manager and click Add Record.
2. Pick the record type Sparkforge specified (A, CNAME, TXT, MX).
3. Paste the hostname into the Name field and the value into the Target/Value field.
4. Save. If you're on Cloudflare, toggle the proxy off so the record propagates correctly.

Where to add domains in Sparkforge

Whitelabel domain

Replaces the default desktop app URL with your own — usually app.yourdomain.com. Configure under Agency View > Settings > Company Settings > Whitelabel Domain. Use a subdomain.

API or branded domain

Customizes system-generated links for forms, surveys, calendars, and tracking. Set the agency default at Agency View > Settings > Company Settings > API Domain. Override per sub-account at Sub-Account > Settings > Business Profile > API Domain. Always a subdomain — a root domain here breaks your main website.

Sites (websites and funnels)

Configure at Sub-Account > Settings > Domains. Supports root or subdomain, depending on whether you're replacing an existing site or adding alongside it.

Email sending domain

Improves deliverability by sending from your own subdomain. Agency level: Agency View > Settings > Email Services > Dedicated Domain. Sub-account level: Sub-Account > Settings > Email Services > Dedicated Domain. Use a subdomain so you don't disturb existing mail flow.

Client portal domain

Hosts communities, courses, memberships, and the affiliate manager under your brand. Configure at Sub-Account > Sites > Client Portal > API Domain.

WordPress

Hosts new or migrated WordPress sites. Configure at Sub-Account > Sites > WordPress > Add Domain.

DNS record cheat sheet

Glossary

• Hostname — the prefix portion of the record (often a subdomain like help).
• Value/Target — what the record points to.
• Nameservers — the directory that controls where DNS lookups go (GoDaddy, Cloudflare, Google, etc.).
• A record — points a name to an IP address. Used for root domains pointing to a website.
• CNAME — points one domain at another. Used for subdomains.
• TXT — text records for SPF, DKIM, DMARC, and verification.
• MX — mail exchange records that route email to the right server.
• DMARC — TXT record that protects against email spoofing.

Troubleshooting

1. Check for duplicate A records

Look for multiple A records using @ as the hostname. Remove the conflicting ones and confirm the remaining record points at the Sparkforge IP 162.159.140.166.

2. Confirm DNS propagation

DNS changes can take 24–48 hours to propagate worldwide. Check status at dnschecker.org.

3. Review records for accuracy

Match every value against what Sparkforge generated. A single typo breaks the connection.

4. Verify nameservers

If your registrar's nameservers point to a different DNS provider, the records have to live on that provider — not the registrar. Use mxtoolbox.com to confirm where DNS is actually being served from.

5. Check for other causes

Server downtime, mistyped subdomains, or recent registrar changes can all cause 404s. Roll back recent changes if the issue started after a config update.

6. Get help

If you're stuck, contact your registrar's support or open a Sparkforge support ticket and we'll walk through it with you.