# OV, EV certificates

**URL:** <https://community.letsencrypt.org/t/ov-ev-certificates/54546>\
**Category:** ISRG/Organizational\
**Created:** [March 1, 2018, 4:31pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546 "2018-03-01T16:31:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kurisu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kurisu/32/20805_2.png) [@kurisu](https://community.letsencrypt.org/u/kurisu)\
**Post date:** [March 1, 2018, 4:31pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/1 "2018-03-01T16:31:24Z")

</div>

Hi.

Let’s Encrypt (in future) create a API for identify and EV verification for domains?

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 1, 2018, 4:31pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/2 "2018-03-01T16:31:48Z")

</div>

Hi,

LE will not support EV, OV certificate.

Thank you

---

<div class="post-metadata">

**Author:** ![kurisu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kurisu/32/20805_2.png) [@kurisu](https://community.letsencrypt.org/u/kurisu)\
**Post date:** [March 1, 2018, 4:32pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/3 "2018-03-01T16:32:34Z")

</div>

I know about that. I talk about future.

---

<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:** [March 1, 2018, 5:11pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/4 "2018-03-01T17:11:57Z")

</div>

…and I’m pretty sure @stevenzhu was talking about the future. The problem is automating the validation, which doesn’t strike me as possible. But it’s been discussed here many times; a search will find a good bit of that discussion.

---

<div class="post-metadata">

**Author:** ![jple](https://avatars.discourse-cdn.com/v4/letter/j/c5a1d2/32.png) [@jple](https://community.letsencrypt.org/u/jple)\
**Post date:** [March 1, 2018, 6:28pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/5 "2018-03-01T18:28:14Z")

</div>

“Will Let’s Encrypt issue Organization Validation (OV) or Extended Validation (EV) certificates?  
We have no plans to issue OV or EV certificates.” from [https://letsencrypt.org/docs/faq/](https://letsencrypt.org/docs/faq/)

---

<div class="post-metadata">

**Author:** ![cc2e6](https://avatars.discourse-cdn.com/v4/letter/c/858c86/32.png) [@cc2e6](https://community.letsencrypt.org/u/cc2e6)\
**Post date:** [March 2, 2018, 2:36pm UTC](https://community.letsencrypt.org/t/ov-ev-certificates/54546/6 "2018-03-02T14:36:43Z")

</div>

Plus EV/OV certificates are of questionable value. Even amazon and google don’t use them.

> **[On The (Perceived) Value of EV Certs, Commercial CAs, Phishing and Let's Encrypt](https://www.troyhunt.com/on-the-perceived-value-ev-certs-cas-phishing-lets-encrypt/)**
>
> Last week I wrote about how Life Is About to Get a Whole Lot Harder for Websites Without HTTPS. Somewhere in the comments there, the discussion went off on a tangent about commercial CAs, the threat Let's Encrypt poses to them and subsequently, the...