If an old form embed, a legacy integration, or a script from a vendor you haven't thought about in years suddenly stopped talking to your HubSpot-hosted pages this month, there's a specific, dateable reason: on October 14, 2026, HubSpot raised the minimum encryption standard required to connect to HubSpot-hosted domains.
What is TLS 1.2, and why did HubSpot change it?
TLS stands for Transport Layer Security. It's the protocol that encrypts the connection between a visitor's browser (or another system) and a website, so the data passing back and forth can't be read or tampered with along the way. Every time you see a padlock icon in your browser's address bar, TLS is the reason. Older versions of TLS (1.0 and 1.1) have known weaknesses that have made them unsuitable for handling anything sensitive for years, which is why most major platforms have been phasing them out.
HubSpot's change means any connection still trying to use TLS 1.0 or 1.1 to reach a HubSpot-hosted domain no longer works. The direct answer to "what do I need to do": check whether anything connecting to your HubSpot site, an embedded script, a third-party integration, an older plugin, still runs on one of the outdated TLS versions, and update or replace it if so.
What this means for your organization
For most nonprofits, this change is invisible. Modern browsers, modern hosting, and any integration built or updated within the last several years already use TLS 1.2 or newer by default, so nothing changes for your visitors or your day-to-day HubSpot use. The organizations who should take a closer look are the ones running older, less frequently updated systems alongside their HubSpot site: an aging embedded widget from a vendor that hasn't shipped an update in a while, a custom integration built years ago and left alone since, or hardware (certain older point-of-sale systems or kiosks, for example) that hasn't had its software refreshed recently.
The practical check is straightforward: if everything on your HubSpot-connected site is working the way it was last month, you likely don't need to do anything. If you've noticed a form stopped submitting, an embed stopped loading, or a sync job that used to run quietly is suddenly failing, and the timing lines up with mid-October, an outdated TLS version on that specific tool is now the first thing worth ruling out, not a mystery to troubleshoot from scratch.
How to check
If you manage your own integrations, your vendor's documentation or support team can usually confirm which TLS version their product uses, and whether a setting or a software update is available to bring it current. If your website or HubSpot portal is managed by an outside team, this is a quick question to hand off rather than something you need to dig into yourself.
Security-related updates like this one rarely come with fanfare, but they're worth a glance whenever a platform you depend on announces one, since the cost of checking is a few minutes and the cost of not checking, for the rare organization actually affected, is a quietly broken integration nobody notices until a donor mentions a form that wouldn't submit.
Not sure if you're affected?
If you want a second set of eyes on your HubSpot integrations after a change like this, or you've noticed something acting up since mid-October, reach out to Tapp Network and we'll help you track it down.
.png)
