1. Why Forward Your Root Domain to WWW? (The DNS Apex Rule Explained Simply)
Understanding why www.yourdomain.com activates instant HTTPS SSL while bare yourdomain.com needs a 301 redirect
When creators, agencies, and small business owners purchase a branded domain name—such as kwameadu.net or yourbrand.com—their very first instinct is to type the shortest version of the address into a browser or print it on a business card without the "www." prefix. Yet when they connect that domain to a modern cloud platform, bio link hub, e-commerce storefront, or SaaS application, the platform almost always recommends pointing a subdomain like www.yourbrand.com or links.yourbrand.com via a CNAME record.
This recommendation is not arbitrary; it stems directly from RFC 1034 and RFC 1035, the foundational internet specifications governing the Domain Name System (DNS). Under RFC rules, the root (also called the "apex" or "@" record) of a domain must hold authoritative infrastructure records—specifically Start of Authority (SOA) and Nameserver (NS) records—and frequently holds email routing records (MX, SPF, and DMARC). Because a standard CNAME record acts as a complete alias that overrides every other record type at the same hostname, traditional DNS registrars legally forbid placing a standard CNAME record at the bare root "@".
A subdomain like www.yourbrand.com, however, carries no SOA or NS records of its own. That means a CNAME record pointing www directly to a cloud edge hostname (such as linksinmybio.com) works reliably on 100% of domain registrars worldwide. Even better, modern edge networks using Cloudflare for SaaS can validate a www CNAME over HTTP DCV in 15 to 60 seconds and issue an automatic, zero-cost TLS/HTTPS SSL certificate without requiring you to change your nameservers or juggle expiring TXT ownership tokens.
The missing bridge is what happens when a real human visitor—or someone tapping a printed flyer or podcast mention—types bare yourbrand.com instead of www.yourbrand.com. If you leave the bare root "@" without a DNS record or redirect rule, visitors hit an ugly "Site cannot be reached" (NXDOMAIN) error. By pairing a clean CNAME on www with an HTTP 301 Permanent Redirect on the bare root, every variation—yourbrand.com, http://yourbrand.com, https://yourbrand.com, and www.yourbrand.com—resolves smoothly to one canonical, HTTPS-secured destination while preserving paths, referral parameters, and Google SEO equity.
The Golden Rule of Custom Domain Architecture
Point www.yourdomain.com via CNAME to your hosting platform (such as linksinmybio.com) for instant automated SSL, and configure a 301 Permanent Redirect from bare yourdomain.com to https://www.yourdomain.com so no visitor ever hits a dead end.
2. DNS Host & Registrar Comparison Matrix (2026)
How Cloudflare, GoDaddy, Namecheap, Dynadot, Porkbun, Hostinger, and Squarespace handle root-to-www forwarding
Every major domain registrar and DNS provider allows regular users to set up root-to-www forwarding manually through a web dashboard—no coding, terminal access, or automation tools required. However, providers differ significantly in one critical area: whether they issue a valid HTTPS SSL certificate on the bare root redirect itself.
Review the comparison matrix below to see exactly what your current DNS host supports and how long manual setup takes.
| DNS Provider / Registrar | Supports Manual Root -> WWW (301) | Free HTTPS on Bare Root Redirect | Preserves Paths & Query Params | Typical Setup Time |
|---|---|---|---|---|
| Cloudflare (Free Plan) | Yes (Redirect Rules / Page Rules) | Yes (Full Automatic Edge SSL) | Yes (100% Exact Path + Query) | ~2 minutes |
| GoDaddy | Yes (Built-in Domain Forwarding) | HTTP native; HTTPS limited | Yes (Forward with settings) | ~2 minutes |
| Namecheap | Yes (URL Redirect Record on @) | HTTP native; HTTPS limited | Partial / Basic | ~2 minutes |
| Dynadot | Yes (DNS Forwarding on @) | HTTP native; HTTPS optional | Yes (Forwarding 301) | ~2 minutes |
| Porkbun | Yes (URL Forwarding on apex) | Yes (Free Let's Encrypt SSL) | Yes (Include URI Path) | ~2 minutes |
| Hostinger | Yes (hPanel Redirects / DNS) | With hosting SSL enabled | Yes | ~3 minutes |
| Squarespace Domains | Yes (Domain Forwarding) | Yes (Automatic SSL) | Yes (Path Forwarding) | ~2 minutes |
3. Method 1: Manual Step-by-Step Setup on Cloudflare (Recommended)
The fastest, 100% free setup with guaranteed HTTPS SSL on both yourdomain.com and www.yourdomain.com
Cloudflare's Free DNS plan is the undisputed gold standard for forwarding a root domain to www because Cloudflare operates as both an ultra-fast Anycast DNS server and an HTTPS Edge Reverse Proxy. That means visitors typing http://yourdomain.com OR https://yourdomain.com receive a sub-30ms encrypted 301 redirect straight to https://www.yourdomain.com without a single certificate warning.
Step 1 — Configure Your www CNAME Record (CRITICAL: Use Grey Cloud / DNS-Only). Log in to your Cloudflare dashboard, select your domain, and click DNS -> Records in the left sidebar. Click "+ Add record" (or edit your existing www record) with these exact values: Type = CNAME, Name = www, Target = linksinmybio.com (or your SaaS target hostname), TTL = Auto, and toggle Proxy status OFF so it displays a Grey Cloud ("DNS only"). Why must www be DNS-only? Because platforms like LinksInMyBio already run behind Cloudflare for SaaS to provision your dedicated HTTPS certificate. Leaving www set to Orange Cloud ("Proxied") creates an Orange-to-Orange routing conflict that can stall SSL validation or trigger Error 525.
Step 2 — Add the Originless Proxied Root (@) Placeholder Record. Cloudflare's redirect engine only runs on hostnames that actually resolve to Cloudflare's Edge Proxy. If your bare root "@" has no DNS record, Cloudflare will display a banner warning that "Visitors cannot reach yourdomain.com" and any redirect rule will sit idle. Click "+ Add record" and create Cloudflare's official originless placeholder record: Type = AAAA, Name = @, IPv6 address = 100:: (if you prefer IPv4, Type = A with 192.0.2.1 works identically), TTL = Auto, and toggle Proxy status ON so it displays an Orange Cloud ("Proxied"). The address 100:: is a reserved RFC 6666 discard prefix that tells Cloudflare "there is no real origin server here; intercept this traffic at the Edge and run my rules."
Step 3 — Deploy the Root-to-WWW Redirect Rule. Where do you enter the destination URL? Note that Cloudflare never puts redirect destination URLs inside the DNS -> Records screen—they live under the Rules menu in the left sidebar. Click Rules -> Redirect Rules -> "+ Create rule". Cloudflare actually offers a built-in one-click template called "Redirect from Root to WWW" right on that page. Click it—or enter the custom rule manually: Rule name = "Root to WWW"; If incoming requests match = Custom filter expression where Field is Hostname, Operator is equals, and Value is yourdomain.com (do NOT include www); Then URL redirect Type = Dynamic, Expression = concat("https://www.yourdomain.com", http.request.uri.path), Status code = 301, and check "Preserve query string". Click Deploy.
Alternative for Classic Page Rules Users: If you prefer Cloudflare's Rules -> Page Rules tab, create one Page Rule with URL = yourdomain.com/* (never put a leading asterisk * before yourdomain.com!), Setting = Forwarding URL, Status Code = 301 - Permanent Redirect, and Destination URL = https://www.yourdomain.com/$1. Click Save and Deploy Page Rule.
Step 4 — Confirm "Always Use HTTPS" Is Enabled. In the left sidebar, open SSL/TLS -> Edge Certificates and verify that the "Always Use HTTPS" toggle is switched ON, and under SSL/TLS -> Overview verify encryption mode is set to Full or Flexible (never Off). Within 30 seconds, open a private browser window and visit http://yourdomain.com and https://yourdomain.com—both will immediately redirect to https://www.yourdomain.com.
Why You Should NEVER Put a Leading Asterisk (*) on a Root-to-WWW Rule
Writing *yourdomain.com/* instead of yourdomain.com/* matches BOTH bare yourdomain.com AND www.yourdomain.com. When Cloudflare redirects www.yourdomain.com back to https://www.yourdomain.com, browsers abort with ERR_TOO_MANY_REDIRECTS. Always match ONLY bare yourdomain.com!
4. Method 2: Manual Step-by-Step Setup on GoDaddy
Connecting www via CNAME and activating GoDaddy's built-in 301 Domain Forwarding in 2 minutes
GoDaddy is the world's largest domain registrar and includes native root domain forwarding directly inside its DNS management screen. You do not need to purchase GoDaddy website hosting or any add-on plans to forward your root domain to www.
Step 1 — Add the www CNAME Record. Sign in to your GoDaddy Domain Portfolio, click your domain name, and select the DNS tab -> DNS Records. Look for an existing CNAME record named "www". If one already exists (GoDaddy often pre-populates www pointing to @), click Edit on that record rather than creating a duplicate. Set Type = CNAME, Name = www, Value = linksinmybio.com, and TTL = Default (1 Hour or 600 seconds). Click Save.
Step 2 — Remove Conflicting Parked A Records if Needed. GoDaddy automatically attaches a "Parked" A record on "@" when you first buy a domain. You do not need to manually delete it before using GoDaddy's Forwarding tool—GoDaddy will automatically update the "@" A record to its forwarding server IP when you complete Step 3.
Step 3 — Configure Root Domain Forwarding. Scroll down on the DNS page (or click the Forwarding tab next to DNS Records) and locate the "Domain" section (not Subdomain). Click "Add Forwarding". Choose "https://" from the protocol dropdown, enter www.yourdomain.com in the destination box, and select "Permanent (301)" as the Forward Type. Click Save.
Step 4 — Wait for Propagation & Verify in Studio. GoDaddy typically propagates DNS changes in 5 to 30 minutes. Once saved, open LinksInMyBio Studio -> Pro Tools -> Custom CNAME Domains, enter www.yourdomain.com, and click Add & Verify Domain to issue your free HTTPS SSL certificate.
5. Method 3: Manual Step-by-Step Setup on Namecheap
Using Namecheap's Advanced DNS URL Redirect Record alongside your www CNAME
Namecheap makes root-to-www forwarding clean and transparent by exposing it as a first-class record type ("URL Redirect Record") directly inside the Advanced DNS table.
Step 1 — Open Advanced DNS. Log in to your Namecheap account, click "Domain List" in the left menu, click "Manage" next to your domain, and switch to the "Advanced DNS" tab. Ensure your Nameservers setting on the Domain tab is set to "Namecheap BasicDNS" (DNS records inside Namecheap only apply when Namecheap BasicDNS is active).
Step 2 — Clear Default Parking Records. Delete any default "CNAME www -> parkingpage.namecheap.com" or "URL Redirect @ -> parking" placeholder records so they do not conflict with your new configuration.
Step 3 — Add the www CNAME Record. Click "Add New Record", select Type = CNAME Record, Host = www, Value = linksinmybio.com, TTL = Automatic, and click the green checkmark to save.
Step 4 — Add the Root (@) URL Redirect Record. Click "Add New Record" again, select Type = URL Redirect Record, Host = @, Value = https://www.yourdomain.com, and change the redirect mode dropdown from "Unmasked" (302) to "Permanent (301)". Never choose "Masked" (iframe), because masked redirects break mobile viewports, block social share meta tags, and trigger browser security errors. Click the green checkmark to save.
Step 5 — Verify Live Routing. Namecheap BasicDNS updates quickly—typically within 2 to 15 minutes. After saving, verify www.yourdomain.com inside LinksInMyBio Pro Tools and test typing yourdomain.com in a fresh browser tab.
6. Method 4: Manual Setup on Dynadot, Porkbun, Hostinger & Squarespace Domains
Exact dashboard navigation paths for four additional popular domain registrars
If your domain is registered with Dynadot, Porkbun, Hostinger, or Squarespace Domains (formerly Google Domains), the exact same two-part architecture applies: one CNAME record on www plus one 301 root forwarding rule on @.
Dynadot Instructions: Sign in to Dynadot -> My Domains -> Manage Domains -> click your domain -> DNS Settings -> choose "Dynadot DNS". Under "Subdomain Records", add Subdomain = www, Record Type = CNAME, IP Address or Target Host = linksinmybio.com. Under "Domain Record" (the top section for bare root), select Record Type = Forward and enter https://www.yourdomain.com (check Permanent 301). Click Save DNS. Note: Avoid Dynadot's root ANAME record if your target SaaS uses Cloudflare Free SaaS, as www CNAME + root forwarding guarantees 15-second green SSL with zero TXT token headaches.
Porkbun Instructions: Log in to Porkbun -> Domain Management -> click "Details" next to your domain -> click "Edit" next to DNS Records. Remove any default ALIAS/CNAME parked entries, then add Type = CNAME, Host = www, Answer = linksinmybio.com. Next, return to Domain Details, click "Edit" next to "URL Forwarding", leave the Subdomain field blank (for bare root), set Redirect To = https://www.yourdomain.com, Type = Permanent (301), and check "Include URI Path" so subpages transfer cleanly. Porkbun automatically provisions a free Let's Encrypt SSL certificate for your root forwarder.
Hostinger Instructions: Open Hostinger hPanel -> Domains -> select your domain -> DNS / Nameservers. Add Type = CNAME, Name = www, Target = linksinmybio.com, TTL = 3600 (delete any conflicting A/CNAME on www). For the bare root redirect, navigate to Websites -> Manage -> Domains -> Redirects (or Domain Forwarding inside the Domains panel) and redirect yourdomain.com -> https://www.yourdomain.com with status 301.
Squarespace Domains (Migrated Google Domains) Instructions: Sign in to Squarespace -> Domains -> click your domain -> DNS -> DNS Settings -> Custom Records -> Add Record: Host = www, Type = CNAME, Data = linksinmybio.com. Then go to Website -> Domain Forwarding -> Add Rule: Forward From = yourdomain.com, Forward To = https://www.yourdomain.com, Redirect Type = Permanent (301), Path Forwarding = Forward Path, and SSL = On. Click Save.
| Registrar | Step 1: WWW Record | Step 2: Root (@) Redirect Menu | Recommended Redirect Mode |
|---|---|---|---|
| Cloudflare | CNAME www -> linksinmybio.com (Grey Cloud) | AAAA @ -> 100:: (Orange Cloud) + Rules -> Redirect Rules | 301 Dynamic + Preserve Query |
| GoDaddy | CNAME www -> linksinmybio.com | DNS -> Forwarding -> Domain | Permanent (301) to https://www... |
| Namecheap | CNAME www -> linksinmybio.com | Advanced DNS -> URL Redirect Record (@) | Permanent (301) (Never Masked) |
| Dynadot | Subdomain CNAME www -> linksinmybio.com | DNS Settings -> Domain Record -> Forward | 301 Forward to https://www... |
| Porkbun | CNAME www -> linksinmybio.com | Domain Details -> URL Forwarding (blank host) | Permanent (301) + Include URI Path |
| Squarespace | Custom Record CNAME www -> linksinmybio.com | Website -> Domain Forwarding | Permanent (301) + Path + SSL On |
7. Solving the Bare-Root HTTPS Problem (Why Cloudflare Free DNS Beats Basic Forwarders)
Why https://yourdomain.com sometimes triggers browser warnings on basic registrars—and how to eliminate it forever
One of the most confusing moments for non-technical domain owners occurs right after setting up forwarding on traditional registrars like GoDaddy or Namecheap. When they type yourdomain.com into Chrome or Safari, it works perfectly if the browser tries HTTP first. Yet if a visitor clicks a link formatted explicitly as https://yourdomain.com (with the "s" and without "www"), Chrome may display a frightening full-screen warning: "Your connection is not private" (NET::ERR_CERT_COMMON_NAME_INVALID or ERR_CONNECTION_CLOSED).
Why does this happen? Because standard registrar forwarding servers often listen only on unencrypted Port 80 (HTTP), or they serve a generic registrar certificate that does not contain your domain name. Modern browsers like Chrome, Safari, and Edge increasingly default to HTTPS-First Mode, automatically upgrading bare domain visits to https:// before receiving any redirect response.
The universal, zero-cost permanent fix is to delegate your domain's DNS to Cloudflare's Free Plan while keeping your domain registered wherever you bought it (you do NOT need to transfer or pay anything to Cloudflare). Simply sign up at cloudflare.com, add yourdomain.com, choose the $0 Free plan, and copy Cloudflare's two nameservers into your registrar's Nameservers box. Cloudflare automatically imports your existing MX, SPF, DKIM, and DMARC email records so your email never misses a beat.
Once Cloudflare is active, apply the exact 4-step Cloudflare configuration from Section 3 (www CNAME Grey Cloud + @ AAAA 100:: Orange Cloud + Root-to-WWW 301 Redirect Rule + Always Use HTTPS). Cloudflare automatically issues a universal edge TLS certificate covering bare yourdomain.com, so http://yourdomain.com, https://yourdomain.com, http://www.yourdomain.com, and https://www.yourdomain.com all load with a spotless padlock icon on every phone and desktop browser worldwide.
8. Troubleshooting the 5 Most Common Root-to-WWW Errors
Exact root causes and instant fixes for redirect loops, SSL handshake errors, and missing DNS records
If your root domain redirect does not work immediately after saving, do not panic. Nearly 99% of custom domain issues trace back to one of five predictable misconfigurations. Use the diagnostic table below to pinpoint and resolve the issue in seconds.
| Symptom / Browser Error | Exact Root Cause | Instant Fix |
|---|---|---|
| ERR_TOO_MANY_REDIRECTS (Infinite Loop) | Redirect rule uses wildcard *yourdomain.com/* which also matches www.yourdomain.com. | Change rule expression to match ONLY bare yourdomain.com (Hostname equals yourdomain.com, or Page Rule yourdomain.com/* with NO leading *). |
| Error 525 / SSL Handshake Failed / Stuck on Pending Validation | www CNAME record in Cloudflare is set to Orange Cloud (Proxied) instead of Grey Cloud. | Edit www CNAME in Cloudflare DNS and toggle Proxy status OFF (Grey Cloud / DNS only). |
| DNS_PROBE_FINISHED_NXDOMAIN on bare yourdomain.com | No A or AAAA record exists on "@" (root), so Cloudflare Edge never receives requests. | Add AAAA record Name=@ Value=100:: with Proxy status ON (Orange Cloud). |
| "Your Connection Is Not Private" on https://yourdomain.com | Registrar forwarding only supports Port 80 HTTP and lacks an HTTPS cert for the bare root. | Connect your domain to Cloudflare Free DNS and use AAAA @ 100:: (Proxied) + Root-to-WWW Redirect Rule. |
| Subpaths or ?ref= query parameters disappear after redirect | Static redirect target drops the incoming URI path and query string. | Use Dynamic expression concat("https://www.yourdomain.com", http.request.uri.path) with "Preserve query string" checked (or /$1 in Page Rules). |
9. Scaling Multiple Branded Custom Domains on LinksInMyBio.com
Connect up to 5 to 20+ custom domains across all your bio profiles with live SSL monitoring
Once you understand the simple www CNAME + Root-to-WWW 301 pattern, you can brand every project, podcast, storefront, or client account under its own dedicated domain name. Inside LinksInMyBio Studio -> Pro Tools -> Custom CNAME Domains, your allowed custom domain quota scales 1-to-1 with the number of bio profiles included in your Pro tier:
Creator Pro and VIP Founder Lifetime accounts include 5 bio profiles and 5 custom domains—plus 1 extra custom domain for every Extra Profile Slot add-on you attach. Pro Plus / Agency accounts include 20 bio profiles and 20 custom domains (scaling even higher with add-on slots), making it effortless for agencies and multi-brand creators to manage an entire portfolio from one unified dashboard.
Every time you open Pro Tools, the always-visible "Domains Currently In Use" directory lists every active and pending domain across all of your profiles, displays your real-time quota meter (for example, 3 / 20 In Use), shows live HTTPS SSL status badges, lets you jump between profiles with one click, and allows targeted removal of any single domain without disturbing your other live domains. And for domains hosted on Cloudflare, our one-click "Authorize Cloudflare" OAuth integration writes your DNS-only CNAME record, registers Cloudflare Edge SSL, revokes its temporary token immediately, and runs a live verification countdown until your domain flips to LIVE · HTTPS SSL ACTIVE automatically.
Ready to Connect Your First Branded Domain?
Open LinksInMyBio Studio -> Pro Tools -> Custom CNAME Domains, enter www.yourdomain.com, and click Add & Verify Domain (or Authorize Cloudflare for 1-click automated setup). Your free HTTPS SSL certificate typically activates in 15 to 60 seconds.