QAlaunch

Replit custom domain not working: verifying, failed and SSL fixes

A Replit custom domain needs both the A record and the TXT record that Publishing > Domains shows you, added at the same time, with no other A or AAAA records on that hostname. Replit checks for them for about six hours after you add the domain; if they are not found in that window it marks the domain Failed and stops checking. Correct the records, set Cloudflare to DNS only, allow Let’s Encrypt in any CAA record, then remove and re-add the domain once.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

In Publishing > Domains the domain sits on Verifying for hours, then switches to Failed. Or it verifies, but the browser shows a certificate warning, the old website still appears, or the bare domain works while www does not.

Why it happens

1. Only one of the two records was added

Replit needs the A record to route traffic and the TXT record to prove you own the domain. Both are required for SSL, so adding just the A record leaves the domain stuck.

2. Conflicting records on the same name

An old A record from your previous host, or an AAAA (IPv6) record on the same hostname, sends some visitors and the certificate check somewhere else. Replit’s docs say to remove them so only one A record points to Replit at the root.

3. Cloudflare proxy or a CAA record blocks the certificate

With Cloudflare’s orange-cloud proxy on, Replit cannot complete certificate issuance. A CAA record that allows only another certificate authority blocks Let’s Encrypt, which Replit uses.

4. The records arrived after the checking window

Replit checks every minute or two for about six hours. If DNS was added later, or propagated slowly, the domain is marked Failed even though the records are now correct.

How to fix it

  1. In Replit open Publishing > Domains, select the domain or Connect your own domain, and copy the exact A record value and TXT record shown. Confirm current values there or in Replit’s custom domain docs rather than from an old tutorial.
  2. At your DNS provider, add the A record for the root (@) and the TXT record together. Delete any other A records and any AAAA records on the same hostname.
  3. If your DNS is on Cloudflare, click the cloud icon on the A record so it shows grey, DNS only.
  4. If the domain has CAA records, add one that allows letsencrypt.org.
  5. Check propagation with a public DNS lookup tool or dig yourdomain.com A and dig yourdomain.com TXT, and confirm they return the Replit values.
  6. If the domain already shows Failed, remove it in Publishing > Domains and add it again once. Avoid repeated reconnects: each one requests a new certificate and Let’s Encrypt limits how many can be issued.
  7. Connect www separately if you want it, because Replit does not issue wildcard certificates; each subdomain is its own connection.

How to check it's fixed

  • Publishing > Domains shows the domain as verified with no warning.
  • Both https://yourdomain.com and, if connected, https://www.yourdomain.com open the published app in a private window with a valid padlock.

What a QAlaunch scan shows for this

  • The page failing to load over HTTPS, or loading content from the old host, on the scanned domain.
  • HTTPS and security header results from the response once the certificate is in place.
  • Running the scan on both the bare domain and www shows whether one of them is not yet pointed at Replit.

See exactly what a full report contains in the sample report.

Frequently asked questions

How long does Replit domain verification take?

If the records are already in place, often minutes. DNS changes can take up to 48 hours to spread, but Replit only checks for about six hours, so add both records before connecting the domain if you can.

Can I use a CNAME for the root domain?

No. Replit’s docs say apex CNAMEs are not supported, so the root needs the A record. Subdomains follow the record type Replit shows for them.

I bought the domain through Replit and it still fails. What now?

Replit manages DNS for domains bought through it, so you cannot fix the records yourself. Replit’s docs say to contact Replit Support in that case.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Replit-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Replit: all Replit fixes · Replit testing

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Replit docs: custom domains and DNS · Replit forum: custom domain not verifying · Replit forum: verifying a domain takes time