Computer networks · 1 min
What does a TLS certificate actually prove?
Learn what a TLS certificate verifies during the handshake and how asymmetric and symmetric encryption secure connection data.
Practise Computer networksMore videos
The quiz
During a TLS handshake, what does the server's certificate prove to the browser?
- That the server really owns the domain, vouched for by a certificate authority the browser trusts
- That the website is free of malware
- That the connection is faster than plain HTTP
- That the browser is the one the server expected
Show the answer
A. That the server really owns the domain, vouched for by a certificate authority the browser trusts
Transcript
Freshers get rejected here: claiming a TLS certificate proves a website lacks malware.
During the handshake, the server sends its certificate, proves it owns the matching private key, and both sides agree on a shared session key.
Now the part most people miss: the certificate binds the domain name to a public key, signed by a trusted authority, needing private key proof.
Asymmetric operations are slow, so TLS uses them during handshake to agree on keys, but switches to fast symmetric encryption for bulk page data.
Never claim certificates check malware or browser identity; they strictly prove that the server really owns the domain, vouched by an authority you trust.
Look at the placement question on your screen right now, pause the video, and tap your chosen answer before the timer runs out.
Option A is correct because the certificate validates domain ownership through a trusted authority, while B is wrong since certificates ignore malware completely.
Save this comparison summary table before your next technical interview, and practice core computer networks questions for free on InternDoor today.