# Test Cert Information

**URL:** <https://community.letsencrypt.org/t/test-cert-information/203549>\
**Category:** Help\
**Created:** [August 15, 2023, 9:42am UTC](https://community.letsencrypt.org/t/test-cert-information/203549 "2023-08-15T09:42:22Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![JRE](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@JRE](https://community.letsencrypt.org/u/JRE)\
**Post date:** [August 15, 2023, 9:42am UTC](https://community.letsencrypt.org/t/test-cert-information/203549/1 "2023-08-15T09:42:22Z")

</div>

My domain is:lmemcoin.xyz

Hi folks,

I am looking to locate the public facing link for the test cert issued for lmemcoin.xzy can you please help?

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [August 15, 2023, 10:40am UTC](https://community.letsencrypt.org/t/test-cert-information/203549/2 "2023-08-15T10:40:26Z")

</div>

I don't know what you mean. Would you explain how you got your test cert?

And what do you mean by the public facing link for it?

---

<div class="post-metadata">

**Author:** ![JRE](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@JRE](https://community.letsencrypt.org/u/JRE)\
**Post date:** [August 15, 2023, 11:26am UTC](https://community.letsencrypt.org/t/test-cert-information/203549/3 "2023-08-15T11:26:03Z")

</div>

Sorry mike, I did a typo, it was lmemecoin.xyz. Our IT guy left us and I read a post on this site earlier that there is ctn link (I think) to very cert that gets issued . It was a temporary cert. Can you help with that? Is there a link ot the cert issue info, not the cert itself of course, but the cert details.

Thanks

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [August 15, 2023, 11:35am UTC](https://community.letsencrypt.org/t/test-cert-information/203549/4 "2023-08-15T11:35:54Z")

</div>

I only see one valid cert for that name and it was issued by ZeroSSL not Let's Encrypt

You can download the cert itself but without its matching private key it won't be helpful

> **[crt.sh | c5f64820375327ca81bf4b7d6b41fca5a9898a50c6aede1c56063f4de127809e](https://crt.sh/?c=c5f64820375327ca81bf4b7d6b41fca5a9898a50c6aede1c56063f4de127809e)**
>
> Free CT Log Certificate Search Tool from Sectigo (formerly Comodo CA)

To become more familiar with automated certs you could start here

> **[Getting Started - Let's Encrypt](https://letsencrypt.org/getting-started/)**
>
> To enable HTTPS on your website, you need to get a certificate (a type of file) from a Certificate Authority (CA). Let’s Encrypt is a CA. In order to get a certificate for your website’s domain from Let’s Encrypt, you have to...

---

<div class="post-metadata">

**Author:** ![JRE](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@JRE](https://community.letsencrypt.org/u/JRE)\
**Post date:** [August 15, 2023, 11:44am UTC](https://community.letsencrypt.org/t/test-cert-information/203549/5 "2023-08-15T11:44:16Z")

</div>

Thanks for this Mike. Very grateful.

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [August 15, 2023, 1:41pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/6 "2023-08-15T13:41:34Z")

</div>

...and just in case it isn't clear: **all** certs are temporary--they're valid for a limited period of time, and then become invalid. In the case of Let's Encrypt certs, they're valid for 90 days, which could very well seem temporary--I can't speak to ZeroSSL. But any cert you get from anyone will expire, so you'll need to have a system in place to renew it (i.e., replace it with one that expires later) before that time.

---

<div class="post-metadata">

**Author:** ![JRE](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@JRE](https://community.letsencrypt.org/u/JRE)\
**Post date:** [August 15, 2023, 1:45pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/7 "2023-08-15T13:45:29Z")

</div>

Thanks Dan. I am learning as I go, so everybody's input is appreciated.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [August 15, 2023, 2:17pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/8 "2023-08-15T14:17:32Z")

</div>

> [@danb35](#):
>
> any cert you get from anyone will expire

NB:

> Subscriber Certificates issued on or after 1 September 2020 SHOULD NOT have a Validity Period  
> greater than 397 days and MUST NOT have a Validity Period greater than 398 days [[https://cabforum.org/wp-content/uploads/CA-Browser-Forum-BR-v2.0.0.pdf](https://cabforum.org/wp-content/uploads/CA-Browser-Forum-BR-v2.0.0.pdf) §6.3.2]

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [August 15, 2023, 2:19pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/9 "2023-08-15T14:19:38Z")

</div>

> [@9peppe](#):
>
> SHOULD NOT have a Validity Period  
> greater than 397 days and MUST NOT have a Validity Period greater than 398 days

It seems odd that the difference between the recommended ("SHOULD NOT") and the mandatory ("MUST NOT") is only one day.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [August 15, 2023, 2:23pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/10 "2023-08-15T14:23:13Z")

</div>

Very weird. 397/8 days is 13 months.

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [August 15, 2023, 2:41pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/11 "2023-08-15T14:41:11Z")

</div>

The standard maximum being 13 months is so that one can replace it every 12 months, and have a month of overlap in case of an issue with replacement. (Really the same reason that Let's Encrypt recommends replacing their 90-day certificates after 60 days.)

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [August 15, 2023, 2:45pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/12 "2023-08-15T14:45:14Z")

</div>

Does that mean that 10-day certs will need to be issued for 40 days?  
LOL

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [August 15, 2023, 2:46pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/13 "2023-08-15T14:46:36Z")

</div>

No, just that 10-day certs will require much more confidence in one's automation, alerting, and recovery times. (Plus confidence in your CA's automation, alerting, and recovery times for problems on their end.)

---

<div class="post-metadata">

**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\
**Post date:** [August 15, 2023, 9:03pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/14 "2023-08-15T21:03:56Z")

</div>

The 397 recommendation here is really "Don't push right up to the edge of what's allowed. Leave an extra day in case you mess up date math" (Like Let's Encrypt's "90 days plus 1 second" incident!)

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [August 15, 2023, 9:13pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/16 "2023-08-15T21:13:41Z")

</div>

Leap years!  
[365+1]+[31]=397  
longest year + longest month

---

<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:** [September 14, 2023, 9:13pm UTC](https://community.letsencrypt.org/t/test-cert-information/203549/17 "2023-09-14T21:13:46Z")

</div>

Closed on September 14, 2023, 9:13pm UTC

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