# Checking certificates dates

**URL:** https://community.letsencrypt.org/t/checking-certificates-dates/49210
**Category:** Help
**Created:** [December 29, 2017, 10:23pm UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210 "2017-12-29T22:23:47Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![PatricF](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patricf/32/34015_2.png) [@PatricF](https://community.letsencrypt.org/u/PatricF)
#### Post date: [December 29, 2017, 10:23pm UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/1 "2017-12-29T22:23:47Z")

</div>

I’ve taken a note that I need to renew 2 certificates for my site in two days. So i’ve run the command sudo certbot renew --dry-run with this output :

```
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/cloud.atakama-studio.ca.conf
-------------------------------------------------------------------------------
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cloud.atakama-studio.ca
Waiting for verification...
Cleaning up challenges

-------------------------------------------------------------------------------
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/cloud.atakama-studio.ca/fullchain.pem
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/atakama-studio.ca.conf
-------------------------------------------------------------------------------
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for atakama-studio.ca
http-01 challenge for www.atakama-studio.ca
Waiting for verification...
Cleaning up challenges

-------------------------------------------------------------------------------
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/atakama-studio.ca/fullchain.pem
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)

Congratulations, all renewals succeeded. The following certs have been renewed:
  /etc/letsencrypt/live/cloud.atakama-studio.ca/fullchain.pem (success)
  /etc/letsencrypt/live/atakama-studio.ca/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)

```

So from what I can see, they are not due for renewal ?

So i’ve run this command to check the dates

`echo | openssl s_client -connect localhost:443 -servername atakama-studio.ca 2>/dev/null | openssl x509 -noout -dates`

and here’s the output

```
notBefore=Dec 1 23:16:30 2017 GMT
notAfter=Mar 1 23:16:30 2018 GMT

```

So I’m not sure why it would still be good until mars 2018. I did not configure autorenew yet…

Any help to check that it will still be working in two days would be appreciated. Thanks !

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [December 29, 2017, 10:26pm UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/2 "2017-12-29T22:26:00Z")

</div>

Your site is behind a Cloudflare proxy, which is terminating SSL for you and doesn’t use your origin certificate (the Let’s Encrypt one).

That is why you have a different view of the validity period using s\_client versus certbot.

If you want to check the validity period of your installed Let’s Encrypt certificate, then you need to connect directly to the origin, not to Cloudflare.

---

<div class="post-metadata">

### Author: ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)
#### Post date: [December 29, 2017, 10:32pm UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/3 "2017-12-29T22:32:48Z")

</div>

“`certbot certificates`” will display the certificates it’s managing, including expiration dates.

---

<div class="post-metadata">

### Author: ![PatricF](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patricf/32/34015_2.png) [@PatricF](https://community.letsencrypt.org/u/PatricF)
#### Post date: [December 30, 2017, 12:20am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/4 "2017-12-30T00:20:15Z")

</div>

I’ve configure SSL to «Full (strict)» in Cloudflare, isn’t that the right way?

---

<div class="post-metadata">

### Author: ![PatricF](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patricf/32/34015_2.png) [@PatricF](https://community.letsencrypt.org/u/PatricF)
#### Post date: [December 30, 2017, 12:22am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/5 "2017-12-30T00:22:33Z")

</div>

running the `"certbot certificates"` here’s the output :

```
Found the following certs:
  Certificate Name: cloud.atakama-studio.ca
    Domains: cloud.atakama-studio.ca
    Expiry Date: 2018-03-01 23:16:26+00:00 (VALID: 61 days)
    Certificate Path: /etc/letsencrypt/live/cloud.atakama-studio.ca/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/cloud.atakama-studio.ca/privkey.pem
  Certificate Name: atakama-studio.ca
    Domains: atakama-studio.ca www.atakama-studio.ca
    Expiry Date: 2018-03-01 23:16:30+00:00 (VALID: 61 days)
    Certificate Path: /etc/letsencrypt/live/atakama-studio.ca/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/atakama-studio.ca/privkey.pem

```

So it’s all good for 61 days i guess

---

<div class="post-metadata">

### Author: ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)
#### Post date: [December 30, 2017, 12:39am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/6 "2017-12-30T00:39:25Z")

</div>

> [@PatricF](#):
>
> I’ve configure SSL to «Full (strict)» in Cloudflare, isn’t that the right way?

Yup. 😄

> [@PatricF](#):
>
> So it’s all good for 61 days i guess

Yup. 😄

It looks like your certificates were issued on 2017-10-03 and renewed on Certbot's typical schedule on 2017-12-02.

Either you have very good timing, or automatic renewal _is_ set up. (It's automatic with many Certbot OS packages.)

---

<div class="post-metadata">

### Author: ![PatricF](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patricf/32/34015_2.png) [@PatricF](https://community.letsencrypt.org/u/PatricF)
#### Post date: [December 30, 2017, 1:06am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/7 "2017-12-30T01:06:44Z")

</div>

Alright, thanks for the help !

---

<div class="post-metadata">

### Author: ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)
#### Post date: [December 30, 2017, 2:01am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/8 "2017-12-30T02:01:27Z")

</div>

By the way… I _meant_ to link a list of your domain’s certificates:

[https://crt.sh/?Identity=%atakama-studio.ca&iCAID=16418](https://crt.sh/?Identity=%25atakama-studio.ca&iCAID=16418)

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)
#### Post date: [January 29, 2018, 2:01am UTC](https://community.letsencrypt.org/t/checking-certificates-dates/49210/9 "2018-01-29T02:01:28Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
