How to
Connecting a domain to GoHighLevel
For a subdomain, add a CNAME pointing to sites.ludicrous.cloud. For a root domain, add an A record pointing to 162.159.140.166. Never both for the same host. If your DNS is on Cloudflare, the record must be set to DNS only, the grey cloud, because HighLevel does not support the Cloudflare proxy. That single setting is the most common reason a correct-looking setup fails.
Research-led reviewThe author has not used this product. Built from public sources.What this means
The author has not used this product. Everything here comes from six public sources: the maker's own site, its pricing and refund terms, its changelog, its support forum, counted complaints across recent public reviews, and a like-for-like comparison against the nearest alternatives. We never claim experience we do not have.
Which badge a page carries is enforced in the site build, not just in editing. A page cannot use first-hand language unless it has declared itself a real-use review, so the badge and the writing cannot drift apart. The full method
We earn a commission if you buy through links on this page, at no extra cost to you.How this works
You pay exactly what you would pay going direct. The maker pays us a share of their margin, not a surcharge on you.
We are never paid for a positive verdict, no maker sees a review before it publishes, and we publish verdicts recommending against products we could earn from. Commission rates never influence which products we cover or how we rank them. Full disclosure
The short version
- Subdomain gets a CNAME. Root domain has to use an A record, which is a DNS rule rather than a HighLevel limit.
- Cloudflare proxy breaks it. Grey cloud, not orange.
- Propagation is usually 1 to 10 minutes, not the 48 hours people brace for.
- SSL is issued automatically a few minutes after verification. Do not go hunting for a certificate to buy.
Affiliate link. We earn a commission if you subscribe, at no extra cost to you. 30 day free trial through HighLevel's Bootcamp offer, card required.
The records
| For | Type | Host / Name | Value |
|---|---|---|---|
| Subdomain, recommended | CNAME | www, or your subdomain | sites.ludicrous.cloud |
| Subdomain, alternative | A | www | 162.159.140.166 |
| Root domain, the only option | A | @ | 162.159.140.166 |
sites.ludicrous.cloud looks like a typo or a placeholder and is neither, which is why people retype it as something more sensible and then wonder why verification fails.| Typical propagation | 1 to 10 minutes |
| Worst case | 24 to 48 hours |
| SSL certificate | Issued automatically, 1 to 10 minutes after verification |
The gap between the typical case and the worst case is the useful part here. One to ten minutes is normal, so if twenty minutes have passed and nothing has verified, the problem is almost certainly the record rather than propagation. Waiting 48 hours to discover a typo is the most common way this task consumes an afternoon.
Root or subdomain
| Option | Good for | Cost |
|---|---|---|
| Root, example.com | A business whose whole web presence is in HighLevel | A record only, and it claims the apex hostname, so no other site can answer there. Email records still work |
| Subdomain, go.example.com | Keeping a WordPress site on the root while funnels live alongside | A slightly longer URL, which almost nobody notices in practice |
The default advice is a subdomain, and the reason is reversibility. Pointing your root domain at a funnel builder decides what answers at your apex, which means any existing website there stops being reachable at that address. Pointing go. or offers. at it affects nothing else and can be undone by deleting one record.
HighLevel will also enable www alongside a root domain with a 301 redirect to the root, which is the correct behaviour and one less thing to configure.
The Cloudflare problem
This deserves its own section because it produces a uniquely frustrating failure. The record is correct, the value is right, DNS lookups resolve, and verification still fails or the site loads with a certificate error. Everything looks fine, so people re-enter correct records repeatedly.
The cause is that Cloudflare's proxy sits between the visitor and HighLevel and terminates SSL itself, which prevents HighLevel from issuing and serving its own certificate. Click the orange cloud next to the record so it turns grey, wait a few minutes, and verification usually completes on its own.
The trade is real and worth stating: DNS only means you lose Cloudflare's caching, DDoS protection and analytics for that hostname. For a funnel or landing page that is typically fine. If those features are why you use Cloudflare, this is a reason to use a subdomain so the rest of your domain keeps them.
Affiliate link. We earn a commission if you subscribe, at no extra cost to you. 30 day free trial through HighLevel's Bootcamp offer, card required.
Email records
| Record | What it does |
|---|---|
| SPF | Says which servers may send email as your domain |
| DKIM | Signs your email so it can be proved unaltered in transit |
| DMARC | Sets the policy when SPF or DKIM fails, and reports on delivery |
HighLevel generates these values for your domain rather than publishing fixed ones, so copy them from the platform exactly as shown. Unlike the funnel records, there is nothing here you can type from memory.
Do not skip them because the funnel already works. Sending marketing email from a domain with no SPF, DKIM or DMARC is the fastest route to the spam folder, and deliverability problems are much harder to diagnose after the fact than to prevent now. Sending is metered separately at $0.675 per 1,000 emails, covered on the pricing page.
When it does not work
| Check | |
|---|---|
| 1 | Never create a CNAME and an A record for the same host. Pick one. |
| 2 | Cloudflare proxy is not supported. Set the record to DNS only, the grey cloud. |
| 3 | Set TTL to 300 seconds while you are working, so mistakes are cheap to fix. |
| 4 | Root domains cannot use CNAME. That is a DNS rule, not a HighLevel limitation. |
One addition that is not in the documentation but causes the same symptom: some registrars append the domain to whatever you type in the host field. Enter go.example.com there and you create a record for go.example.com.example.com, which resolves for nobody. Enter just go.
If everything checks out and it still fails, the fastest diagnosis is to look up the record from outside your own network, since a stale local DNS cache will happily serve you the old answer for hours after the change is live everywhere else.
Domains are configured inside the account
The email records are generated per domain, so they only exist once there is an account to generate them. The funnel records above are the same for everyone.
Start the GoHighLevel trialAffiliate link. We earn a commission if you subscribe, at no extra cost to you. 30 day free trial through HighLevel's Bootcamp offer, card required.
If this is for one business rather than clients
Systeme.io connects custom domains on its free plan, with the same kind of CNAME or A record and no sub-account structure to work through first.
Start free on Systeme.ioAffiliate link to Systeme.io. We earn a commission if you later upgrade, at no extra cost to you. No card required, and the free plan does not expire.
If page quality is the priority
Domain setup is much the same everywhere. What differs is what you put on the domain, and ClickFunnels has the better builder of the three at the same $97 as GoHighLevel Starter.
Start the ClickFunnels trialAffiliate link. We earn a commission if you subscribe, at no extra cost to you. 14 day trial, then $97 a month with a 30 day money-back guarantee.
Common questions
What DNS record do I use for GoHighLevel?
A CNAME pointing to sites.ludicrous.cloud for a subdomain, or an A record pointing to 162.159.140.166 for a root domain. A subdomain can use an A record instead if you prefer, but never create both a CNAME and an A record for the same host.
Why is my GoHighLevel domain not verifying?
Most often the Cloudflare proxy, which is not supported and must be set to DNS only, the grey cloud. The next most common causes are both a CNAME and an A record on the same host, and a registrar that appends your domain to the host field so you end up with go.example.com.example.com.
Does GoHighLevel work with Cloudflare?
Yes, but only with the proxy off. Set the record to DNS only rather than proxied. You lose Cloudflare caching and DDoS protection for that hostname, which is a reason to point a subdomain at HighLevel rather than your root domain.
How long does a GoHighLevel domain take to work?
Usually 1 to 10 minutes, with a worst case of 24 to 48 hours. If twenty minutes have passed with nothing verified, check the record rather than waiting, because it is far more likely to be a typo than slow propagation.
Do I need to buy an SSL certificate?
No. HighLevel issues one automatically, typically 1 to 10 minutes after the domain verifies. If you are seeing a certificate error after that, the usual cause is the Cloudflare proxy terminating SSL before the request reaches HighLevel.
Can I use my root domain instead of a subdomain?
Yes, with an A record to 162.159.140.166, since root domains cannot use CNAME records. A subdomain is the safer default because it leaves the rest of your domain untouched and can be undone by deleting one record.
Last reviewed September 3, 2026