Publishing & Domains

Custom domains

Connect your own domain like yourbrand.com — add it, set the DNS records at your registrar, verify, and go live with automatic HTTPS.

Last updated 2026-06-29

A custom domain — yourbrand.com instead of yourbrand.webpress.id — makes your site look established and professional. Connecting one means telling your domain to point at Webpress. This guide walks through it for non-technical users.

Custom domains are a paid-plan feature. You bring your own domain (buy it from any registrar — Namecheap, GoDaddy, Cloudflare, and so on); Webpress doesn't sell domains. See Plans & pricing.

A quick primer on DNS

Your domain has a DNS (Domain Name System) — think of it as the address book that tells the internet where your domain lives. To connect it to Webpress, you add a couple of records to that address book at your registrar (the company you bought the domain from). Webpress gives you the exact records to paste in.

Connect your domain

  1. Open Project Settings → Domain (or follow the "Use a custom domain" link in the publish dialog).
  2. Enter your domain, e.g. mybrand.com, and add it.
  3. Webpress shows the DNS records to add. They typically include:
    • an A or CNAME record that points your domain at Webpress,
    • a CNAME for the www version,
    • a TXT record that proves you own the domain.
  4. Each record has a Copy button. Sign in to your registrar, open its DNS settings, and add each record exactly as shown.
  5. Back in Webpress, click Verify.

Verification and going live

After you add the records, Webpress checks them. You'll see a status that moves through:

StatusMeaning
Pending DNSWaiting for you to add the records.
VerifyingRecords found — confirming everything lines up.
ActiveDone — your site is live on your domain, with HTTPS issued automatically.
ErrorSomething's off; the message tells you which record needs attention.

DNS takes time. Changes can take anywhere from a few minutes to a few hours to spread across the internet. If verification doesn't pass right away, that's normal — wait a bit and click Verify again. Webpress won't hard-fail; it keeps re-checking.

Apex vs www

  • The apex (or "root") is the bare domain: mybrand.com.
  • The www version is www.mybrand.com.

You can connect both, with one as the primary and the other redirecting to it (most people send www → the bare domain). Some registrars can't point an apex with a CNAME — in that case use the A record Webpress provides for the apex, and a CNAME for www.

HTTPS is automatic

Once your domain verifies, Webpress issues and renews the HTTPS certificate for it automatically. You don't need to buy or configure anything — visitors get the padlock and a secure connection.

Where to go next