GitHub Pages custom domain stuck on DNS Check / HTTPS certificate not issued

[k4hvecii]

🏷️ Discussion Type

Bug

Body

Hello,
I’m having an issue with HTTPS certificate provisioning for my GitHub Pages custom domain.
Repository: k4hvecii/k4hvecii.github.io
Default Pages URL: https://k4hvecii.github.io
Custom domain: k4hveci.info
The default GitHub Pages site works correctly and all Pages deployments are successful.
DNS configuration:

• k4hveci.info A → 185.199.108.153
• k4hveci.info A → 185.199.109.153
• k4hveci.info A → 185.199.110.153
• k4hveci.info A → 185.199.111.153
• www.k4hveci.info CNAME → k4hvecii.github.io

The domain is also successfully verified under my GitHub account using the GitHub Pages verification TXT record.
Both authoritative DNS servers return the correct GitHub Pages IP addresses.
In Repository Settings → Pages, the DNS check sometimes shows DNS check successful, but after refreshing it returns to DNS Check in Progress.
Enforce HTTPS remains unavailable because GitHub says a certificate has not yet been issued for k4hveci.info.
GitHub’s Pages SSL troubleshooting assistant also reports that the domain is not replying with a valid SSL certificate.
This issue has persisted for more than 24 hours. I have already removed and re-added the custom domain once, verified the domain, and confirmed the DNS configuration.
Is the GitHub Pages DNS health check or TLS certificate provisioning for this domain stuck or failing?
Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐