GitHub Pages custom domain stuck on DNS Check in Progress — HTTPS certificate not provisioned

[9718352-cmd]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Pages

Body

Hello,

I need help diagnosing a GitHub Pages custom domain that remains stuck on “DNS Check in Progress”.

Repository:
https://github.com/9718352-cmd/artemiy-k-site

Custom domain:
artemiy-k.ru

What I expected:
The DNS check should complete, GitHub should provision an HTTPS certificate, and the “Enforce HTTPS” option should become available.

What actually happened:
The site is published and works over HTTP, but the GitHub Pages settings continue to display “DNS Check in Progress”.

The “Enforce HTTPS” option is disabled with the message:
“Unavailable for your site because your domain is not properly configured to support HTTPS”.

Opening https://artemiy-k.ru/ produces:
NET::ERR_CERT_COMMON_NAME_INVALID

Checks already completed:

• All four A records point to GitHub Pages:
  185.199.108.153
  185.199.109.153
  185.199.110.153
  185.199.111.153
• The www CNAME points to 9718352-cmd.github.io.
• No conflicting AAAA records were found.
• No restrictive CAA records were found.
• The repository contains a CNAME file with artemiy-k.ru.
• The site is deployed successfully from the main branch, root directory.
• I have already removed and re-added the custom domain once.

The problem has persisted for approximately 24 hours after the latest changes.

Could someone help identify why the DNS check does not complete and whether HTTPS certificate provisioning is stuck?

Thank you.

[Simo-J-E]

Your DNS looks correct, so try removing the custom domain from GitHub Pages, add it again and wait up to 24 hours since this restarts the HTTPS certificate provisioning.

[9718352-cmd]

Thank you for your reply. I have already removed and re-added the custom domain once, then waited approximately 24 hours. Unfortunately, the status is still “DNS Check in Progress”, “Enforce HTTPS” remains unavailable, and HTTPS still returns NET::ERR_CERT_COMMON_NAME_INVALID.
Is there another way to diagnose or restart certificate provisioning without repeating the same procedure?

[hshm0799-max]

Full blank website show