GitHub Pages custom domain TLS certificate stuck at "Authorization created"

[jackyshenfenghua]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Pages

Body

I am seeing what appears to be another instance of the recent GitHub Pages custom-domain TLS provisioning issue.

Repository and domain

Repository: jackyshenfenghua/fenghuashen.com

Custom domain: fenghuashen.com

The site is deployed successfully and works over HTTP, but GitHub Pages has not issued a TLS certificate for the custom domain.

Pages Settings remains at:

• DNS Check in Progress
• 1 of 3 — Certificate Requested: Authorization created
• Enforce HTTPS is unavailable

The Pages API reports:

status: built
cname: fenghuashen.com
protected_domain_state: verified
https_certificate.state: authorization_created
https_certificate.description: Authorization created
https_certificate.domains:
  - fenghuashen.com
  - www.fenghuashen.com
https_enforced: false

DNS and domain checks

I have verified the public DNS configuration:

• fenghuashen.com resolves to all four current GitHub Pages IPv4 addresses:
  • 185.199.108.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153
• www.fenghuashen.com is a CNAME to jackyshenfenghua.github.io
• No AAAA record is present
• No CAA record is present
• No DS record was found
• The repository CNAME contains exactly fenghuashen.com
• GitHub account-level domain verification has completed successfully and the domain is shown as Verified

HTTP requests to the apex domain return 200 OK from GitHub Pages, and www redirects to the apex domain over HTTP.

HTTPS currently presents GitHub's default *.github.io certificate, which does not contain fenghuashen.com, resulting in a hostname mismatch.

Troubleshooting already performed

I have already:

1. Verified the DNS records publicly.
2. Completed GitHub account-level domain verification.
3. Removed and re-added the custom domain once, following the GitHub Pages HTTPS troubleshooting guidance.
4. Left the DNS and Pages configuration unchanged since that retry.

Removing and re-adding restarted provisioning, but it became stuck again at authorization_created.

I also ran GitHub Support's "Troubleshoot Pages SSL issues" assistant, which confirmed that the domain is not currently presenting a valid SSL certificate.

Similar recent reports

Before posting, I searched the Community and found several recent reports describing very similar behavior, including domains stuck at new, authorization_created, or continuing to receive the default *.github.io certificate despite apparently valid DNS.

In particular, discussion #206108 documents multiple affected domains and includes cases stuck at authorization_created.

My domain appears to be another independent data point with the same general provisioning symptom.

Question

Is there anything else that can be corrected on my side, or does https_certificate.state: authorization_created indicate that certificate provisioning is now waiting on GitHub Pages infrastructure?

If someone from the Pages team is able to inspect the certificate provisioning state or queue for fenghuashen.com, that would be greatly appreciated.

For now I am leaving the DNS records and custom-domain configuration unchanged so that I do not restart the provisioning process again.

Thank you.