Abstract: Embodiments presented herein provide a validation service used to validate a certificate chain for both public facing servers as well as internal, non-public facing servers. To validate a certificate chain, the client generates a request with the network address and sends it to the validation service. In response, the validation service attempts to establish a connection with the server at the network address. If successful, the validation service receives a certificate chain from the server and can verify that the certificate chain is complete, valid, and chains to a trusted root. If the validation service cannot connect to the network address identified in the request, then the validation service sends a local validation component to the requesting client. The local validation component executes from the client and validates the certificate chain presented by the network server.

Abstract: Embodiments presented herein provide a validation service used to validate a certificate chain for both public facing servers as well as internal, non-public facing servers. To validate a certificate chain, the client generates a request with the network address and sends it to the validation service. In response, the validation service attempts to establish a connection with the server at the network address. If successful, the validation service receives a certificate chain from the server and can verify that the certificate chain is complete, valid, and chains to a trusted root. If the validation service cannot connect to the network address identified in the request, then the validation service sends a local validation component to the requesting client. The local validation component executes from the client and validates the certificate chain presented by the network server.

Abstract: A method for creating customer-specific tools for generating certificate signing requests may include (1) identifying a request from a customer for a tool for generating a certificate signing request for a digital certificate, (2) creating, in response to the request, a customer-specific version of the tool that is unique to the customer by injecting information into the customer-specific version of the tool that (a) uniquely identifies the customer and (b) identifies a desired encryption algorithm for the digital certificate and/or a desired certificate authority for the digital certificate, (3) configuring the customer-specific version of the tool to generate the certificate signing request using the injected information, and (4) providing the customer-specific version of the tool to the customer to enable the customer to generate, using the customer-specific version of the tool, the certificate signing request without having to manually provide the injected information.