Free failure-moment diagnostic
Find why your custom domain, DNS, or SSL launch is stuck
Check the public signals that commonly block a custom domain on Lovable, Replit, Bolt.new, Vercel, Framer, Shopify, Netlify, and Webflow. You get observed evidence and a fix-first action list—not a generic score.
- Platform-aware DNS comparison
- HTTPS and redirect checks
- TXT, AAAA, duplicate A, and CAA diagnostics
Fix in dependency order
Do not wait for “propagation” before checking the records
- Confirm the platform deployment is published. A correct domain cannot repair an unpublished or failed deployment.
- Copy the exact dashboard values. Remove old or duplicate records only after confirming the required apex and www setup.
- Resolve verification and certificate blockers. TXT ownership, conflicting AAAA records, DNS proxying, DNSSEC, or CAA policy can delay activation.
- Test both HTTP and HTTPS. Choose one preferred hostname and redirect every alternate version to it.
- Then audit discoverability. A working domain still needs useful public pages, canonical URLs, crawl controls, sitemap coverage, and internal links.
Problem-specific guides
Continue with the guide for your builder
Domain Launch Doctor FAQ
Why is my custom domain not working?
Common causes include an incorrect apex or www record, an extra AAAA or A record, missing ownership TXT verification, a restrictive CAA policy, incomplete propagation, or a platform deployment that is not ready.
Can this tool see my hosting dashboard?
No. It observes public DNS and HTTP responses only. Project-specific values and private provisioning states must be verified in the hosting dashboard.
Does a passing result guarantee that SSL is finished?
No. A successful public HTTPS response is evidence that the checked hostname responded securely, but only the platform can confirm its internal certificate and domain state.