Custom domain returns ERR_CONNECTION_REFUSED although DNS and HTTPS are correctly configured

Support
1

Hello,Hello,

My custom domain is not loading and returns ERR_CONNECTION_REFUSED.

Domain:
ettileflershay dot comUpdate:

The Netlify subdomain works correctly:

However, the custom domain still does not load:
ettileflershay dot com
www dot ettileflershay dot com

So the deploy itself is working, but the custom domain routing still seems to be the issue.

Can someone from Netlify please check the custom domain routing or any stale/inactive DNS zone on Netlify’s side?

Site name:
resonant-tiramisu-2d73b5

Netlify subdomain:
resonant-tiramisu-2d73b5 dot netlify dot app

The Netlify subdomain works correctly, but the custom domain does not.

This is not a build issue. The site was deployed manually through Netlify Drop.

I am using external DNS through Namecheap BasicDNS, not Netlify DNS.

Namecheap support confirmed:

  • The domain is Active
  • The domain is not suspended
  • There is no registry hold
  • There is no clientHold
  • There is no verification lock
  • There is no domain-level block
  • The domain uses Namecheap BasicDNS

DNS records in Namecheap:
A Record:
Host: @
Value: 75.2.60.5

CNAME Record:
Host: www
Value: resonant-tiramisu-2d73b5 dot netlify dot app

There are no AAAA records in Namecheap, and there is only one A record for the apex domain.

In Netlify:

  • The site is published
  • ettileflershay dot com is set as the primary domain
  • www dot ettileflershay dot com redirects to the primary domain
  • HTTPS is enabled
  • The Let’s Encrypt certificate is active
  • The certificate includes both custom domains

The domain was previously suspended by Namecheap due to contact verification, but the registrant email was verified successfully and Namecheap confirmed the domain is now fully active with no remaining block.

Despite all this, the custom domain still returns ERR_CONNECTION_REFUSED.

Ask Netlify suggested checking:

  • DNS propagation
  • leftover AAAA records
  • multiple A records
  • an inactive or stale Netlify DNS zone

Can someone from Netlify please check whether there is an inactive or stale Netlify DNS zone, a backend routing issue, or anything that needs to be refreshed or re-provisioned on Netlify’s side?

Thank you.