> When I write in browser twitter.com/give-me-lots-of-pr0n does it first connect with twitter.com's port 80 and sends an unencrypted GET request with /give-me-l

> When I write in browser twitter.com/give-me-lots-of-pr0n does it first connect with twitter.com's port 80 and sends an unencrypted GET request with /give-me-lots-of-pr0n to receive redirect to https://twitter.com/ https://twitter.com/? Probably not, in this case, because Twitter has implemented HSTS[1], and are[2] in a list that comes with your browser that specifies never to connect to the site unencrypted. If they're in the browser list, your browser will never actually connect on port 80; it will silently redirect client-side to HTTPS. 1. https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security 2. https://hstspreload.appspot.com/?domain=twitter.com https://hstspreload.appspot.com/?domain=twitter.com