Which entity is responsible for linking a public key to a site's identity?

Which entity is responsible for linking a public key to a site's identity?

• A. Web hosting company
• B. Certificate Authority
• C. End-user device
• D. Internet Service Provider

Answer: (B)

The binding of a site's public key to its identity is done by a Certificate Authority. In TLS/SSL, a site gets a certificate that includes its domain name and its public key, and this certificate is issued and signed by a trusted CA after the CA verifies the site's ownership of the domain and other details. When you connect, the browser checks that the certificate is valid, trusted, and matches the site you’re visiting, and then uses the included public key to establish a secure connection. The web hosting company provides the server, but doesn’t verify or certify the site’s identity. The end-user device and the ISP don’t perform the identity binding either; they just use the certificate and connect to the network.

The binding of a site's public key to its identity is done by a Certificate Authority. In TLS/SSL, a site gets a certificate that includes its domain name and its public key, and this certificate is issued and signed by a trusted CA after the CA verifies the site's ownership of the domain and other details. When you connect, the browser checks that the certificate is valid, trusted, and matches the site you’re visiting, and then uses the included public key to establish a secure connection. The web hosting company provides the server, but doesn’t verify or certify the site’s identity. The end-user device and the ISP don’t perform the identity binding either; they just use the certificate and connect to the network.