HubSpot creates system domains so that parts of your account can function before you connect a branded domain. These default URLs may support hosted content, files, tracking-related assets, meetings or other platform features, depending on your HubSpot configuration.
To view them, open the settings area, go to the section for Domains & URLs, and review the domains associated with your account. The exact labels and layout can change, so the important task is to identify each domain’s purpose rather than rely only on its name.
System domains are operational defaults, not a replacement for a deliberate domain strategy. Use connected branded domains for public-facing experiences where appropriate, while documenting which platform functions still depend on default HubSpot URLs. This makes publishing, troubleshooting and ownership clearer.
What is a HubSpot system domain?
A HubSpot system domain is a platform-provided URL associated with your HubSpot account. It exists even when your organisation has not connected a custom domain, and it gives HubSpot a working address for functions that need to publish, host or resolve content.
The domain may appear in settings, generated links or technical configuration. Its presence does not automatically mean that every visitor-facing page uses it. The domain assigned to a particular asset depends on the content type, your connected domains and the publishing settings for that part of the account.
Common examples of platform-managed URL functions include hosted files, landing pages, website pages, blog content, knowledge base content, meeting pages and subscription-related pages. The exact set varies by HubSpot product configuration and account permissions.
A system domain is a working platform address. It is not necessarily the right public address for your brand.
System domains, connected domains and primary domains are different
These terms are often treated as interchangeable, but they describe different parts of the domain model.
Provided by HubSpot
This is a default address managed by HubSpot. It supports account functionality and may remain available as a fallback or technical reference.
Owned by your organisation
This is a domain or subdomain that your team connects and verifies so HubSpot can publish selected content under a branded address.
A connected domain is not automatically the primary domain for every HubSpot content type. A team can connect a domain successfully and still publish a page, file or knowledge base article from a different address if the relevant assignment has not been reviewed.
This distinction matters during migrations. Replacing a system domain with a branded domain is not one global switch. It is a configuration decision across content types, assets, links, tracking and ownership.
How to view system domains in HubSpot
Use this sequence to locate and interpret the domain list:
The goal is not simply to copy a URL from the screen. The useful outcome is a domain inventory that explains what each address does and who owns the related decision.
How to identify what a system domain is used for
HubSpot may show more than one default or system-related address. Names and labels can differ, so review the record using four questions:
- What is the domain type? Determine whether it is system-managed, connected, redirected or used for a particular platform function.
- What does it host? Check whether the address relates to web content, files, meetings, email preferences or another asset category.
- Which domain is primary? Confirm whether a branded domain has been selected for the relevant content type.
- Who owns the decision? Record whether marketing, sales operations, IT or a web team is responsible for changes and reviews.
A domain audit is incomplete if it lists URLs without linking each URL to a business function, content owner and publishing rule.
Do not assume that a HubSpot-owned root domain is an error. It may be an expected part of the account’s setup. Investigate it when it appears in a customer-facing asset that should use a branded address, when a link resolves incorrectly, or when a migration has left mixed domain assignments behind.
How system domains interact with connected branded domains
Connecting a branded domain allows HubSpot to serve selected content under your organisation’s URL. It does not automatically change every existing link or asset. Domain behaviour depends on the content type and the assignments configured in your account.
For example, a marketing team may connect www.example.com for website pages and a separate subdomain for landing pages. A file link, meeting page or subscription page may have a different configuration. The team should therefore test the actual URLs generated for each important customer journey rather than assume that one domain setting controls everything.
System domains can continue to matter behind the scenes or as defaults. They may also appear in older assets, internal references or technical troubleshooting. This is why removing or ignoring them is usually less useful than documenting their role.
A practical decision sequence
- List the public journeys that matter, such as website visits, campaign landing pages, form submissions, file downloads and meeting bookings.
- Map each journey to the HubSpot content type or tool that creates the URL.
- Confirm the intended branded domain for each content type.
- Check newly generated and existing links, including links in emails, templates and internal documentation.
- Assign an owner for future domain changes and periodic review.
This sequence separates domain architecture from the technical act of connecting a domain. That separation reduces the risk of a successful connection producing an inconsistent customer experience.
Operational checks before changing domain settings
Before changing a primary domain or redirecting content, check the dependencies around it. Domain changes can affect links in campaigns, sales enablement documents, templates, forms, embedded content and reporting references.
- Record every system and connected domain currently visible in settings.
- Document the intended domain for each content type.
- Check whether important public links still use a default address.
- Verify that the relevant domain is authenticated, active and appropriate for its intended use.
- Test links from real emails, pages, forms and booking journeys.
- Document the change owner, review date and rollback approach.
Keep email sending configuration separate from website hosting decisions. A domain used to publish web content is not automatically the same as a domain used for email authentication or sending. Treating them as separate configuration areas makes troubleshooting more precise.
Also distinguish a URL problem from a content problem. If a page has the wrong address, changing the domain may not fix an incorrect redirect, an outdated template link or a hard-coded URL in an email. Trace the complete path from the asset to the link that exposes it.
Example: diagnosing a default URL in a customer journey
Imagine a hypothetical company that connects its branded website domain to HubSpot. Its main pages use the branded domain, but a campaign email contains a file link with a HubSpot system domain. The link works, so the issue is not necessarily availability.
The operations owner should first identify how the file is hosted, whether files are intended to use the branded domain, and whether the email template contains an old copied URL. If the file domain assignment is correct, the team can decide whether the default address is acceptable. If it is not, the team can correct the relevant domain configuration or replace the outdated link, then test the email again.
This example shows why a system domain should be investigated in context. The right response may be a configuration change, a template update, better documentation or no change at all.
When a default URL appears, ask what business state it represents before deciding that it is a defect.
When to involve a HubSpot administrator or consultant
Routine viewing is usually straightforward, but domain work becomes more sensitive when several teams publish content, when the account is being migrated, or when links are embedded across customer-facing systems.
Bring in an administrator or implementation specialist when you need to rationalise multiple subdomains, standardise ownership, audit links across content types, coordinate redirects or align domain settings with a broader CRM and marketing operations design. The useful work is not just changing a value in HubSpot. It is making the intended publishing rules visible and repeatable.
ConsultEvo’s HubSpot consulting service can support configuration, automation, pipeline design, integrations and reporting when domain decisions form part of a wider HubSpot operating model. For broader CRM dependencies, the CRM consulting service provides a related route for reviewing ownership, data flow and process design.
A system should be judged by whether teams can reliably answer where an asset is published, why that address is used and who can change it. More connected domains do not automatically create a better operating system.
What good domain governance looks like
Good governance is lightweight but explicit. Maintain a current record of system domains, connected domains, content assignments, responsible owners and known exceptions. Review it when a new content type is introduced, a domain is migrated or a customer-facing link changes.
The practical standard is clarity. Marketing should know which domain a campaign uses. Operations should know which setting controls it. IT or web owners should know what verification and security work is required. Reporting and support teams should know how to distinguish an expected system URL from a misconfiguration.
Viewed this way, HubSpot system domains are not merely a settings-page detail. They are part of the publishing and integration model of the account. Understanding them helps teams make deliberate choices about branding, reliability, troubleshooting and ownership.
Frequently asked questions
What is a system domain in HubSpot?
A system domain is a default URL provided and managed by HubSpot so account features can host or resolve content before, or alongside, connected branded domains.
Where can I view system domains in HubSpot?
Open HubSpot settings, find the Domains & URLs area within the relevant website or content settings, and review the system-managed and connected domains listed there. Interface labels can vary.
Does connecting a custom domain remove a HubSpot system domain?
No. A connected custom domain can become the primary address for selected content types, but the HubSpot system domain may remain available for platform functions, fallback behaviour or existing references.
Why is a HubSpot system domain still appearing in a public link?
The link may belong to a content type with a separate domain assignment, an older asset, a template with a copied URL or a function that still uses a system-managed address. Trace the specific asset and publishing rule before changing settings.
Are HubSpot website domains and email sending domains the same thing?
Not necessarily. Website hosting, file links, email sending and email authentication can involve separate domain settings. Review each function independently when auditing a HubSpot account.
Make HubSpot domain settings easier to operate
If system domains, connected domains and publishing rules are difficult to trace, ConsultEvo can help document the current setup, clarify ownership and align HubSpot configuration with the processes your teams actually use.
