Lovable custom domain stuck on Verifying? It is almost always one of five DNS or auth settings

Your Lovable custom domain is not working: it sits on Verifying, the browser shows a security warning, it loads your old website, or the site works but login fails. From the guide: "Almost every case is one of five DNS or auth settings, and Lovable's domain status tells you which one."

Open Project settings, Domains, read the status next to the domain, then fix the matching cause.

The records Lovable expects

For a domain bought elsewhere and connected with manual setup, Lovable gives you two records:

• A record on @: 185.158.133.1
• TXT record on _lovable: lovable_verify=...

Then check that nothing else is fighting them: no AAAA record on that host, no leftover A or CNAME from your old host, and no CAA record that blocks Lovable's certificate authorities.

Stuck on "Verifying" or "Unable to verify"

Lovable cannot see the records it asked for yet. In order of how often it shows up:

• The A record is proxied. In Cloudflare, an orange-cloud A record hides Lovable's IP. From the guide: "Lovable's docs say that while verification is in progress you should not enable proxying on the A record or point it at a CDN. Switch it to DNS only (grey cloud)."
• The TXT value is cut off or on the wrong host. The host is _lovable and the whole lovable_verify= value has to be there.

A couple of other notes from the guide: custom domains need a paid Lovable plan, and the project has to be published before the domain serves anything.

If login breaks on the new domain

Adding a domain does not update Supabase Auth. Your new URL has to be in the Supabase redirect URL list too, or sign-in loops back to the old host.

Full guide with all five causes and the record table: fixloop.dev/guides/lovable-custom-domain-not-working. Stuck on it right now? Paste the error at fixloop.dev/start and we will email the likely cause within 24 hours, free. (I run FixLoop.)