Which protocol represents a secure version of HTTP using SSL/TLS?

• A. Hash Function
• B. CTR Mode
• C. OFB Mode
• D. HTTPS

Answer: (D)

HTTPS is the secure version of HTTP because it adds TLS/SSL between the web client and server, creating an encrypted channel for all HTTP data. This means requests and responses are scrambled in transit, so eavesdroppers can’t read them. TLS also authenticates the server with a certificate, which helps prevent impersonation, and it protects message integrity so tampering is detectable. The handshake process negotiates which encryption methods to use and establishes session keys; using ephemeral keys can provide forward secrecy, so past communications stay private even if the server’s key is later compromised. In short, HTTP over TLS/SSL secures confidentiality, integrity, and authenticity for web traffic.

The other options aren’t secure web protocols by themselves: a hash function ensures data integrity but does not encrypt data; encryption modes like CTR or OFB are ways to apply a cipher to data, not complete protocols for securing an entire communication session.