# What's the Let's Encrypt URL?

**URL:** <https://community.letsencrypt.org/t/whats-the-lets-encrypt-url/144562>\
**Category:** Issuance Tech\
**Created:** [February 5, 2021, 1:54am UTC](https://community.letsencrypt.org/t/whats-the-lets-encrypt-url/144562 "2021-02-05T01:54:22Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [February 7, 2021, 4:49am UTC](https://community.letsencrypt.org/t/whats-the-lets-encrypt-url/144562/21 "2021-02-07T04:49:28Z")

</div>

If I'm understanding all this correctly, we are basically considering two types of potato: 🥔

1. A stated URL that serves the directory (per the standard now) that could be basically anything
2. A standardized starting point to "discover" the URL stated in (1)

I feel like the current discovery path is basically "RTFM". Having a standardized discovery path that... wait for it... programmatically exposes the variously available ACME services and their directories, say through an associative array presented via JSON that maps the services to their directories, could serve as a type of standardized "super directory", an _index_ if you will. Granted you'd still need to understand what the indexed services mean, so a blurb could also be included in the JSON.

Did I actually just suggest creating an index page on the internet? 😂 How... novel.

---

_[View the full topic](https://community.letsencrypt.org/t/whats-the-lets-encrypt-url/144562)._