Connect a custom domain

Every published site gets a free address on the platform. When you're ready for www.yourorganization.org, connect the domain you own — it takes two DNS records and needs the admin role on the site.

1. Add the domain

In the editor, open Settings → Custom domains, type your domain and add it. You'll be shown a TXT record (named _rainbow-verify) to create at your DNS provider — this proves you control the domain, so nobody else can claim it.

2. Verify ownership

Create that TXT record in your DNS provider's control panel (GoDaddy, Cloudflare, Namecheap — they all have a DNS records page), then click Verify back in Settings. DNS changes can take a few minutes to a few hours to propagate, so if verification fails at first, wait and try again.

3. Point the domain here

Once verified, point the domain at the platform:

• an A record to the server's IP address, or
• a CNAME record (typical for www) to the builder's host name.

Your platform operator can tell you which to use if you're not sure. Until this record is in place the domain shows as Verified — waiting for DNS and your site keeps using its platform address everywhere — links in emails and receipts never point at a domain that isn't answering yet. Click Check once you've made the change (or just visit the domain); when it answers, the status flips to Live.

What happens next

• HTTPS is automatic. A TLS certificate is issued the first time the domain is visited — no certificate files, no renewal chores.
• The site serves at your domain with clean addresses (no /s/... prefix), and its sitemap, robots.txt and llms.txt move with it.
• Search engines are told your domain is the canonical address.

You can connect more than one domain, and remove one at any time. Only verified domains ever serve your site.