Troubleshooting Custom Domain

Scenario #1 Domain Setup with Cloudflare (CNAME Conflicts)

If you're trying to connect a custom domain to your Scorecard and your domain is using Cloudflare, you may run into an issue where the CNAME record pointing to dns.scoreapp.net fails to verify correctly.

Common Scenario

A common setup conflict happens when trying to point a subdomain like:

forms.yourdomain.com → dns.scoreapp.net

In Cloudflare, by default, CNAME records are proxied through their network (orange cloud icon), which can cause SSL conflicts or verification issues with ScoreApp, since we also use Cloudflare for DNS and SSL management.

Recommended Fix

To resolve this issue:

• Log in to your Cloudflare account.
• Go to the DNS settings for the domain.
• Locate the CNAME record that points to dns.scoreapp.net.
• Click the orange cloud icon to turn it grey — this disables Cloudflare's proxy for that record.
• Save your settings.

Once the proxy is disabled, you should be able to verify the domain inside your ScoreApp account without issues.

Important

DNS changes can take a few minutes to propagate (TTL), but in some cases, may take up to 48 hours.

Scenario #2: 404 Error – No Default Landing Page Set

If you're seeing a 404 error after publishing your scorecard, it may be because no landing page has been set as the default for your Scorecard.

This can happen even when your domain is correctly configured. Without a default landing page, ScoreApp doesn’t know which page to display.

Recommended Fix to Resolve the 404 Error:

Select the Scorecard you’ve connected to your domain.

Click on the Build tab from the left-hand menu.

Navigate to Landing Pages.

Locate the landing page you want to display.

Click the three dots on the far right-hand side of that page.

Click Make Default from the dropdown menu.

Once you’ve set a default landing page, your scorecard should correctly show the intended content instead of a 404 error.