# How to enable certificate monitoring in synthetics
**URL:** https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024
**Category:** Synthetics
**Created:** [August 31, 2023, 8:22am UTC](https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024 "2023-08-31T08:22:04Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@UweW](https://discuss.elastic.co/u/UweW)
#### Post date: [August 31, 2023, 8:22am UTC](https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024/1 "2023-08-31T08:22:04Z")
Hi,
since i see the item "tls certificates" in the menu under synthetics, i assume that these can be read out by the tests accordingly.
I have now already set up some tests, but the certificate of the website is not listed here. What do I have to do so that the synthetic tests capture the certificate ?
By the way, with "uptime" the reading of the certificates works.
greetings Uwe
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [August 31, 2023, 10:10am UTC](https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024/2 "2023-08-31T10:10:53Z")
Hello @UweW
Synthetics app tls certificate page right now only works with lightweight monitors certs , for browser monitors we have an open issue to capture certs for browser pages as well
>
>
> Existing TLS certificate checks for Heartbeat monitors are useful to give an ear…ly warning that certificates are going to expire (and give users the time to renew them before they expire which may well impact the availability of the site).
>
> These are not currently available for Synthetics monitors, but the requirement and value that certificate checks provides, is just as valuable for these monitors (arguably more so as more hosts and content are included in Synthetic monitors, with a wider number of hosts needed to deliver it to make up the website).
>
> Use case
> \* As a Synthetic monitoring customer
> \* I want Heartbeat to check the status of TLS certificate for the root URL tested with Synthetics (the same as it does for HTTP checks)
> \* So I get visibility and early warning that the main host has an expiring certificate
>
> This requirement is being split into two phases.
>
> \*\*Phase 1\*\* certificate check the host of the main URL on step 1 (this issue)
>
> Feature:
> \* Check the certificate status for the host defined in the URL for the user journey (as shown in the \*\*Url\*\* column of the \*\*Monitors Overview\*\* page (if this is accessed via HTTPS)
> \* Show the certificate details in the \*\*TLS Certificate\*\* column on the \*\*Monitors Overview\*\* page
> \* The certificate details will also be shown on the \*\*Certificates status\*\* page, the same as other Heartbeat certificate checks
>
> In this example:
> !\[image\](https://user-images.githubusercontent.com/70908889/97740749-a3026280-1ad9-11eb-93c1-1d1c29b0a425.png)
> \* \`www.elastic.co\` would be checked and appear in the \*\*TLS Certificate\*\* column
> \* \`www.mydomain.com\` would not be checked (not HTTPS) so nothing would be shown in the \*\*TLS Certificate\*\* column
>
>
> \*\*Phase 2\*\*: a future enhancement to check the certificates of all hosts for a user journey monitor is detailed in \[this issue\](https://github.com/elastic/beats/issues/22327).
Regards
---
### Author:  [@UweW](https://discuss.elastic.co/u/UweW)
#### Post date: [August 31, 2023, 11:37am UTC](https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024/3 "2023-08-31T11:37:33Z")
this was the right hint.
Thanks' a lot
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 28, 2023, 11:37am UTC](https://discuss.elastic.co/t/how-to-enable-certificate-monitoring-in-synthetics/342024/4 "2023-09-28T11:37:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.