Doubt with domain ending in

Dear Colleagues,

I’ll start by apologizing for the typos. I am Brazilian and not much knowledge of the English language.

I registered a new domain, As usual, I’m trying to implement the Let’s Encrypt certificate on it.

I run the following command:

letsencrypt --webroot certonly -d -d -d -d -w /var/www/html

It is the same procedure that I do with all the domains that I have running on my server.

However, in this case, I am getting the following error:

“There were too many requests of a given type :: Error creating new order :: too many certificates already issued for: see

From what I understand, it is as if Let’s Encrypt was recognizing as if it were a subdomain of the domain and that many certificates have already been created for the domain.

That’s what I’m getting at. Can someone help me?
The version of the server’s operating system is Debian GNU / Linux 9.13 (stretch).

Let’s Encrypt was installed from this tutorial:

Obs .: With all the others my domains work, only the one that doesn’t want to work.

I will be very grateful if anyone can help me!

Kind regards,

Henrique Fagundes


Just adding to this thread that I also have this issue with a domain.

Both of these are new first level domains, in fact (not user domains), under the registrar, among others as follows in the complete list:


You can see the official list of new first-level domains in the official announcement (in Portuguese) or the FLD category list (also in Portuguese).

Therefore, they should be treated the same way as, say, “”.

1 Like

Hi @HenriqueBR & @EpicEric,

Let’s Encrypt relies on a list called Public Suffix List and pull domains/zones from there to determine tld (on rate limit).

From the commits on GitHub, i think the operators from .br domains submitted and merged these domains 10 days ago Source. (10 days is relatively new in all means)

I think Let’s Encrypt will take some time to merge the new updates, pinging @jsha for more information.


Hi @HenriqueBR

there is already a PR:


This change will be deployed into production on July 30th, 2020 @ ~17:30 UTC.


Thank you! Thanks to everyone who responded.

As I understand it, my “problem” will resolve itself, after the 30th of July.


Yes, that’s correct.


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