# Wat gebeurt er als mijn domein HTTP is?

**URL:** <https://meta.discourse.org/t/what-happens-if-my-domain-is-http/162482>\
**Category:** Product Support\
**Created:** [30 augustus 2020 om 18:34 UTC](https://meta.discourse.org/t/what-happens-if-my-domain-is-http/162482 "2020-08-30T18:34:33Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![anon23840344](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@anon23840344](https://meta.discourse.org/u/anon23840344)\
**Post date:** [30 augustus 2020 om 18:34 UTC](https://meta.discourse.org/t/what-happens-if-my-domain-is-http/162482/1 "2020-08-30T18:34:33Z")

</div>

I have a domain that loads over HTTP. It being a single-page, static website, conversion to HTTPS hasn’t been a priority. I have now added a subdomain for discourse, and curiously it loads over HTTPS.

How can Discourse use HTTPS, when I’ve not invested the time to convert my domain to HTTPS?

Could this HTTP/HTTPS disparity cause problems for my Discourse users?

The Meta post https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709 says “This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) automatically enables HTTPS by default.” I followed that official guide when adding my Discourse, so I might presume that Meta post is non-applicable.

Thank you.

---

_[View the full topic](https://meta.discourse.org/t/what-happens-if-my-domain-is-http/162482)._
