• Certificates and/or their contents are not published by the CA. This is policy. Privacy is considered more important than any reasons to make the the information available.
  • FWIW, Non-publication is in line with industry practice for commercial CAs.
  • See comments by Dutch Data Protection Authority on privacy implications
  • It is unclear what (public?) purpose is served by making cert info publically available in an organised fashion. Possibly, fraud protection by encouraging domain owners to scan for their domain?
  • There is a common expectation that certificates should be public, perhaps deriving from their name "public key".
  • In privacy regulation, some information is sometimes deemed as public in mandates: especially name and email address. What is not deemed as public is numbers and similar.
  • In contrast, there are costs in declaring this info private. "Declared as private" means that the info has to be protected, which creates costs for the CA, and costs for the users. Which may impact on privacy. Certificates by their nature encourage publication of info, so this may create an uneconomic burden for some illusory benefit.
  • CAcert considers any contents of the certificates to be published information, because of the customary and intended purpose of the certificates.
  • Domains information is not made available.
  • email sent to DR 2006.05.24.