Publicsuffix/list should be replaced with dedicated solution


Right now Letsencrypt uses a list of public domains from
While the list is really convenient, it’s maintainers seems to have a strong negative attitude.
As an example, here is a pull request:
which is not merged (imo) only because maintainer doesn’t want it to be merged.

As a representative of a small group of people using and domains users, I would like to ask you to:
Either drop the list usage and establish your own list of domains
Or intervene current workflow to make it more user friendly

With best regards,
Ippolitov Igor.

Maintaing a list like that would take a considerable amount of time and resources for Let’s Encrypt. Can you propose how to find the money to hire people dedicated to discovering and maintaining such a duplicate resource?

Based on my reading of that PR, the maintainers aren’t being negative. Rather, they are saying that being added on the PSL isn’t just for bypassing Let’s Encrypt rate limits. Being on that list also causes several other things to happen like browsers not allowing cookie sharing and taking other protections. If a regular domain is added, it can cause all kinds of problems for the owner of that domain and it would be impossible to immediately reverse the inclusion as not every user of the list updates on the same schedule. They simply want the operator of the .ru TLD to confirm that,, and are public prefixes, much like .com, .net,, and are. Also, it looks like they are asking that the PR be adjusted for the addition to be put in the right spot to keep it clean and sorted. IMO, that’s not much to ask of someone who is responsible for running that TLD.


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