Guide · Base44
Base44 custom domain stuck on "Pending verification" or not loading
Updated
You connected your own domain to a Base44 app, but it still says "Pending verification", or visitors get an error or an SSL warning.
Why it happens
Base44 hosts the app, but the domain stays with your registrar or DNS host, so the records there have to line up before the domain can load and get its SSL certificate.
Possible causes
- The DNS records do not match exactly what Base44 shows for your domain.
- AAAA (IPv6) records for the same hostname are blocking the connection.
- CAA records block the certificate authorities Base44 uses.
- The domain is on hold at the registrar.
- You use Cloudflare and the records are not set to DNS only.
- The www version behaves differently: some domain endings (such as uk.com or eu.com) never get a www version, and for a subdomain the www address has to be added by Base44 support.
- The domain is still reserved by an app in another workspace.
You can't see it yourself
You're signed in, your customers aren't. Your own device can hold an old DNS answer or a cached page, so the domain can look fine to you while visitors elsewhere get an error.
Related: Lovable custom domain not working: "Action required", "Verifying" or "Unable to verify" · Google sign-in fails on my custom domain: "redirect_uri_mismatch" · My builder says the app is tested, but my customers hit problems
VibeFix is independent. Lovable, Bolt, Replit, Base44, v0, Supabase, Firebase, Stripe and Vercel are trademarks of their owners.
Want it fixed?
Our AI agent finds the cause, fixes it in your code and re-checks your live app. $79 for one bug, paid up front. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.