Reason for not publishing list

[serverco]

@My1

most implementations on how people generate their keys are open source the exact generation data for your key is secret and random because that is what is used to encrypt but the algorhythms are mostly open source.

Exactly as been done here. The "algorithm" or methodology has been stated .....

@jsha

Here's our methodology to fill in the main part of our blacklist: We started with the Alexa top 1k domains. This was both too aggressive and not aggressive enough. There were a number of domains in that list that we didn't consider high enough risk to prevent issuance.

Our security officers manually reviewed the list to trim the list, ending with less than 200 "names." They're from all categories - banks, shopping, software, online services, and more.

At the same time, we added the notion of "permute." Specifically, there are a number of domains, like "google" or "hotmail," where domain.TLD exists and is registered to the same entity in almost all TLDs. However, in smaller TLDs the domain.TLD may not have enough traffic to wind up in the Alexa top 1k. So we introduce the notion of "permuting" a domain: If we believe a domain to be in this category, we blacklist it in each TLD.

The pure data hasn't.

@My1

what is that SDN thing?

Specially Designated Nationals List (SDN) - Specially Designated Nationals And Blocked Persons List (SDN) Human Readable Lists | Office of Foreign Assets Control