# Is LetsEncrypt compatible with all TLDs?

**URL:** <https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277>\
**Category:** Help\
**Created:** [January 8, 2021, 1:54pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277 "2021-01-08T13:54:32Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![dr00bie](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@dr00bie](https://community.letsencrypt.org/u/dr00bie)\
**Post date:** [January 8, 2021, 1:54pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/1 "2021-01-08T13:54:32Z")

</div>

I use LetsEncrypt for all my domains, so I am very familiar with it. However, I have always used it with very common TLDs, org, com, net, etc. Do "new" TLDs, like .rocks, work with LetsEncrypt?

---

<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:** [January 8, 2021, 2:40pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/2 "2021-01-08T14:40:55Z")

</div>

I believe so, I've been able to use it with every TLD that I have tried:

```auto
.cc
.com
.icu
.net
.org
.ovh
.pw
.tk
.top
.us
.work
.xyz

```

And we see all kinds of TLDs come through here.

[Unless the TLD is explicitly listed on some government block list - you should be fine]

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 8, 2021, 3:13pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/3 "2021-01-08T15:13:00Z")

</div>

Hi @dr00bie

> [@dr00bie](#):
>
> Do "new" TLDs, like .rocks, work with LetsEncrypt?

rocks isn't new, see

[https://publicsuffix.org/list/public\_suffix\_list.dat](https://publicsuffix.org/list/public_suffix_list.dat)

> // rocks : 2013-11-14 Dog Beach, LLC  
> rocks

So if a TLD is listet on the Public Suffix List, you should be able to create a certificate.

Or use the IANA list:

[https://www.iana.org/domains/root/db](https://www.iana.org/domains/root/db)

spa is the newest TLD - [.spa Domain Delegation Data](https://www.iana.org/domains/root/db/spa.html)

Or use online tools like [https://letsdebug.net/](https://letsdebug.net/) (from @_az) or [https://check-your-website.server-daten.de/](https://check-your-website.server-daten.de/) (own tool), there are domain name checks included.

In some cases it's possible that a domain is listed (PSL or IANA), but Letsencrypt doesn't have the newest version. But that's rare.

---

<div class="post-metadata">

**Author:** ![dr00bie](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@dr00bie](https://community.letsencrypt.org/u/dr00bie)\
**Post date:** [January 8, 2021, 4:21pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/4 "2021-01-08T16:21:50Z")

</div>

Thanks for the reply. I hadn't used it before, so I guess I should've said "new to me". I really appreciate the further documentation and information to review on this question.

---

<div class="post-metadata">

**Author:** ![dr00bie](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@dr00bie](https://community.letsencrypt.org/u/dr00bie)\
**Post date:** [January 8, 2021, 4:22pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/5 "2021-01-08T16:22:29Z")

</div>

Thanks for your reply! I was thinking it would, but having only used the most common TLD's, I didn't want my friend to buy a new domain that might not be compatible.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [January 8, 2021, 5:50pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/6 "2021-01-08T17:50:38Z")

</div>

I think in the **past** , the cross-signed intermediate had a resitriction for the `.mil` TLD. And I believe there are some restrictions to some TLDs like `.ir` due to some kind of block list from the USA goverment. But in principle, any TLD should work.

I myself, being a M.D. have a website with the `.md` TLD and for which I have a LE cert of course 😁

---

<div class="post-metadata">

**Author:** ![JamesLE](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jamesle/32/49364_2.png) [@JamesLE](https://community.letsencrypt.org/u/JamesLE)\
**Post date:** [January 8, 2021, 7:19pm UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/7 "2021-01-08T19:19:27Z")

</div>

> [@Osiris](#):
>
> there are some restrictions to some TLDs like `.ir` due to some kind of block list from the USA goverment

There’s not a restriction for the entire TLD.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [January 9, 2021, 12:14am UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/9 "2021-01-09T00:14:04Z")

</div>

> [@JamesLE](#):
>
> There’s not a restriction for the entire TLD.

Sorry, I didn't mean the entire TLD, but to some domains of that TLD, more as an example, as the US gvrmt blocklist includes domains from other TLDs too (but not 100&nbsp;% sure).

---

<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:** [January 9, 2021, 12:15am UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/10 "2021-01-09T00:15:10Z")

</div>

Tough crowd.

😅

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 9, 2021, 10:01am UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/11 "2021-01-09T10:01:59Z")

</div>

> [@Osiris](#):
>
> as the US gvrmt blocklist includes domains from other TLDs too (but not 100 % sure).

It's the

[https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx](https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx)

list: TXT:

[https://www.treasury.gov/ofac/downloads/sdnlist.txt](https://www.treasury.gov/ofac/downloads/sdnlist.txt)

Checked my local version (used in "check-your-website"):

| TLD | num\_Entries |
| --- | --- |
| .com | 220 |
| .ir | 123 |
| .ru | 58 |
| .net | 20 |
| .mx | 11 |
| .org | 6 |
| .ua | 6 |
| .co | 5 |
| .sy | 5 |
| .de | 5 |
| .ni | 4 |
| .my | 3 |
| .lb | 3 |
| .fi | 3 |
| .uk | 3 |
| .su | 2 |
| .cn | 2 |
| .ae | 2 |
| .ph | 2 |
| .ps | 2 |
| .rs | 1 |
| .tr | 1 |
| .tv | 1 |
| .tw | 1 |
| .ly | 1 |
| .ir/ferro\_gilan | 1 |
| .af | 1 |
| .am | 1 |
| .ar | 1 |
| .bh | 1 |
| .biz | 1 |
| .by | 1 |
| .com/about/fa | 1 |
| .com/porticellomalta | 1 |
| .com/zkgrandtown | 1 |
| .cy | 1 |
| .ac/ir | 1 |
| .edu/jalili | 1 |
| .fr | 1 |
| .hr | 1 |
| .info | 1 |
| .su/about | 1 |
| .ua/en/contacts | 1 |
| .ve | 1 |
| .vn | 1 |
| .za | 1 |

---

<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:** [February 8, 2021, 10:02am UTC](https://community.letsencrypt.org/t/is-letsencrypt-compatible-with-all-tlds/142277/12 "2021-02-08T10:02:02Z")

</div>

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