Every site starts on a free subdomain, which is enough to share it and to test everything. When you are ready to use a domain you own, connect it — the site stays exactly as it is, it just answers on your own address.

Connect the domain

  1. Open the site, go to Settings and pick the Domains tab.
  2. Press Connect domain and enter the domain you own, for example www.mysite.com.
  3. Open the DNS settings at the company you bought the domain from, and add the records Ettex shows you.
  4. Wait. Verification and the SSL certificate happen on their own once DNS has propagated.

Not sure where to start? The Domains tab has a View guide link that walks through the same four steps with instructions for Cloudflare, GoDaddy and Namecheap.

The DNS records

Three records are needed, and each one can be copied with a single click from the DNS dialog:

  • An A record on @ — points the bare domain at the server.
  • A CNAME record on www — points the www address at your site's host.
  • A TXT record on @ — the verification token that proves the domain is yours.

Remove any existing A or CNAME record with the same name before adding these — the parked page your registrar created counts. Records can take up to 24 hours to propagate, though most domains go live within an hour.

Registrar-specific notes

  • Cloudflare — Dashboard → your domain → DNS → Records. Set each record to “DNS only” (grey cloud). The orange proxy breaks verification.
  • GoDaddy — My Products → your domain → Manage DNS. Add each record with “Add new record” and delete the parked A record if there is one.
  • Namecheap — Domain List → Manage → Advanced DNS. Add them under Host records and delete the default URL-redirect record.
  • Anywhere else — look for DNS management, DNS records or Zone editor, then add the same three records.

What the Domains table tells you

Each connected domain has a row showing its status, whether SSL is active or still pending, a DNS link that reopens the record list, and the type. The domain marked Primary is the address your site is served from; the others point at it.

After it is live

  • SSL is issued for you — the site switches to HTTPS with nothing to configure.
  • Check the SEO tab: the default title and meta description, the social preview, the sitemap and robots.txt all follow the new address.
  • Set up redirects on the site's settings if URLs changed — old links keep working instead of returning a 404.
  • Changes to site settings apply on the next publish, so publish once after connecting.

If it does not verify

  • Give it time. Propagation is genuinely slow sometimes; up to 24 hours is normal.
  • Check for a leftover record. An old A or CNAME on the same name wins over the new one.
  • On Cloudflare, check the cloud is grey, not orange.
  • Make sure the TXT record was added to @ and not to a subdomain — registrars sometimes append the domain for you, producing a doubled name.