HHostWithSheryWebsite & Domain Troubleshooting ToolsCheck a domain
Menu
Provider repair guideReviewed 2026-08-07By HostWithShery technical editorial

Fix a Netlify custom domain that is not working

Verify the domain assignment, DNS target and HTTPS state before changing nameservers.

Start with evidence from your own domain before changing DNS, SSL or mail settings.
Check your own configuration

SSL Certificate Checker

This page is preconfigured with the SSL Certificate Checker that best matches this problem.

No accountPublic evidence only
Live public check
No account · Public configuration only
On this page

Fix a Netlify custom domain that is not working: when this repair path applies

Verify the domain assignment, DNS target and HTTPS state before changing nameservers. Use these steps when external DNS or domain assignment does not match the Netlify site, but first run the embedded diagnostic so the TLS, certificate and HTTPS evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.

Find the authoritative setting before editing

Netlify Domain management/DNS together with the external registrar or DNS provider when Netlify DNS is not authoritative. For Fix a Netlify custom domain that is not working, confirm the active nameservers and exact service owner before changing check domain in Netlify. A DNS-looking screen at netlify has no public effect when another provider is authoritative for the zone.

Evidence to save for Fix a Netlify custom domain that is not working

Record the current public state for check domain in Netlify, verify A/CNAME target, remove conflicts. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.

  • Check domain in Netlify — Verify check domain in Netlify from the public Internet and compare it with the value the responsible provider says should be live.
  • Verify A/CNAME target — A CNAME aliases one hostname to another. Confirm the alias target is the provider-assigned hostname and that no conflicting address record exists at the same owner name.
  • Remove conflicts — Verify remove conflicts from the public Internet and compare it with the value the responsible provider says should be live.
  • Wait for certificate issuance — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.

Repair steps in netlify

Verify the domain assignment, DNS target and HTTPS state before changing nameservers.

  • 1. Check domain in Netlify. After this step, check the public value tied to check domain in netlify before changing another unrelated setting.
  • 2. Verify A/CNAME target. After this step, check the public value tied to verify a/cname target before changing another unrelated setting.
  • 3. Remove conflicts. After this step, check the public value tied to remove conflicts before changing another unrelated setting.
  • 4. Wait for certificate issuance. After this step, check the public value tied to wait for certificate issuance before changing another unrelated setting.

Why this order matters for netlify

The sequence begins with the provider/authority decision, then moves through check domain in Netlify, verify A/CNAME target, remove conflicts. That keeps the change scoped to the failed TLS, certificate and HTTPS path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.

Verify Fix a Netlify custom domain that is not working

HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. Compare the same check domain in Netlify and verify A/CNAME target evidence used before the change; a repair is complete when the public result agrees, not merely when the netlify interface reports that a save succeeded.

If netlify and the public result disagree

Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting check domain in Netlify value to force validation.

Mistakes to avoid for this repair

Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix a Netlify custom domain that is not working should change only the settings required by this diagnosis.

Technical references

These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.