Your domain is stuck on Pending, shows a DNS error, or the page is not secure. This guide explains what each message means and how to fix it.
Before you start
Know where your domain's DNS is managed. This is usually the company you bought the domain from, such as GoDaddy, Namecheap, Cloudflare, or Squarespace. If you moved your nameservers elsewhere, edit DNS there instead.
Keep the hub open at Settings > Domains & URL Redirects so you can copy the exact record values it shows you.
Be patient. DNS changes can take from a few minutes up to 24 to 48 hours.
How the domain gets connected
Automatic: If your provider is GoDaddy, Google Domains, or Cloudflare, go to Settings > Domains & URL Redirects, click Connect a Domain, choose what you are connecting, enter your domain, click Authorize, and complete your provider's prompts.
Manual: For any other provider, choose the manual records option. The hub shows you the A, CNAME, and TXT records. Copy them into your provider's DNS settings exactly as shown, save, and wait.
Tip: if you add "www", the hub offers to add the root domain too. Accept it so both versions work.
Status: Pending
Pending means the hub has not yet seen the correct records at your provider.
Wait. Many domains verify within an hour, but some take up to 24 hours.
If it is still Pending after 24 hours, compare each record at your provider with what the hub shows. One wrong character is enough to block it.
Make sure the records are on the correct name:
@for the root domain,wwwfor www, or the exact prefix for a subdomain such asoffers.Save and verify again in the hub.
Error: DNS Records Do Not Match
The records the hub can see are different from the ones it asked for. Common causes: a typo, records added at the wrong DNS host, or a record changed after connecting.
In the hub, copy the required values from the setup screen again.
At your DNS host, check each record's type, name, and value, one by one.
Remove or update only the conflicting records for that exact domain or subdomain. Do not delete unrelated records such as email (MX) or verification (TXT) records.
Save, wait, then verify again.
Cloudflare users: set the proxy status to DNS Only (the grey cloud) for the A and CNAME records.
Error: Multiple A Records
Your domain is pointing to more than one place at once. Keep only the A record whose value matches what the hub gave you, remove any other A records for that same name, save, and verify again.
Error: AAAA Record Conflict
An AAAA record is an IPv6 address, often created automatically or left behind by an old host. Remove all AAAA records for the exact domain or subdomain you are connecting, save, and verify again.
SSL is not working or the site shows "not secure"
The hub issues the SSL certificate automatically once the domain is connected and the records are correct. If it never appears:
Confirm the domain is fully connected (not Pending) and the records match.
Check for a CAA record at your provider. It controls who may issue certificates for your domain. Remove the CAA records for the affected domain, or update them to allow
pki.goog.Save and verify again.
Error: Domain is Connected Elsewhere
The domain is already attached to another product or account. Changing DNS will not fix this.
Check any other hub accounts you have access to, including websites, funnels, and client portals.
Remove the domain from the old place if you no longer need it there, then try again.
If you cannot find it, contact support with the domain, what you are connecting it to, a screenshot of the error, and proof that you own the domain.
Still stuck? Open the chat widget in the hub and our support team will help.