> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot domains

> Check custom-domain DNS records, verification and HTTPS, isolate hosting from authentication failures, and gather safe evidence for unresolved domain issues.

## Test the default published URL first

Open the app's `replit.app` URL and its custom domain. If both fail similarly,
start with [deployment troubleshooting](/help/troubleshooting/deployments).
If only the custom domain fails, continue below.

Identify where your domain's authoritative DNS is managed. Buying a domain from
one company does not necessarily mean that company hosts its DNS.

## Domain verification is pending or fails

1. Open **Publishing → Domains** and select the domain.
2. Compare the records shown by Replit with those at your authoritative DNS provider.
3. Check the record type, name, and value exactly. Do not reuse an IP address
   from another app or an old screenshot.
4. Check the apex domain and `www` separately. A record for one does not
   automatically configure the other.
5. Look for conflicting records at the same hostname. Preserve unrelated
   records, especially email and verification records.

Follow [Custom domains](/features/publishing/custom-domains) for the required
record types and provider-specific setup. If your provider offers proxying,
check that guide before enabling it.

DNS changes can take time to appear through caches. Record when you changed
the records and compare the public response with the intended configuration.
Repeatedly changing records makes the result harder to diagnose.

## HTTPS or certificate provisioning fails

Confirm that DNS points to the intended deployment and that domain verification
has completed. Check for conflicting records or provider proxy settings before
changing application code.

If verification is complete but certificate provisioning remains stuck,
contact Support with the hostname, record types, verification state, and time
of the last change. Do not disable HTTPS or certificate verification as a fix.

## The domain loads the wrong site

Check which project the domain is linked to and whether DNS still points to an
older host. Compare the apex and `www` responses. Before unlinking a live
domain, plan the change to avoid interrupting visitors.

## The site loads, but sign-in fails

This may be an auth-provider domain issue rather than hosting DNS.
Use the [authentication guide](/help/troubleshooting/auth) to identify your
provider and environment.

For “domain already in use” errors involving Clerk, do not delete the auth
application as a shortcut. Deletion can remove user accounts. Contact Support
for a managed integration or the provider for your own account.

## Domain registration or renewal questions

Connecting a domain and purchasing a domain are different operations. Consult
[Domain purchasing](/build/domain-purchasing) before changing renewal settings
or moving a registration. Do not assume unlinking a domain cancels its renewal.

## Details for Support

Include the hostname, project URL, DNS provider, exact error, last change time
and timezone, and whether the default published URL works. Share only relevant
DNS records; omit unrelated verification tokens and personal information.
See the [support checklist](/help/troubleshooting/overview#when-to-contact-support).