Most custom-domain problems come down to one of three things: DNS hasn't finished spreading yet, a record was entered slightly wrong, or SSL is still being issued. The good news is that each has a clear fix. Work through the sections below in order and you'll usually find the cause quickly.
The site isn't loading on my domain yet
If your domain doesn't show your site right after you add the records, the most likely reason is propagation — DNS changes spread gradually across the internet. This often takes minutes to a few hours and can occasionally take 24–48 hours.
- Wait a little and check again rather than re-adding records repeatedly.
- Try loading the domain in a private/incognito window, which avoids old cached results.
- Confirm the records are saved at your registrar and haven't been reverted.
I think a DNS record is wrong
A single typo will stop a domain from connecting. Compare what's at your registrar against exactly what the platform asked you to add — see DNS records explained for what each record does.
- Check the record type matches (an
Arecord versus aCNAME). - Check the value exactly, with no extra spaces or missing characters.
- Check the name/host field — root domain versus
www— matches what was requested. - Remove any old, conflicting records that point the same name elsewhere.
- Save, then allow time for the corrected record to propagate.
SSL is stuck on pending
SSL certificates are issued automatically, but only after your DNS records are correct and detected. If HTTPS shows as pending or you see a security warning, it almost always means verification hasn't completed yet.
- Make sure your DNS records are correct and have finished propagating — SSL can't be issued until the domain verifies.
- Give it time after verification; the certificate is provisioned automatically and isn't instant.
- Avoid forcing
https://manually before the certificate is ready — once issued, secure loading works on its own.
Quick checklist
- Records added exactly as shown, correct type and value.
- No leftover conflicting records.
- Enough time allowed for propagation.
- Domain verified before expecting SSL.
If you'd rather skip DNS entirely
Registering a domain inside the app avoids manual records altogether, since it's auto-configured for your site — see Registering a new domain. For the full connection steps with an existing domain, see Connecting a custom domain.
Still need help? If you've checked your records, waited for propagation, and SSL is still pending, open a support ticket from your support page. Include your domain name and a screenshot of the DNS records at your registrar so we can spot the issue faster.