By Alpit Patel and the aibrevo team · October 1, 2026 · 2 min read
How Do You Connect Your Domain to GoHighLevel?
Quick answer
Add the domain in GoHighLevel's domain settings, then create the DNS record at your domain provider: an A record pointing @ to 162.159.140.166 for a root domain, or a CNAME pointing your subdomain to sites.ludicrous.cloud. On Cloudflare set the record to DNS only. SSL is issued automatically once the domain connects.
Key takeaways
- Root domain: an A record with host @ pointing to 162.159.140.166.
- Subdomain (such as www or offers): a CNAME pointing to sites.ludicrous.cloud.
- On Cloudflare, set the HighLevel record to DNS only, not proxied, or the domain will not verify.
- SSL is provisioned automatically after the domain connects, usually within minutes; DNS changes can take up to 24 hours.
- A sites domain is not an email sending domain. Email authentication (SPF, DKIM, DMARC) is a separate setup.
To connect a domain to GoHighLevel, add it in the sub-account’s domain settings, then create one DNS record at the company that manages your domain’s DNS: an A record pointing @ to 162.159.140.166 for a root domain, or a CNAME pointing your subdomain to sites.ludicrous.cloud. If you use Cloudflare, set that record to DNS only. HighLevel issues the SSL certificate automatically once the domain connects.
The DNS records
From HighLevel’s guide to setting up a root domain or subdomain for sites (modified September 27, 2026):
| You are connecting | Record type | Host / name | Value |
|---|---|---|---|
| Root domain (example.com) | A | @ | 162.159.140.166 |
| Subdomain (www, offers, book) | CNAME | the subdomain, e.g. offers | sites.ludicrous.cloud |
| Subdomain, alternative | A | the subdomain | 162.159.140.166 |
When you connect a root domain, HighLevel can also add the www version and set a 301 redirect from www to the root, so both addresses work.
Step by step
- Find where your DNS lives. That is whoever your domain’s nameservers point to: often the registrar (GoDaddy, Namecheap), sometimes Cloudflare or your web host. Adding the record anywhere else does nothing.
- Add the domain in HighLevel in the sub-account’s domain settings, and choose what it will serve (funnels and websites).
- Create the record from the table above at your DNS provider. Delete any existing A or CNAME record for the same host first; two records for one host is a common reason verification fails.
- On Cloudflare, switch the record to DNS only (grey cloud). A proxied (orange cloud) record stops HighLevel validating the domain.
- Verify in HighLevel. SSL is provisioned automatically and usually takes a few minutes. DNS changes can take up to 24 hours to spread, so if it does not verify straight away, wait before changing more records.
- Assign the domain to the funnel or website pages that should use it.
Root domain or subdomain?
If your main website is hosted somewhere else, keep it there and connect a subdomain such as offers.yourdomain.com or book.yourdomain.com to HighLevel. Pointing the root domain at HighLevel replaces your website. Only do that when HighLevel hosts the whole site.
Sites domain vs email sending domain
Connecting a domain for funnels and websites does not set up email. Sending email from your own domain needs a separate dedicated sending domain with SPF, DKIM and DMARC records, and that is where most deliverability problems start. Our email deliverability guide covers it, and agencies setting up branded app and API domains should read the white label guide too.
Still not connecting?
Run through the usual culprits in order: wrong DNS provider, a conflicting old record, propagation still in progress, Cloudflare proxy on. If all four check out and it still fails, HighLevel support can see the validation error on their side.
Domain connection, sending-domain authentication and the rest of the technical setup are included in every build we do. See our GoHighLevel expert page.
Sources
- HighLevel, set up a root domain or subdomain for HighLevel sites, modified September 27, 2026.