AI-built apps · November 2026
Short answer: a domain that will not go live is almost always one of three things: the records that point your domain at Lovable are missing or were entered in the wrong place, old records from your previous website are still there, or something sits in between (Cloudflare's proxy, or a rule about who may issue your security certificate). Lovable tells you which step it is stuck on; four free checks, about ten minutes, show you the rest. Then find your case in the seven causes below.
A few words first. Your domain's DNS records are the public
entries that say where the domain points. An A record points a name at a server, a
TXT record proves the domain is yours, and the SSL certificate is what makes
https:// work.
A, AAAA and TXT results line by line. Anything extra counts as
much as anything missing.yourdomain.com,
www.yourdomain.com and the app's your-app.lovable.app address. If the
lovable.app address is broken too, the domain is not your problem:
a blank page after publishing has six usual causes.| What you see | What it means | What to do |
|---|---|---|
| Setting up domain | Lovable is preparing the connection, checking records or issuing the certificate. | Read the progress line under it. If "Set up DNS" appears, the records are not there yet. |
| Looking for your DNS records | Lovable cannot find the records it asked for. | Causes 2, 3 and 4. |
| DNS records found, waiting for them to take effect | The records are right; other networks have not caught up. | Wait. Lovable says most changes are live within a few hours and it can take up to 72. |
| Finishing up, for a long time | The last step is the SSL certificate. | Cause 5. |
| Active, but the site is not there | The connection is done. The app still has to be published, and stray records can still send visitors elsewhere. | Causes 1 and 3. |
| Needs attention, or a warning under the domain | Lovable found a connection problem; the warning names it. | Follow the warning, then "Check again" in the three dots menu. |
| Domain Service Error | The setup window (a service called Entri) did not load. No record was changed. | Turn off the ad or script blocker for Lovable, or choose "Setup instructions" and enter the records yourself. |
lovable.app address.
@, left blank, or typed out in full; Lovable's page names Amazon Route 53 as one that
wants it blank or typed out. Or the proof record was cut short: it is a TXT record on the name
_lovable (for a subdomain, _lovable.blog) whose value starts with
lovable_verify=, and the whole value has to be there.
www each have their own records; if Lovable lists an
AAAA record, add that too. Then choose "Check again".A or
AAAA record can send visitors to the wrong place even when the domain shows Active, and that
some providers add an AAAA record to a new domain by themselves; visitors whose devices prefer
that newer kind of address then reach it instead of your app. "It works on my laptop and not on my phone" is
a reason to look here first.
A, AAAA or CNAME record on the same name. Leave
everything else alone, above all the MX records: those carry your email.CNAME record that points at the app's published address, so publish first. In
that setup, by Lovable's own words, the proxy is yours to configure and Lovable does not check it.CAA records, a list
of which certificate companies may issue certificates for it, and none of the ones Lovable uses is on the
list. A subdomain inherits the list of the domain above it.
CAA records of your domain (the same lookup site
shows them). If there are any, add the three Lovable names, or at least one:
0 issue "pki.goog", 0 issue "letsencrypt.org", 0 issue "ssl.com". If
you cannot change the main domain's list, add the records on the subdomain you are connecting. Then "Check
again". No CAA records at all is fine: then any company may issue.yourdomain.com opens and
www.yourdomain.com does not, or the other way round. They are two separate names with their own
records. When you connect a root domain, Lovable offers to connect www as well and send its
visitors on; if that was switched off, or only one set of records was entered, some of your visitors get an
error.
lovable.app
address, or the customer comes back from Stripe to the old address. Nothing is wrong with the domain here:
other services still have the old address written down. This one is from our own engineering practice, not
from Lovable's domain page.
Sources, read November 22, 2026: Lovable's documentation, Set up a custom domain, Connect a domain from another provider and Publish, for the statuses, the records, the Cloudflare and certificate notes, the waiting times and the redirects. Lovable changes these pages; check them for your own case. Cause 7 and the advice under "Before you change the records again" are from engineering practice. This is a checklist, not a study: we have not counted how often each cause happens. Other pages on this site: not sure what is broken? A ten-minute check. Moving a Lovable or Bolt app to Vercel or Netlify. Six security checks. Lovable to WordPress. Convert a Lovable app to iOS. Slow on phones? Our demo shop, measured before and after. Urgisoft is not affiliated with Lovable, Cloudflare, Supabase, Stripe or Google.
We find which record or setting is stopping your domain and give
you the exact records to enter at your provider, and in the app's own code we fix what still names the old
address: sign-in, emails, payment return pages. Then we show you the domain answering, with and without
www. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from
$150. No fix, no charge. We work through GitHub or as a collaborator you invite; we never ask for your
password, not for Lovable and not for your domain provider.