# Failing PCI Vulnerability Scan

**URL:** <https://community.hubspot.com/t/failing-pci-vulnerability-scan/127986>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [March 14, 2025, 4:00pm UTC](https://community.hubspot.com/t/failing-pci-vulnerability-scan/127986 "2025-03-14T16:00:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lshroff](https://avatars.discourse-cdn.com/v4/letter/l/e9bcb4/32.png) [@lshroff](https://community.hubspot.com/u/lshroff)\
**Post date:** [March 14, 2025, 4:00pm UTC](https://community.hubspot.com/t/failing-pci-vulnerability-scan/127986/1 "2025-03-14T16:00:25Z")

</div>

Hello,

We ran a PCI scan on our HubSpot website, and we are failing an element of our PCI scan with the scan stating that they found a vulnerability with SSL servers using TLS 1.0.

In our Settings → Domains and URLs, all our domains are set to require HTTPS + TLS 1.2+.

Is there any other setting we are missing to make sure no SSL-enabled servers are using TLS 1.0?

Thanks

---

<div class="post-metadata">

**Author:** ![Josh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/josh/32/17115_2.png) [@Josh](https://community.hubspot.com/u/Josh)\
**Post date:** [March 14, 2025, 5:26pm UTC](https://community.hubspot.com/t/failing-pci-vulnerability-scan/127986/2 "2025-03-14T17:26:22Z")

</div>

Hi @lshroff,

One thing you can check is that your TLS setting is set to 1.2+ for all domains on the account; which would include subdomains, secondary domains, and redirected domains (for example, non-www to www).

Just in case you don’t already have this: [SSL and domain security in HubSpot](https://knowledge.hubspot.com/domains-and-urls/ssl-and-domain-security-in-hubspot)

Josh

---

<div class="post-metadata">

**Author:** ![lshroff](https://avatars.discourse-cdn.com/v4/letter/l/e9bcb4/32.png) [@lshroff](https://community.hubspot.com/u/lshroff)\
**Post date:** [March 17, 2025, 11:06pm UTC](https://community.hubspot.com/t/failing-pci-vulnerability-scan/127986/3 "2025-03-17T23:06:10Z")

</div>

Thank you very much for your reply! We have configured our security settings based on the linked documentation, and will follow-up if we have questions!
