Custom Domains

Each Micropage project has a primary host (for example my-site.micropage.sh). You can also attach your own custom subdomain such as www.example.com and we'll serve the project over HTTPS at that address with a valid SSL certificate.

Setup

1. In the Micropage web editor, open your project → Settings → Custom Domain → enter the subdomain you want to use (e.g. www.example.com).

2. At your DNS provider, create this CNAME record:

   Field	Value
   Type	CNAME
   Name	www (or whatever subdomain you chose)
   Target	cname.micropage.sh

   Example: www.example.com → CNAME → cname.micropage.sh

3. Wait. Within a minute or two the editor's status panel will go through Waiting for DNS → Validating → Issuing TLS certificate → green Live. Once it's green, https://www.example.com/ serves your project.

SSL certificates are automatically provisioned and renewed by Cloudflare. You don't need to upload one or manage it yourself.

What's supported

• Any subdomain you own: www.example.com, store.example.com, landing.example.com, even multi-level like app.api.example.com.
• CNAME-flattening DNS providers (Cloudflare, Route 53, DNSimple, etc.) work the same way.

What's not supported (yet)

• Apex domains (bare example.com with no subdomain). The editor will reject them with a message. If you want bare example.com to work, set up an apex → subdomain redirect at your DNS provider. Most providers have a "URL forwarding" or "redirect" feature for this — point example.com to https://www.example.com and the apex will redirect to your live subdomain.

Troubleshooting

Status stuck on "Waiting for DNS" past 5 minutes

• Double-check the CNAME target — it must be exactly cname.micropage.sh, not your project's *.micropage.sh host.
• Run dig CNAME www.example.com (replace with your hostname) and confirm it resolves to cname.micropage.sh.
• DNS TTLs vary. If your provider has a long TTL set, propagation can take longer than the editor's first poll.

Status shows "Validation failed" with a Cloudflare error message

• If your DNS is hosted on Cloudflare and the subdomain's record is proxied (orange cloud), validation will fail silently. Change it to DNS-only (gray cloud) for the subdomain you're attaching, then click Retry validation in the editor.

"This hostname is already attached to a different Cloudflare account"

• The hostname is already registered as a Custom Hostname in another Cloudflare account. Remove it there first, or contact support.

Notes

• Custom domains are available on paid plans.
• Removing the domain in the editor immediately cleans up the Cloudflare side; certificates for unused hostnames are deprovisioned automatically.