# Long term server certificate **URL:** \ **Category:** MQTT\ **Created:** [January 23, 2024, 1:09pm UTC](https://community.hivemq.com/t/long-term-server-certificate/2641 "2024-01-23T13:09:08Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![AaronTLFranz](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/aarontlfranz/32/638_2.png) [@AaronTLFranz](https://community.hivemq.com/u/AaronTLFranz)\ **Post date:** [January 23, 2024, 3:18pm UTC](https://community.hivemq.com/t/long-term-server-certificate/2641/2 "2024-01-23T15:18:34Z")
Hello @zandonella , To start, welcome to the HiveMQ Community! We are always happy to see new faces interested in MQTT. This question is dependent on the version of HiveMQ that you are currently utilizing. For [self-managed brokers](https://www.hivemq.com/products/hivemq-self-managed/), these certificates are generated by the user implementing TLS/SSL, and as a result the duration of the certificate will be determined during the certificate chain creation process. For HiveMQ Cloud brokers, the current certificate is always available from the ‘FAQ’ section of our community forum ([here](https://community.hivemq.com/t/frequently-asked-questions/514)), or via direct link ([here](https://letsencrypt.org/certs/isrgrootx1.pem)). This currently has an expiration of June 4th, 2035. Additionally, Cloud users utilizing Starter, Professional, or Enterprise tiers are able to provide their own certificates as well, similarly to self-hosted users, which allows for users to provide their own certificates, and as a result dictate their own expiration periods. A blog post regarding this feature is available [here](https://www.hivemq.com/blog/enhance-iot-security-client-certificate-authentication/). Best, Aaron from the HiveMQ Team --- _[View the full topic](https://community.hivemq.com/t/long-term-server-certificate/2641)._