{"id":1083,"date":"2017-03-21T07:30:00","date_gmt":"2017-03-21T07:30:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2017\/03\/21\/what-is-sni-server-name-indication\/"},"modified":"2021-07-24T15:06:15","modified_gmt":"2021-07-24T15:06:15","slug":"what-is-sni-server-name-indication","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Security\/Concepts-and-Terminology-Security\/what-is-sni-server-name-indication.html","title":{"rendered":"What is SNI (Server Name Indication)?"},"content":{"rendered":"
SNI (Server Name Indication) is an extension to the TLS protocol, that provides the ability to host multiple HTTPS-enabled sites on a single IP.<\/p>\n
Prior to SNI the client (i.e browser) would send the requested hostname to the webserver within the HTTPS payload (Figure 1). Due to the hostheader being encrypted the SSL handshake and certificate retrieval had to be completed before it could be read. As a a result, websites hosted on the same IP address were forced to use the same SSL certificate, or they needed to each have their own IP address.<\/p>\n