Troubleshooting

Fix custom-domain issues fast

Most failures come down to only four things: wrong DNS zone, wrong CNAME value, Cloudflare proxying too early, or platform-side connection still finishing.

The most common mistakes

You entered status.example.com in Statuscode but created the CNAME inside the DNS zone for example.in.

The CNAME does not point to cname.statuscode.in.

Cloudflare is on Proxied before the first verification pass. Start with DNS only.

You used the root domain like example.com instead of a subdomain like status.example.com.

If verification says not found

Confirm the exact hostname in Statuscode matches the zone where you added the record.

Confirm the record type is CNAME.

Confirm the host/name is just status, not the full hostname, if your DNS provider expects a relative name.

Wait a few minutes and run verify again.

If the browser shows the wrong page or a Vercel error

The domain may be reaching the hosting platform before the platform-side attach is fully healthy.

Open the custom-domain panel in the editor and use Refresh so Statuscode can reconcile DNS, provider attach, and SSL state again.

If you changed the domain value recently, republish once after the domain returns to a connected state.

What correct DNS looks like

Host

status

Type

CNAME

Target

cname.statuscode.in

Root domain

Do not use the apex/root domain for this flow.

Was this helpful?

Quick feedback helps improve the docs.