---
title: "SSL certificate pinning/HTTP public key pinning (HPKP)"
slug: "ssl-certificate-pinninghttp-public-key-pinning-hpkp"
updated: 2026-04-27T19:44:27Z
published: 2026-04-27T19:44:27Z
canonical: "help.quickbase.com/ssl-certificate-pinninghttp-public-key-pinning-hpkp"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SSL certificate pinning/HTTP public key pinning (HPKP)

Quickbase doesn't support the practice of hard-coding public SSL certs associated with the Quickbase platform into client-side agents, infrastructure, or code. Doing so results in unexpected outages and an inability to connect to Quickbase when certificates are rotated or renewed.

The frequent, unannounced, automated rotation and/or renewal of SSL Certificates (Root CA, Intermediate CA, and Leaf Certificate) on the Quickbase Platform preclude the use of client-side cert pinning.

## Certificate pinning resources

We recommend the following resources to learn more about this security practice:

- [Avoiding downtime: modern alternatives to outdated certificate pinning practices](https://blog.cloudflare.com/why-certificate-pinning-is-outdated/)
- [Certificate and public key pinning](https://owasp.org/www-community/controls/Certificate_and_Public_Key_Pinning)
- [What is certificate pinning](https://www.ssl.com/blogs/what-is-certificate-pinning/)