How to Fix a Hubspot Root Domain Not Loading Over HTTPS

If your Hubspot-hosted website is not loading correctly over HTTPS at the root domain, visitors may see security warnings, redirect loops, or blank pages. This guide walks you through the exact checks and settings you need to review so your main domain loads securely and consistently.

The process focuses on your DNS configuration, SSL status, and redirect behavior to ensure the root domain correctly points to your Hubspot-hosted content.

Understand How Hubspot Hosts Your Root Domain

Before changing any settings, it is important to understand how content hosting and redirects work in your account. In many cases, Hubspot hosts content on a subdomain (such as www.example.com) while the bare root domain (example.com) simply redirects to that content.

When HTTPS is involved, your SSL certificate, redirect rules, and DNS records must all be aligned, or the root domain may fail to load over a secure connection.

Common Symptoms of Root Domain HTTPS Problems in Hubspot

If your Hubspot configuration is not correct, you may see one or more of the following issues:

The root domain does not load over HTTPS, but the www subdomain does.
Visitors are redirected repeatedly between HTTP and HTTPS versions.
Browser security warnings appear about an invalid or missing certificate.
Your main domain opens a generic page instead of Hubspot content.

The steps below show you how to systematically resolve these issues.

Step 1: Check Domain Connection Status in Hubspot

Start inside your Hubspot settings to confirm the domain connection is healthy.

Sign in to your account and open your domain and URL settings.
Locate your primary domain (for example, www.example.com) and the root domain (example.com) if both are connected.
Confirm that the domain status shows as connected without errors.
Review which domain is set as primary for web content and which is set to redirect.

If your root domain is meant to redirect to a Hubspot-hosted subdomain, verify that this behavior is configured in your domain settings.

Step 2: Verify DNS Records for Your Hubspot Domains

DNS records must point your domains to the correct Hubspot endpoints. If your root domain is not loading over HTTPS, misconfigured DNS is often the cause.

DNS checklist for your Hubspot root domain

Confirm that the root domain (example.com) has the correct A record or ALIAS pointing where your hosting instructions specify.
Make sure the www subdomain has the CNAME record that points to the address provided in your domain setup instructions.
Avoid extra or conflicting DNS records that point your root domain to another server or service.

After you adjust DNS, allow time for propagation. Some changes may take several hours before they fully apply worldwide.

Important DNS notes for Hubspot SSL

For an SSL certificate to work correctly, your DNS records must be stable and point to the correct Hubspot endpoints during the verification and provisioning process. Any changes during that time can delay or break your secure connection at the root domain.

Step 3: Confirm SSL Certificate Status in Hubspot

A missing or incomplete SSL configuration can keep your root domain from loading securely even when DNS is correct.

In your settings, open the SSL or security section for your connected domains.
Verify that the SSL status for both the root domain and the www subdomain is active or enabled.
If SSL is still provisioning, wait until the status shows as complete before further testing.
If the certificate failed, follow any in-app guidance to reinitiate provisioning or correct DNS conflicts.

Once SSL is active, your root domain should be able to respond over HTTPS as long as it is properly redirected to your Hubspot-hosted content.

Step 4: Review Redirect Behavior for Hubspot Root Domains

Redirect rules determine how visitors move from one hostname or protocol to another, such as from HTTP to HTTPS or from the root domain to the www subdomain.

Configure HTTPS redirects in Hubspot

In many cases you want all traffic to use the secure version of your site. To achieve this, review your redirect behavior:

Ensure that the primary domain for your content is set correctly, often the www version.
Set the root domain to redirect to the primary domain when it is not hosting content directly.
Avoid duplicate redirect rules that send traffic back and forth between domains.

Misconfigured rules outside of Hubspot, such as redirects set at your DNS provider or legacy hosting, can conflict with in-app settings and prevent clean HTTPS loading.

Check for external redirects that affect Hubspot

URL forwarding settings for the root domain that may override Hubspot redirects.
Old HTTP-only redirects that do not forward traffic to HTTPS.
Any rule that redirects from HTTPS back to HTTP, causing loops or warnings.

Disable or update any conflicting rules so Hubspot can manage canonical and HTTPS redirects consistently.

Step 5: Test Your Root Domain Over HTTPS

After you verify DNS, SSL, and redirect behavior, test your site thoroughly.

Open an incognito or private browsing window.
Type https://example.com directly in the address bar.
Confirm that you are automatically redirected to the correct secure URL.
Ensure that the page content loads from your Hubspot site without browser warnings.

You can also use online HTTPS and redirect checkers to trace how your root domain and www subdomain respond to different requests.

Advanced Considerations for Hubspot Root Domains

In more complex setups with multiple brands or subdomains, you may need additional configuration to keep your root domain behavior consistent.

Multiple domains and Hubspot hosting

When you connect several domains, confirm that:

Only one domain is set as the primary for each content type.
Additional domains are configured as secondary or set to redirect.
The root domain for each brand has a clear destination and does not conflict with other connected domains.

Clear roles for each domain help ensure HTTPS works reliably across your entire site structure.

When to contact support or your DNS provider

If your root domain still will not load securely after following these steps, consider:

Reviewing the official documentation on domain and URL troubleshooting at this Hubspot help article.
Contacting your DNS provider to confirm there are no hidden records or caching layers interfering with SSL.
Reaching out to support with detailed notes on your DNS records, SSL status, and redirect settings.

Improve Overall Domain Strategy Beyond Hubspot

While this guide focuses on fixing a non-loading root domain in a Hubspot environment, the same principles apply to most secure web setups: clean DNS, valid SSL, and predictable redirects.

For broader SEO and technical strategy around domain architecture, canonicalization, and secure redirects, you can also review specialized resources such as Consultevo for advanced optimization guidance.

Summary: Restoring a Secure Root Domain in Hubspot

To fix a root domain that does not load over HTTPS in a Hubspot setup, you must align four key elements: domain connection status, DNS records, SSL configuration, and redirect behavior.

Check domain health and primary/secondary roles in your account.
Verify DNS points correctly to the required endpoints.
Confirm SSL is fully provisioned for both root and subdomain.
Clean up redirects so traffic flows once to the secure, canonical URL.

Once these components are in sync, your visitors will reach your content securely at the root domain without loops or warnings, and your Hubspot-hosted site will perform as expected.

Need Help With Hubspot?

If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.

Scale Hubspot

“`

Fix Hupspot HTTPS root domain issues