Skip to main content
Every published Moda site gets a free *.moda.page address. On a paid plan you can also connect a domain you own — like www.yoursite.com or portfolio.yoursite.com — so visitors reach your site at your own address.

​
Before you start

  • Your site must be published (custom domains attach to the published site).
  • You need access to your domain’s DNS settings — usually at the registrar where you bought the domain (GoDaddy, Cloudflare, Namecheap, FastHosts, …).

​
Connect a domain

  1. Open your site’s Publish panel and find Custom domains.
  2. Click Add domain. In the dialog, enter the hostname you want, e.g. www.yoursite.com, and click Add. If you type a root domain like yoursite.com, Moda suggests www.yoursite.com instead — most registrars can’t point a root at Moda, and www works everywhere (see Root domains).
  3. The dialog now shows your domain’s setup. Under Where is your DNS hosted? pick your provider — GoDaddy, Cloudflare, Namecheap, or Other — and the click path, field names and TTL guidance switch to match.
  4. Add the two DNS records shown at your DNS provider. Add them both in one visit — they’re independent:
    • Ownership (TXT) — proves you control the domain.
    • Routing (CNAME) — points traffic at Moda.
  5. Back in Moda, click Verify ownership. Moda also re-checks automatically for a few minutes.
Once ownership verifies and your CNAME propagates, Moda issues a TLS certificate for your domain (usually 1–2 minutes) and the status flips to Active. You can reopen the dialog any time from the domain’s row in the Publish panel (Set up while it’s pending, Manage once active).
Enter each record’s Name exactly as shown in Moda. Most DNS providers automatically append your domain to whatever you type in the Name/Host field. If Moda shows the Name _moda-verify and you paste the full _moda-verify.yoursite.com, your provider saves it as _moda-verify.yoursite.com.yoursite.com — a doubled record that never verifies. This is the single most common reason verification fails.
For TTL, use the lowest value your provider offers — 300 seconds if available. GoDaddy’s minimum of ½ Hour (600 seconds) is fine too; it only affects how quickly a later change propagates.

​
Provider guides

The same steps the in-app dialog shows, checked against each provider’s own help pages on 2026-09-03.

​
GoDaddy

  1. Sign in, open Domain Portfolio, select your domain, then open the DNS tab.
  2. Click Add New Record and pick the record Type.
  3. Fill in Name, Value and TTL exactly as Moda shows. GoDaddy adds .yoursite.com to Name for you; @ means the root.
  4. Save, then repeat for the second record.
  • TTL: the lowest option is ½ Hour (600 seconds) — that’s fine.
  • Root domains: GoDaddy’s CNAME Name field can’t be @ and there is no ALIAS/ANAME type, so yoursite.com can’t route to Moda at GoDaddy. Connect www.yoursite.com instead, then forward the root: DNS → Forwarding → Add Forwarding, forward to https://www.yoursite.com, Permanent (301).

​
Cloudflare

  1. Select your domain, then open DNS → Records.
  2. Click Add record and pick the record Type.
  3. Enter Name and Content exactly as Moda shows. On the CNAME, set Proxy status to DNS only (gray cloud).
  4. Leave TTL on Auto and save.
  • DNS only is required. A proxied (orange-cloud) CNAME terminates TLS in your own Cloudflare zone and conflicts with the certificate Moda issues for your hostname.
  • Root domains: Cloudflare flattens CNAMEs at the root, so a CNAME on @ works — you can connect yoursite.com directly.
  • Root → www redirect: add a redirect rule under Rules → Redirect Rules from yoursite.com to https://www.yoursite.com.

​
Namecheap

  1. Sign in, open Domain List, click Manage next to your domain, then open the Advanced DNS tab.
  2. Under Host Records click Add New Record and pick the record type.
  3. Fill in Host and Value exactly as Moda shows — Namecheap calls the name field Host. It adds .yoursite.com to Host for you; @ means the root.
  4. Leave TTL on Automatic and click Save All Changes.
  • Root domains: Namecheap doesn’t allow a CNAME on @. Use the ALIAS Record type for the routing record instead (Moda shows this type when you pick Namecheap for a root domain). Remove any existing A, CNAME or URL Redirect record on @ first — they block it.
  • Root → www redirect: add a URL Redirect Record with Host @, Value https://www.yoursite.com, type Permanent (301). Remove any A record on @ first.

​
Other providers

  1. Open the DNS settings for your domain at your DNS provider (usually the registrar you bought it from).
  2. Add a new record for each card Moda shows, copying Type, Name and Value exactly. Remember the auto-append gotcha above — enter the short Name, not the full hostname.
  3. Use the lowest TTL your provider offers, then save.
  • Root domains: your provider may not allow a CNAME at the root; if it offers an ALIAS or ANAME type, use that. If it offers neither, connect www.yoursite.com instead and set up a web forward from the root — providers name it differently: Web Forwarding (FastHosts), Domain Forwarding (GoDaddy), URL Redirect (Porkbun and others). It’s usually a toggle in the same panel as your DNS settings.

​
Root domains (yoursite.com without www)

A root domain (also called an apex domain — yoursite.com rather than www.yoursite.com) is special: the DNS standard doesn’t allow a CNAME record at the root, and many registrars offer no alternative. Recommended: use www and forward the root. Visitors reach your site either way, and it works at every provider:
  1. In Moda, click Add domain and connect www.yoursite.com. (If you already added the root domain, open its row and Remove it — it can’t route at a provider without ALIAS/ANAME.)
  2. Add the TXT and CNAME records Moda shows. Note the TXT Name will be _moda-verify.www — enter it exactly as shown.
  3. At your registrar, forward yoursite.com to https://www.yoursite.com as a permanent (301) redirect. See the provider guides for where that lives.
That’s the standard setup across the web: www serves the site, the bare domain redirects to it. If your provider supports ALIAS/ANAME or root CNAMEs (Cloudflare, Namecheap, DNSimple, and others), you can connect the root directly:
  1. Add yoursite.com as your custom domain in Moda.
  2. Create the routing record with Name @ and the value Moda shows — as a CNAME on Cloudflare (flattened automatically) or as the ALIAS/ANAME type elsewhere.
  3. Optionally, also add www.yoursite.com as a second domain in Moda so both addresses serve your site.

​
Status meanings

​
Removing a domain

In the Publish panel, open the domain’s row (Set up or Manage) and click Remove in the dialog, then confirm. Removal frees the hostname immediately and detaches the certificate; your *.moda.page address keeps working throughout.

​
Troubleshooting

Verification keeps failing. Almost always the doubled-Name problem from the warning above. In your DNS provider’s record list, check what the TXT record’s full name actually is — if you see your domain repeated twice, edit the record’s Name (Host on Namecheap) to just the short value Moda shows (e.g. _moda-verify). Records added but nothing happens. DNS changes take a few minutes to propagate — longer with a high TTL, so use the lowest your provider offers (300 if available; GoDaddy’s 600-second minimum is fine). Moda re-checks automatically for a few minutes after you add a domain; you can always open the domain’s row and click Verify ownership to re-check immediately. Your DNS is on Cloudflare. Set the CNAME to DNS only (gray cloud, not orange). Proxying through your own Cloudflare zone conflicts with the certificate Moda issues for your hostname. Your root domain is stuck at GoDaddy. GoDaddy can’t route a root domain to Moda at all. Remove the root entry, add www.yoursite.com, and forward the root as described in the GoDaddy guide.