HubSpot gives each account its own values in the connect wizard: www is a CNAME to your-hub-id.groupN.sites.hubspot.net, and the root takes the A records the wizard shows — addresses in HubSpot’s 199.60.103.x range. Remove AAAA records and extra A records, and keep Cloudflare’s proxy off.
The records to add
| Name | Type | Value |
|---|---|---|
www | CNAME | 145335.group35.sites.hubspot.net (your own) |
@ | A | The addresses the connect wizard shows (199.60.103.x) |
HubSpot sets up the redirect between the root and www itself.
| Older sites | www as a CNAME to a …secure0128.hubspot.net name — still HubSpot |
| Verification | The DNS check itself — 15 to 80 minutes |
| Certificate | Google Trust Services, minutes to 4 hours |
Check your domain
Enter your domain: we look up its records and compare them with what HubSpot expects — the root, www, and any record left over from before.
Step by step
- In HubSpot, open Settings → Domains & URLs → Connect a domain and follow the wizard.
- At your DNS host, add the www CNAME and the root A records exactly as the wizard shows them.
- Remove AAAA records and any other A records on those names.
- Let HubSpot’s DNS check verify the domain, then wait for the certificate.
What to remove
- AAAA records on HubSpot-connected names.
- Extra A records.
The certificate
HubSpot’s certificates come from Google Trust Services: a CAA record must include 0 issue “pki.goog”. Names longer than 64 characters cannot have one, and a domain listed by Google Safe Browsing or PhishTank is refused.
Common mistakes
- A DNS host adding the domain again — www.example.com.example.com.
- Cloudflare’s proxy switched on.
- A CNAME where HubSpot asks for an A record, or the reverse.
Sources
Records checked on 26 September 2026 against these official sources:
- Connect a domain to HubSpot — knowledge.hubspot.com
- Update DNS records — knowledge.hubspot.com
- Troubleshoot SSL certificate errors — knowledge.hubspot.com