Netlify Let’s Encrypt certificate provisioning fails despite successful DNS verification — unusual CAA response

Support
1

I’m trying to enable HTTPS for:

  • chasingshadowscomic.com
  • www.chasingshadowscomic.com

The website is hosted on Netlify at lambent-malabi-dfa9e4.netlify.app. DNS is managed by HostGator using hgns1.hostgator.com and hgns2.hostgator.com.

My DNS records are:

chasingshadowscomic.com      A       75.2.60.5
www.chasingshadowscomic.com  CNAME   lambent-malabi-dfa9e4.netlify.app.

Netlify reports “DNS verification was successful,” but provisioning fails with:

We could not provision a Let’s Encrypt certificate for your custom domain.

Netlify doesn’t show the underlying ACME error, and I don’t have access to its certificate-client logs.

Checks performed on September 14, 2026:

  • Both authoritative nameservers return the expected website records.
  • Google and Cloudflare DNS resolve both names correctly.
  • HTTP requests reach Netlify and serve the website.
  • HTTPS fails with a certificate hostname mismatch.
  • No root AAAA, restrictive CAA, or DS records were found.

One unusual result: querying either HostGator nameserver directly for www CAA records:

dig @hgns1.hostgator.com www.chasingshadowscomic.com CAA +norecurse

returns:

status: NXDOMAIN

ANSWER:
www.chasingshadowscomic.com. 14400 IN CNAME lambent-malabi-dfa9e4.netlify.app.

AUTHORITY:
netlify.app. 3600 IN SOA HGNS1.HOSTGATOR.com. root.HOSTGATOR.com. 126040501 10800 3600 604800 3600

Could this response interfere with Let’s Encrypt’s CAA checks or domain validation? What further diagnostics would distinguish a HostGator DNS problem from a Netlify provisioning issue?