How To Change Privacy And Safety Settings On Domain_6

HubSpot automatically provisions a standard SAN SSL certificate through DigiCert when you connect a domain to your account. This usually takes a few minutes, but can take up to four hours.

If you've purchased the custom SSL add-on, you can upload custom SSL certificates to HubSpot. You can also configure security settings for each connected domain, such as TLS version and security headers.

Please note: if you encounter errors during the SSL provisioning process, learn more about troubleshooting SSL certificate errors.

If you'd prefer to use a different provider or certificate type, you can add custom SSL certificates to your account by purchasing the custom SSL add-on. You cannot use a pre-existing SSL certificate, because this compromises the security of the certificate.

Please note : DigiCert is the certificate authority that provisions a certificate for your domain. If your domain has a Certification Authority Authorization (CAA) record, ensuredigicert.comis listed so SSL can be provisioned or renewed.

Pre-provision your SSL certificate

If you're moving your existing site to HubSpot, you may want to pre-provision an SSL certificate so there's no SSL downtime. You can pre-provision an SSL certificate whileconnecting a domain to HubSpot.

To pre-provision an SSL certificate:

On theDNS Setup page of the domain connection process, a banner will appear if your site has an existing SSL certificate. ClickClick here to begin the provisioning process.
Follow the instructions in the dialog box:
- Log in to your DNS provider account, such as GoDaddy or Namecheap.
- In your DNS provider, navigate to the DNS settings screen where you manage your DNS records.
- Create new DNS records according to the dialog box using the Host (name) andValue values provided in the dialog box.

Please note: if you're using Network Solutions, Namecheap, or GoDaddy, you do not need to copy the root domain. Your provider will add a root domain to the end of the DNS record automatically.

ClickVerify. It can take up to four hours for your changes to process. If you get an error when clicking Verify, wait a few minutes then click Verify to check again.

Once your certificate has been pre-provisioned, a confirmation banner will appear in the domain connection screen. You can then continue connecting your domain.

ssl-pre-provision-success

Domain security settings

You can customize the security settings for each subdomain connected to HubSpot. Security settings include your website protocol (HTTP vs. HTTPS), TLS version, and your website security headers.

To update a domain's security settings:

In your HubSpot account, click the settings settings icon in the main navigation bar.
In the left sidebar menu, navigate toWebsite > Domains & URLs.
Click Edit next to the domain, then selectUpdate domain security settings .

HTTPS protocol

You can require all pages on your site to load securely over HTTPS. Once this is enabled, content loaded over HTTP, such as images and stylesheets, will not load on your site. Content loaded over HTTP on an HTTPS site is referred to as mixed content. Learn how to resolve mixed content errors on your page.

To turn on HTTPS protocol, select the Require HTTPS checkbox.

TLS version

By default, HubSpot servers will accept a connection using TLS 1.0 and above.

To change which TLS versions are supported, click the TLS version dropdown menu and select thelowest TLS version that you want to support. Connections attempting to use a TLS version lower than the minimum set will fail.

TLS-version

Security headers

You can configure your domain security and turn on security headers for each domain.

HTTP Strict Transport Security (HSTS)

You can add an extra layer of security to your website by enabling HTTP Strict Transport Security (HSTS). HSTS instructs browsers to convert all HTTP requests to HTTPS requests instead. Enabling HSTS adds the HSTS header to responses for requests made to the URLs on the subdomain.

To enable HSTS, click the Security headers tab, then select theHTTP Strict Transport Security (HSTS) checkbox.

security-HSTS-setting

To set how long browsers should remember to convert HTTP to HTTPS requests, click the Duration (max-age) dropdown menu and select aduration.
To include the preload directive in the domain's HSTS header, select the Enable preload checkbox. Learn more about HSTS preloading.
To include the HSTS header in all subdomains under the selected subdomain, select the Include subdomains checkbox. For example, if HSTS is enabled forwww.examplewebsite.com and theInclude subdomains checkbox is selected,cool.www.examplewebsite.com will also have HSTS enabled.

Learn more about the HSTS header.

Additional domain security settings ( CMS Hub only)

If you have a CMS Hub account, you can enable the additional security settings below.

X-Frame-Options

Enable the X-Frame-Options response header to indicate whether or not a browser can render a page in <frame>, <iframe>, <embed>, or <object> HTML tags.

To enable X-Frame-Options, select the X-Frame-Options checkbox, then select aDirective from the dropdown menu:

To prevent pages on your domain from being loaded on any page in the above tags, select deny.
To allow pages on your domain to load in the above tags across your domain only, selectsameorigin.

Learn more about the X-Frame-Options header.

X-XSS-Protection

Enable the X-XSS-Protection header to add a layer of security for users of older web browsers by preventing pages from loading when cross-site scripting is detected.

To enable this header, select the X-XSS-Protection checkbox, then select anXSS setting from the dropdown menu:

To disable XSS filtering, select0.
To remove the unsafe parts of a page when a cross-site scripting attack is detected, select1.
To prevent the rendering of a page if an attack is detected, select1; mode=block.

Learn more about the X-XSS-Protection header.

X-Content-Type-Options

Enable the X-Content-Type-Options header to opt pages out of MIME type sniffing. Enabling this setting tells the browser to follow the MIME types advertised in the Content-Type headers.

x-content-type-options

Learn more about the X-Content-Type-Options header.

Content-Security-Policy

Enable the Content-Security-Policy header to control resources that the user agent can load on a page. This header helps to prevent cross-site scripting attacks.

To enable the Content-Security-Policy header, select theContent-Security-Policy checkbox, then specify your Policy directive s. For a list of available directives, check out Mozilla's Content-Security-Policy header guide.

To allow <script> elements to execute only if they contain a nonce attribute matching the randomly-generated header value, selectEnable nonce.

content-security-policy-header

Content-Security-Policy-Report-Only

Enable the Content-Security-Policy-Report-Only header to monitor policy directives. Policy directives will not be enforced, but the effects will be monitored, which can be useful when experimenting with policies.

To enable this header, select theContent-Security-Policy-Report-Only checkbox, then enter yourPolicy directives.

To allow <script> elements to execute only if they contain a nonce attribute matching the randomly-generated header value, selectEnable nonce.

content-security-policy-report-only-header

Learn more about the Content-Security-Policy-Report-Only header.

Referrer-Policy

Enable the Referrer-Policy header to control how much referrer information should be included with requests.

To enable this header, select theReferrer-Policy checkbox, then select aDirective from the dropdown menu.

referrer-policy-header For a definition of the available directives, see Mozilla's Referrer-Policy guide.

Feature-Policy

Enable the Feature-Policy header to control the use of browser features on the page, including <iframe> element content.

To enable this header, select theFeature-Policy checkbox, then enter yourDirectives. For a list of directives, see Mozilla's Feature-Policy guide.

feature-policy-header

Domains & URLs