Cloudflare Pages + Custom Domain

Scope / Objective

Dependencies / Preconditions

Change plan

1. Create/update static site content in GitHub repo (index.html at repo root).
2. Create Cloudflare Pages project from Git repository and deploy.
3. Add custom domains in Pages: apex + www.
4. Ensure Cloudflare DNS has required web CNAMEs (proxied) without disturbing mail records.
5. Validate via Cloudflare UI + DoH JSON checks + browser proof.
6. Capture evidence pack artifacts and hashes.

Implementation steps

1) Prepare repository (static site)

1. Confirm repo exists and contains /index.html at repo root.
2. Commit and push to main (prefer PR workflow if using governance controls).

2) Create Cloudflare Pages project (Git-connected)

1. Cloudflare Dashboard → Workers & Pages → Pages → Create application → Connect to Git.
2. Select the repo (GIT-MT-01 / MT-WEB-01).
3. Set build config:
   • Production branch: main
   • Framework preset: None
   • Build command: (blank)
   • Build output directory: .
4. Click Save and Deploy.

3) Bind custom domains in Pages

1. Pages Project → Custom domains → Set up a custom domain.
2. Add apex: mtinfrasolutions.com → proceed.
3. Add www: www.mtinfrasolutions.com → proceed.
4. If Cloudflare requests DNS changes, apply them (see DNS mapping below).
5. Wait until both domains show Active with SSL enabled.

4) Confirm Cloudflare DNS records (authoritative zone)

1. Cloudflare zone mtinfrasolutions.com → DNS → Records.
2. Verify the two web records exist and are proxied. Do not modify Proton Mail records.

5) Optional: redirect www → apex (canonical host)

1. Cloudflare zone → Rules → Redirect Rules → Create rule.
2. Match: Hostname equals www.mtinfrasolutions.com
3. Redirect: https://mtinfrasolutions.com/$1 (301)

Validation (with exact commands)

A) Cloudflare UI

• Pages → Custom domains: apex + www = Active (SSL enabled)
• Zone → DNS → Records: web CNAMEs present; mail records unchanged

B) External DNS checks via DoH (PowerShell)

$domain   = "mtinfrasolutions.com"
$BasePath = "$env:USERPROFILE\Documents\MTINFRA-EvidencePack"

# Apex A (post)
$Apost = Invoke-RestMethod -Uri ("https://cloudflare-dns.com/dns-query?name=$domain&type=A") -Headers @{ accept="application/dns-json" }
$Apost | ConvertTo-Json -Depth 10 | Out-File (Join-Path $BasePath "EV-41-A-DoH-Post.json") -Encoding utf8

# www CNAME (post)
$WWWpost = Invoke-RestMethod -Uri ("https://cloudflare-dns.com/dns-query?name=www.$domain&type=CNAME") -Headers @{ accept="application/dns-json" }
$WWWpost | ConvertTo-Json -Depth 10 | Out-File (Join-Path $BasePath "EV-42-WWW-CNAME-DoH-Post.json") -Encoding utf8

C) HTTP HEAD checks (PowerShell)

Invoke-WebRequest -Uri "https://mtinfrasolutions.com" -Method Head | Select-Object -ExpandProperty StatusCode
Invoke-WebRequest -Uri "https://www.mtinfrasolutions.com" -Method Head | Select-Object -ExpandProperty StatusCode

D) Browser proof

• Open https://mtinfrasolutions.com and confirm expected page content.

Rollback plan

1. Cloudflare Pages → Project → Custom domains: remove www and apex domain bindings.
2. Cloudflare zone → DNS → Records: remove web CNAMEs:
   • CNAME @ → mt-web-01.pages.dev
   • CNAME www → mt-web-01.pages.dev
3. Confirm Proton Mail records still exist (MX/SPF/DKIM/DMARC).
4. Validate: DoH queries should no longer resolve web hostnames; mail should remain functional.

Evidence pack checklist

Final state