Domain & Site Verification Master Checklist - LawtonChilesRedCrossClub/website GitHub Wiki
β Domain & Site Verification Master Checklist
This page ensures that after setup, renewal, or changes to DNS, the website is correctly configured with DNS, HTTPS, and DNSSEC enabled.
Domain: lchsredcross.org
Custom Domain: www.lchsredcross.org
Step 1 β Verify DNS Records
-
In Cloudflare β DNS:
- CNAME:
www β lawtonchilesredcrossclub.github.io
- A records (root):
β’@ β 185.199.108.153
β’@ β 185.199.109.153
β’@ β 185.199.110.153
β’@ β 185.199.111.153
- CNAME:
-
Use DNS Checker to confirm:
www.lchsredcross.org
β CNAME βlawtonchilesredcrossclub.github.io
lchsredcross.org
β resolves to GitHub IPs above
π If propagation is slow or results are inconsistent, read the π DNS Propagation Guide to understand why and what to do.
Step 2 β Verify HTTPS & GitHub Pages
- GitHub Repo β Settings β Pages β Custom Domain =
www.lchsredcross.org
- "Enforce HTTPS" is checked in GitHub Pages settings
- Visit https://www.lchsredcross.org β page loads with lock icon (π)
- Visit https://lchsredcross.org β redirects to
https://www.lchsredcross.org
Step 3 β Verify DNSSEC
- In Cloudflare β DNS β DNSSEC shows "Enabled"
- In Porkbun β Domain Management β DNSSEC β DS record saved
- Run test at DNSViz β enter
lchsredcross.org
- Confirm chain of trust is valid (green)
Step 4 β Device Testing
- Test site on desktop browser (Chrome/Firefox/Edge)
- Test site on mobile browser (Safari/Chrome)
- Verify navigation links and images load correctly
Step 5 β Documentation
- Update Domain Renewal Reminder Wiki page with:
- Date DNSSEC verified
- Date HTTPS verified
- Notes on any changes made
- Save screenshots or notes for future Web Team reference
π GitHub Pages Custom Domain Troubleshooting
If GitHub shows βDNS Check in Progressβ or HTTPS unavailable for more than 24 hours:
-
Check Cloudflare DNS
- Ensure CNAME
www
βlawtonchilesredcrossclub.github.io
exists. - Ensure root (
@
) A records β 185.199.108.153 / 109 / 110 / 111. - All records should be orange cloud (proxied).
- Ensure CNAME
-
Check Cloudflare SSL/TLS Settings
- SSL/TLS encryption mode = Full.
- Enable Always Use HTTPS.
- Enable Automatic HTTPS Rewrites.
-
Reset GitHub Custom Domain
- Repo β Settings β Pages β Remove custom domain.
- Re-add
www.lchsredcross.org
. - Save β GitHub re-triggers DNS check.
-
Wait for Certificate
- GitHub may take up to 24 hours to issue HTTPS certificate.
- Once available, check Enforce HTTPS in GitHub Pages.
-
Still failing?
- Test with DNS Checker.
- Read the π DNS Propagation Guide to confirm whether itβs just a delay.
- Open a GitHub Pages support ticket if DNS records are correct but verification fails.
π Final HTTPS Setup (Cloudflare + GitHub)
Before finishing verification, check both Cloudflare and GitHub settings:
In Cloudflare
- SSL/TLS β Encryption mode = Full
- Always Use HTTPS = ON
- Automatic HTTPS Rewrites = ON
In GitHub Pages
- Repo β Settings β Pages β Custom Domain =
www.lchsredcross.org
- Enforce HTTPS = checked
- Visit
https://www.lchsredcross.org
and confirm green lock (π)
β With both sides configured, your site is fully HTTPS-secured.
β Once all steps pass, your site will be live, secure, and using HTTPS.