Lovable custom domain stuck on Verifying or Unable to verify
Your Lovable custom domain sits on Verifying or shows Unable to verify? Lovable can't see its A and TXT records yet. Fix the records, turn off proxying, and recheck.
Short answer
Verifying means Lovable can't see your DNS records yet, and Unable to verify means verification did not finish within one hour. At your DNS provider, point the A record at 185.158.133.1, add the full lovable_verify= value as the TXT record at _lovable, turn off proxying, and delete any AAAA records. Then click Check status in Project → Settings → Domains.
Reviewed October 25, 2026
Not sure which status you have? Start at Lovable custom domain not working.
What it means in plain English
Lovable shows Verifying while it is "waiting for DNS records to propagate." Unable to verify means "DNS verification did not complete within one hour. This usually means your DNS records are incorrect or still propagating."
This applies to a domain you bought somewhere else and connected to Lovable. Lovable checks two records at your DNS provider:
- An
Arecord that "points your domain to Lovable's edge IP address185.158.133.1." - A verification
TXTrecord with the host_lovablefor a root domain, or_lovable.plus the subdomain for a subdomain (for example,_lovable.blog), and "a value starting withlovable_verify=."
Lovable says DNS changes "may take up to 72 hours to propagate, though most updates are live within a few hours."
Likely causes
- The
TXTvalue was cut off or mistyped. For both statuses, Lovable says to check the records "especially the full TXT value." - Proxying is on for the
Arecord, or the record points at a CDN or reverse proxy. Lovable says that if either happens during manual setup, "the domain remains in the Verifying state." - The provided
Arecord was changed before verification finished. - The host name field is in the wrong format for your provider. Lovable says it may need to be
@, left blank, the domain name, or the subdomain label. Amazon Route 53 needs it left blank or set to the domain name. - An
AAAArecord exists for the domain. Lovable's prerequisites say there must be none, because it "can interfere with domain setup." - DNS is still propagating.
How to fix it, step by step
- Go to Project → Settings → Domains and confirm the exact records Lovable expects. If the domain shows Action required instead, click Complete setup first.
- At your DNS provider, check the
Arecord points to185.158.133.1. Check theTXTrecord at_lovable(or_lovable.yoursub) holds the fulllovable_verify=value. - If your DNS is on Cloudflare or a similar service, set the
Arecord to DNS only. Lovable's fix: "Disable proxying (DNS-only) on the providedArecord" and "Ensure theArecord points directly to Lovable's IP address." - Delete any
AAAArecords for the host you are connecting. - Fix the host name format if your provider needs
@, a blank field, or the full domain. - Click Check status to re-verify. You can also ask Lovable in the project chat about the domain. Lovable says it reports "which DNS records it expects and whether it can see them, and whether the project is published."
- Use a DNS lookup tool such as dnschecker.org to confirm the records resolve. If nothing changes after propagation, Lovable suggests removing and re-adding the domain in Project → Settings → Domains.
- If you want to keep Cloudflare's proxy on permanently, reconnect the domain with Advanced → Uses Cloudflare or similar proxy. In proxy mode, Lovable gives you a
CNAMErecord pointing to your project'slovable.appURL instead of theArecord, and needs no verificationTXTrecord. Lovable then does not configure, validate, or monitor your proxy setup.
How to check it worked
- The status moves past Verifying to Setting up, then Live.
- If it stops at Setting up, Stalled, or Failed, verification passed and the SSL certificate is the problem. See Lovable domain stuck on Setting up, Stalled, or Failed.
- Once Live, the site loads at your domain over
https. If login then fails on the new domain, see Lovable sign-in works in preview but fails when published.
If the domain is proxied through Cloudflare and shows Error 526, see Cloudflare invalid SSL certificate (Error 526).
Questions people ask
How long does Lovable domain verification take?
Lovable says DNS changes may take up to 72 hours to propagate, though most updates are live within a few hours. Unable to verify appears when verification did not complete within one hour.
Can I keep Cloudflare proxying on with a Lovable domain?
Not during manual setup. Lovable says a proxied A record keeps the domain in Verifying. To keep the proxy on, reconnect with Advanced → Uses Cloudflare or similar proxy, which uses a CNAME record instead of the A record.
What is the 185.158.133.1 IP address in my DNS settings?
Lovable says that is its own server, not a previous host. Your A record should point to it.
Sources
Related fixes
More Custom domains fixes
More Lovable fixes
Keep going on your own.
The guides stay free. A deep leak report is $15. Fix packs are $24, or $49 for all three. There is no done-for-you repair.