Something akin to lists of recommended TLS versions and cipher suites? [1][2]
[1]: https://wiki.mozilla.org/Security/Server_Side_TLS
[2]: https://www.owasp.org/index.php/TLS_Cipher_String_Cheat_Shee...
Something akin to lists of recommended TLS versions and cipher suites? [1][2]
[1]: https://wiki.mozilla.org/Security/Server_Side_TLS
[2]: https://www.owasp.org/index.php/TLS_Cipher_String_Cheat_Shee...
The main trust stores today are operated by Microsoft (for Windows), Apple (for Mac OS and iOS), Mozilla (Firefox and all the Free Unix systems), Google (Android), and Oracle (Java). Smaller or less frequently updated stores are operated by a large number of organisations, including Sony, Nintendo, Avaya, IBM and so on.
All the big stores either explicitly publish a list of what's trusted or provide an obvious way to work it out and some third party aggregates the results.
Most of the trust programmes are completely opaque and proprietary. Mozilla's is open to the public as you'd expect, Google openly relies on Mozilla's process although it takes its own final decisions. Microsoft uses the shared CCADB with Mozilla but doesn't publicly talk about its trust processes.
https://ccadb-public.secure.force.com/mozilla/CACertificates...
All that the certificates do is make it possible to ensure you are talking to the server at the address you intend to communicate with.
TLS has nothing to do with the morality, ethics or legality of the site operator.
It's too bad that the English word "trust" has so many meanings that people get confused about what it means in this context.
You mentioned TLS versions and cipher suites. TLS is documented in a set of RFCs, so if you want to answer the question "Does software X implement TLS version 1.2?", then you can answer that question by checking its behavior against RFC 5246.
As far as I'm aware, there is no RFC which quantifies trust.