Lovable custom domain on Namecheap: fix A and TXT verification

Short answer. Add the hostname at the service that publishes the site, then copy that project's records into the active DNS zone. Buying another name does not fix a verification error.

Convert your host's record to Namecheap fields

Use the records your host supplies. This formatter removes the DNS zone from a full owner name and preserves your value. Paste public DNS values only.

Use the right publishing route

In Lovable, open Project → Settings → Domains → Connect existing domain. Custom domains require a paid plan; publish the project before expecting it to serve your site. Choose the exact root or subdomain. Manual setup supplies an A record and an ownership TXT value. Copy both from your project.

For Namecheap, the root A owner becomes @. A full TXT owner such as _lovable.example.com becomes _lovable; for a subdomain, preserve the extra label, such as _lovable.blog. The formatter below converts only the owner name, never the supplied value.

Lovable also has an advanced CDN/reverse-proxy route. It supplies a project CNAME instead of the ordinary A/TXT setup. Follow the route actually selected in your project; do not mix its records with the standard flow. After DNS verification, check the domain reaches Live and HTTPS works.

Checked against the official setup instructions on 27 October 2026. Current instructions in your own project take priority.

Record exists, but the domain still fails?

Check the DNS troubleshooting sequence: active nameservers, exact owner name, duplicated domain suffix, host-required proxy mode, root versus www, then the host's binding and certificate. Keep email and unrelated records.