# HTTPS for local network only

**URL:** <https://community.letsencrypt.org/t/https-for-local-network-only/135173>\
**Category:** Help\
**Created:** [October 3, 2020, 10:15pm UTC](https://community.letsencrypt.org/t/https-for-local-network-only/135173 "2020-10-03T22:15:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 3, 2020, 10:48pm UTC](https://community.letsencrypt.org/t/https-for-local-network-only/135173/2 "2020-10-03T22:48:26Z")

</div>

Welcome to the Let's Encrypt Community, Henry 🙂

You could use dns-01 challenges that use TXT records created in your publicly reachable DNS zone to prove that you control the domain. The IP address of your server is irrelevant at that point.

> **[Challenge Types - Let's Encrypt - Free SSL/TLS Certificates](https://letsencrypt.org/docs/challenge-types/)**
>
> Last updated: Feb 24, 2020 | See all Documentation When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this...

---

_[View the full topic](https://community.letsencrypt.org/t/https-for-local-network-only/135173)._