Resolved — 4 November 2026

Both Pages DNS health checks now report is_valid: true with no error. The certificate is approved for sorog.net and www.sorog.net, and https_enforced is true. HTTPS works on the apex, and HTTP/www redirect to https://sorog.net/.

The full GitHub-hosted verification run passed: https://github.com/mrmahmd/sorog/actions/runs/41794505989

The initial problem and intermediate update below are retained for context.

Update — 4 November 2026, 07:44 UTC

GitHub has now approved the certificate for sorog.net and www.sorog.net. HTTPS enforcement is enabled. HTTPS on the apex returns 200 with a valid certificate; HTTP and www redirect to https://sorog.net/.

The full diagnostic workflow, including HTTPS certificate verification, now passes: https://github.com/mrmahmd/sorog/actions/runs/41794505989

The Pages DNS health endpoint still returned the earlier validation failure in the last check, so the remaining discrepancy concerns that health result rather than the live HTTPS site. The initial report below records the state before certificate approval.

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pages

Body

Repository: https://github.com/mrmahmd/sorog
Custom domain: sorog.net; alternate: www.sorog.net.
Pages source: main, /. Root CNAME contains only sorog.net.

Problem

Pages reports NotServedByPagesError for the apex and InvalidCNAMEError for www. The TLS certificate stays in state new, and HTTPS hostname verification fails.

DNS and routing

Both authoritative GoDaddy nameservers (ns11.domaincontrol.com, ns12.domaincontrol.com) return only these apex A records:

185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

www is a CNAME to mrmahmd.github.io.. No apex AAAA or CAA records are present.

From a GitHub-hosted Ubuntu runner, HTTP for the apex returns 200 with Server: GitHub.com; www returns 301 to the apex. HTTPS still serves a certificate that does not match sorog.net.

Official checker disagrees with Pages service

A GitHub Actions diagnostic installed GitHub's github-pages-health-check 1.19.2. For the apex, default/public/authoritative resolvers all return valid: true, served_by_pages: true, and https_eligible: true. For www, default/public resolvers return the same successful values. Direct dig queries to both authoritative servers confirm the correct www CNAME.

Evidence and full logs: https://github.com/mrmahmd/sorog/actions/runs/41792500352

The Pages REST health endpoint continues reporting both hosts invalid despite those results. The custom domain was already removed and re-added once; the certificate remains new.

Could someone from the Pages team investigate the discrepancy in the Pages service validation and the certificate provisioning request? I would like to keep hosting this site on GitHub Pages.