Cloudflare Pages · Custom Domain
Configure cruise-crews.com
Step by Step
Follow these 9 steps to attach your custom domain to Cloudflare Pages, enable HTTPS, and confirm everything is working using the live diagnostics tool.
App built & deployed
All files published via the Publish tab
Domain registered
cruise-crews.com must be registered at any registrar (Namecheap, GoDaddy, etc.)
Cloudflare account
Free account at cloudflare.com — no credit card needed
~15 min total
Most steps take under a minute; DNS can propagate in 5–60 min
1
Publish the App from GenSpark
Deploy all project files to get a live *.pages.dev URL
Before attaching a custom domain you need a live Cloudflare Pages deployment. This happens through GenSpark's Publish tab.
1
In the GenSpark editor, click the Publish tab (top-right area of the interface).
2
Click "Publish Project" or "Deploy". GenSpark will bundle all your files and push them to Cloudflare Pages automatically.
3
Wait 30–60 seconds. When complete you'll receive a public URL like:
Copy this URL — you'll need it in Step 4.
cruise-crews-abc123.pages.devCopy this URL — you'll need it in Step 4.
4
Open the URL in a new tab and confirm the app loads correctly (splash screen → neon purple UI).
Your
*.pages.dev URL is your fallback URL — it always works even after adding a custom domain.2
Log In to Cloudflare
Access your Cloudflare dashboard and add cruise-crews.com
You need a Cloudflare account with your domain added. If you registered the domain elsewhere (GoDaddy, Namecheap, etc.), that's fine — Cloudflare will manage the DNS.
1
Go to dash.cloudflare.com ↗ and sign in (or create a free account).
2
Click "Add a Site" on the dashboard home page.
3
Enter
cruise-crews.com and click Continue.4
Select the Free plan and click Continue. Cloudflare scans your existing DNS records automatically.
5
Review the imported DNS records. Click Continue to activation.
Already added? If cruise-crews.com is already in your Cloudflare account, skip directly to Step 3.
3
Open Your Cloudflare Pages Project
Find the Pages project where Cruise Crews was deployed
Navigate to your Cloudflare Pages project to manage custom domains.
1
In the Cloudflare dashboard, click Workers & Pages in the left sidebar.
2
Under the Pages tab, find your project — it will be named something like
cruise-crews or the name GenSpark assigned it.3
Click on the project name to open it.
4
Click the Custom domains tab at the top of the project page.
Deployments
Functions
Custom domains
Settings
No custom domains yet
+ Set up a custom domain
4
Add cruise-crews.com as a Custom Domain
Tell Cloudflare Pages to serve the site on your domain
This is where you link your custom domain to the Pages project. Cloudflare will automatically create a CNAME DNS record pointing your domain to the Pages URL.
1
On the Custom domains tab, click "Set up a custom domain".
2
In the input field, type exactly:
cruise-crews.com — then click Continue.3
Cloudflare will show you a DNS record to add. It looks like this:
| Type | Name | Content |
|---|---|---|
| CNAME | cruise-crews.com | cruise-crews.pages.dev |
4
Click "Activate domain". Cloudflare will add this DNS record automatically if the domain is already in your Cloudflare account.
5
Also add
www.cruise-crews.com as a second custom domain (repeat steps 1–4 with www.cruise-crews.com) so both www and non-www work.Domain not in Cloudflare yet? If you get an error saying the domain isn't found, complete Steps 5 first (add nameservers at your registrar), then come back here.
5
Update Nameservers at Your Registrar
Point your domain to Cloudflare's DNS servers
This is the most important step. You need to tell your domain registrar (where you bought the domain) to use Cloudflare's nameservers. Until this is done, nothing else works.
Go to Cloudflare Dashboard → cruise-crews.com → Overview. You'll see two nameserver values assigned specifically to your account — copy them from there.
Your Cloudflare Nameservers (example — get yours from Cloudflare)
arya.ns.cloudflare.com
josh.ns.cloudflare.com
⚠️ Your actual nameservers will be different — find them in Cloudflare Dashboard → cruise-crews.com → Overview → Nameservers section.
1
Log in to your domain registrar (GoDaddy, Namecheap, Google Domains, Porkbun, etc.).
2
Find DNS Management or Nameservers settings for
cruise-crews.com.3
Choose "Custom nameservers" or "Use custom DNS".
4
Delete any existing nameservers and enter both Cloudflare nameservers (one per field).
5
Save the changes. Propagation typically takes 5 – 60 minutes (sometimes up to 24 hours).
Quick guide by registrar
Namecheap
Domain List → Manage → Nameservers → Custom DNS → enter both NS values
GoDaddy
My Products → DNS → Nameservers → Change → Enter My Own Nameservers
Google Domains / Squarespace
DNS → Custom nameservers → switch from Default Google to custom
Porkbun
Domain → Authoritative Nameservers → edit both NS1 and NS2 fields
Propagation takes time. After saving, wait at least 10 minutes before proceeding. You can check progress at dnschecker.org ↗ — look for Cloudflare NS records appearing globally.
6
Verify DNS Records in Cloudflare
Confirm CNAME records are correct and the proxy is on
After nameservers propagate, check that the correct DNS records exist in Cloudflare and the proxy (orange cloud) is enabled.
1
In Cloudflare Dashboard, click cruise-crews.com → DNS → Records.
2
Confirm these records exist (Cloudflare Pages added them automatically in Step 4):
| Type | Name | Content / Target | Proxy |
|---|---|---|---|
| CNAME | cruise-crews.com | cruise-crews.pages.dev | ☁️ Proxied |
| CNAME | www | cruise-crews.com | ☁️ Proxied |
3
If the proxy icon shows a grey cloud (DNS only), click the record → Edit → toggle the Proxy status to Proxied (orange cloud). This enables DDoS protection, CDN, and HTTPS.
4
If a record is missing, add it manually using the + Add record button with the values from the table above.
With the proxy on, your site gets: automatic HTTPS, CDN caching, DDoS protection, and the CF-Ray header on every response.
7
Enable HTTPS, HSTS & Always-Use-HTTPS
Force all traffic to use encrypted HTTPS connections
Cloudflare provides free SSL. Configure it correctly for the strongest security and to ensure the Service Worker (required for PWA) registers without errors.
Path: Dashboard → cruise-crews.com → SSL/TLS
1
SSL/TLS encryption mode — click SSL/TLS → Overview and set mode to Full (strict). This encrypts traffic end-to-end.
2
Always Use HTTPS — click SSL/TLS → Edge Certificates → toggle "Always Use HTTPS" to ON. This redirects all HTTP requests to HTTPS automatically.
3
HSTS — on the same Edge Certificates page, click "Enable HSTS" → set Max Age: 6 months → enable Include Subdomains → Save. This tells browsers to always use HTTPS for 6 months.
4
Minimum TLS Version — set to TLS 1.2 (or 1.3 for best security). Located in Edge Certificates → Minimum TLS Version.
5
Automatic HTTPS Rewrites — toggle to ON. This fixes mixed-content warnings by rewriting HTTP asset URLs to HTTPS.
Expected SSL mode values
SSL/TLS Mode: Full (strict) Always Use HTTPS: ON HSTS Max-Age: 15552000 (6 months) HSTS Include Subdomains: ON Minimum TLS Version: TLS 1.2 Automatic HTTPS Rewrites: ON
Full (strict) requires a valid origin cert. Cloudflare Pages automatically has a valid cert, so this is safe. Do NOT use "Flexible" mode — it breaks service workers.
8
Run Live Diagnostics on verify.html
Confirm DNS, HTTPS, Cloudflare, and PWA are all working
Now it's time to run the automated diagnostic tool to verify everything is configured correctly. The tool checks DNS, SSL, Cloudflare proxy, PWA files, and more — all in real time.
1
Open verify.html?domain=cruise-crews.com ↗ in a new tab.
2
The domain
cruise-crews.com should be pre-filled. Click "Run Diagnostics".3
Wait ~15-20 seconds for all checks to complete. You'll see results across 7 groups.
4
Review each group. Aim for a score of 80 or higher.
What verify.html checks
Seven automated check groups run in parallel:
DNS — A/CNAME records, Cloudflare NS, proxy IP, TTL, www subdomain
HTTPS/SSL — Site reachable, HTTP→HTTPS redirect, HSTS, CF-Ray header
Cloudflare — Proxy status, Pages CNAME, IPv6, SPF email records
PWA — manifest.json valid, service worker live, icons 192+512, HTTPS
Performance — Page HTML loads, title tag, viewport meta, Open Graph tags
Security Headers — Links to securityheaders.com, Mozilla Observatory, SSL Labs
Manual Checklist — Click-to-tick: SW active, install prompt, iOS add-to-homescreen, offline mode, QR code
What a passing result looks like:
88
Good — cruise-crews.com
18 checks passed · 2 warnings · 0 failures
✓ 18 Pass
⚠ 2 Warn
✓ DNS Resolution
✓ HTTPS / SSL
✓ Cloudflare Setup
✓ PWA Requirements
Score below 60? Check the red "Fail" items first — DNS and HTTPS failures block everything else. See the full Cloudflare Setup Guide for specific fixes.
9
Final Checklist — You're Live! 🎉
Manual tests to confirm the full PWA experience works
Run these final manual tests — tick each one as you confirm it works on the live domain.
🔒 HTTPS padlock visible in browser address barVisit https://cruise-crews.com — the padlock must be green/closed
🔄 HTTP → HTTPS redirect worksVisit http://cruise-crews.com (plain HTTP) — it should redirect to https://
🌐 www subdomain resolvesVisit https://www.cruise-crews.com — should load the same app
⚙️ Service Worker activatesChrome DevTools → Application → Service Workers → status: "activated and running"
📱 Android install prompt appearsOpen in Chrome on Android — a banner or address-bar install icon should appear after a few seconds
🍎 iOS Add to Home Screen worksSafari on iPhone → Share → "Add to Home Screen" → tap Add → opens fullscreen (no browser UI)
✈️ Offline mode worksLoad the app → enable airplane mode → refresh the page → it should still load from cache
📷 QR code opens the appGenerate QR at qr.html → scan with phone camera → tapping the link opens cruise-crews.com correctly
⚡ Lighthouse PWA audit passesChrome DevTools → Lighthouse → Progressive Web App → Generate report → all checks should be green
🔢 Diagnostics score ≥ 80verify.html?domain=cruise-crews.com → Run Diagnostics → score ring shows 80 or above
Tip: Run the diagnostics monthly to catch any configuration drift, expired tokens, or DNS changes.