Replit Custom Domain Not Working: Diagnose the Exact Blocker
A Replit custom domain can fail even when the app works on its Replit URL because domain ownership, DNS routing, proxy behavior, and production publishing are separate systems.
Open the custom-domain instructions for the published Replit app and copy the exact A and replit-verify TXT values into your DNS provider. Keep one Replit-required apex A record, remove conflicting AAAA or old-host records, and use DNS-only mode if Cloudflare proxying is enabled. Replit says the verification TXT record should remain in place and that DNS changes can take up to 48 hours, but first confirm the public records actually match the dashboard.
This guide separates a Replit publishing failure from a domain-routing failure. It explains the apex and subdomain setup, permanent ownership TXT record, duplicate A and AAAA conflicts, Cloudflare proxy behavior, propagation, HTTPS validation, preferred-host redirects, and the discoverability checks that follow a successful connection.
Quick Questions
The public A or replit-verify TXT value may differ from the project instructions, may be published on the wrong hostname, or may be hidden behind an incompatible proxy setup.
No. Replit’s current documentation says the replit-verify TXT record is permanent and should not be deleted after verification.
Replit’s manual setup guidance says to remove AAAA records when using its custom-domain configuration unless the project dashboard explicitly instructs otherwise.
Replit domain evidence table
Use the observed symptom to choose the next check instead of repeatedly deleting and re-adding the domain.
- Verification pending: compare the exact replit-verify TXT value and hostname
- Some visitors reach the old site: look for duplicate A or conflicting AAAA records
- Replit URL works but custom host does not: verify the project-specific A record and DNS proxy mode
- Apex works but www fails: connect www as its own hostname
- DNS matches but HTTPS fails: read the platform domain status and retry after validation completes
See which AI crawlers actually reach your website.
Track visits from GPTBot, ClaudeBot, PerplexityBot, search bots, and other discovery agents-then see which public pages attract their attention.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
Main Explanation
Start by proving that the Replit deployment itself works. Open the published Replit URL in a private window, refresh the homepage, and test the production path that should appear on the custom domain. If the deployment returns a build error, health-check failure, or 404, DNS is not the first problem. Repair publishing before changing registrar records.
Next, open the custom-domain panel for that exact deployment. Replit generates the records needed for the hostname you are connecting. For an apex domain, the setup normally includes one A record and a TXT value beginning with replit-verify=. Do not copy another project’s IP or verification token. A valid-looking record from an old tutorial can still point to the wrong deployment.
Check the hostname field carefully at the DNS provider. Providers often represent the apex as @, while a subdomain such as www needs its own host entry. Replit treats each hostname separately, so connecting example.com does not automatically prove that www.example.com is configured. Decide which version will be primary, connect the required hostnames, and redirect the alternate version when the platform supports it.
Remove conflicts only after identifying them. Replit’s current manual instructions call for a single A record and no AAAA record for this setup. Extra A records can send different visitors to different servers, while an old AAAA route can send IPv6 traffic away from Replit. Also remove a legacy CNAME on the same hostname because DNS providers cannot normally serve a CNAME alongside A and TXT records at one name.
If the DNS is managed by Cloudflare, set the Replit routing record to DNS only while connecting the domain. A proxied record returns Cloudflare addresses to public resolvers rather than the underlying destination, which can interfere with platform validation or make a public checker unable to confirm the Replit route. Public DNS alone cannot always prove proxy state, so inspect the cloud icon in Cloudflare directly.
Keep the verification TXT record after the domain becomes active. Ownership validation is not the same as traffic routing: the A record directs visitors, while the TXT value proves control of the hostname. Check both in public DNS. Replit notes that propagation may take up to 48 hours, but waiting will not correct a typo, duplicate record, wrong hostname, or proxied value.
Then test HTTPS as a visitor. Request both http and https versions of the apex and www hostnames. The preferred host should return the app securely, and alternatives should end on that same HTTPS version. If DNS is correct but HTTPS remains unavailable, use the Replit dashboard status and support evidence; a public test cannot see the private certificate queue.
After recovery, update canonical tags, OAuth callbacks, email links, analytics, sitemap URLs, and Search Console properties that still use the Replit preview address. Run the Domain Launch Doctor for public DNS and HTTPS evidence, then use the full TruboRankAI scan for robots, sitemap, page content, AEO, GEO, and AI-crawler readiness. A connected domain is necessary infrastructure, not a promise of indexing or traffic.
Practical Steps
- Verify that the published Replit deployment works.
- Copy the exact A and replit-verify TXT records from that deployment.
- Publish each apex or subdomain value on the correct hostname.
- Remove conflicting extra A, AAAA, or legacy CNAME records.
- Use DNS-only mode during validation when Cloudflare manages DNS.
- Keep the verification TXT record permanently.
- Test apex, www, HTTP, HTTPS, and the preferred-host redirect.
- Update discovery files and callbacks to the final canonical domain.
Stop guessing whether AI crawlers see your best pages.
Use crawler activity as an early discovery signal, identify pages that receive attention, and find important pages that may need a clearer path.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
Turn AI crawler visits into a repeatable visibility workflow.
Monitor discovery over time, compare activity across important pages, and use the evidence to decide what deserves attention next.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
FAQ
How long does a Replit custom domain take?
Replit says DNS changes can take up to 48 hours. Confirm the exact public A and TXT records first because propagation cannot fix incorrect values.
Why does Replit show the domain but the site still fails?
Ownership verification, DNS routing, deployment health, and HTTPS provisioning are separate stages. Test the published app and public records independently.
Do I need separate records for www?
Yes when you want www to work. Replit documents connecting each subdomain separately, so configure it and then choose one preferred host.
Sources and methodology
The troubleshooting order combines Replit’s current manual custom-domain and publishing documentation with observable DNS and HTTP dependencies. Sources and platform rules were reviewed on 2026-08-16. Project-specific dashboard values override examples, and no passing check guarantees indexing, rankings, referrals, or certificate completion.
These references support the changeable facts and study findings discussed above. Results depend on each source's sample, date, market, query set, and measurement method.