Server Name Indication is a TLS extension where the browser tells the server which hostname it's trying to reach, before the encrypted connection is even established. This sounds minor, but it solved a real architectural problem: without it, a server hosting multiple HTTPS sites on one IP address couldn't know which certificate to present until after the encryption handshake had already started.
Why this used to be a real limitation
Before SNI was widely supported, hosting multiple HTTPS sites required a dedicated IP address per site, because the server had to pick a certificate before knowing which domain the visitor wanted. That made shared and budget hosting with HTTPS expensive and awkward at scale.
Why it matters today
SNI is now supported by effectively all modern browsers and servers, which is what makes cheap or free shared HTTPS hosting for thousands of unrelated small domains on one IP economically possible. The rare exception is very old clients (some legacy embedded devices, ancient Android/Windows XP-era browsers) that don't support SNI — a genuinely small and shrinking population today.
What browsing looked like before SNI was widely supported
Before SNI, hosting multiple HTTPS sites on shared infrastructure required a dedicated IP address per site, since the server had to select a certificate before knowing which domain the visitor wanted — this made HTTPS on budget shared hosting expensive and impractical at scale, a real barrier SNI's near-universal support has since removed.
The rare cases where SNI still causes issues today
A small, shrinking population of very old clients, some embedded devices, ancient versions of Android or Windows XP-era software, don't support SNI at all and will receive whatever certificate is configured as a server's default rather than the one for their intended hostname — a genuinely rare edge case today, but worth knowing about if you're troubleshooting an unusual, isolated certificate mismatch report.
What a packet capture actually reveals during the SNI exchange
Because SNI is sent before encryption is established, the requested hostname is technically visible in plaintext to anyone capturing network traffic at that exact moment — TLS 1.3's Encrypted Client Hello extension, where supported by both client and server, closes this specific remaining gap by encrypting the SNI field too.
Why SNI support became essentially universal so quickly
Once major browsers and server software adopted SNI, the cost savings for hosting providers, no longer needing a dedicated IP per HTTPS site, were substantial enough that adoption spread rapidly across the industry within a few years, making the remaining population of non-SNI-capable clients shrink to a genuinely small edge case relatively fast.
What a server without SNI support would need to do instead
A server unable to use SNI must dedicate a separate IP address to each HTTPS site it hosts, selecting which certificate to present based on which IP address received the connection rather than which hostname was requested — a workable but considerably less flexible and more resource-intensive approach than SNI-based hosting.
Why this small extension quietly reshaped affordable hosting
SNI's near-universal adoption is a big part of why HTTPS became affordable and practical for the huge population of small sites on shared, budget hosting — without it, the dedicated-IP requirement alone would have kept HTTPS considerably more expensive and technically inconvenient for far longer than it actually was.
What a network administrator specifically gains from understanding SNI deeply
Understanding SNI at a technical level helps explain certain network behaviors that would otherwise seem confusing — like why a single IP address can serve entirely different, unrelated websites depending on which hostname a specific request requests, a detail relevant to network troubleshooting and infrastructure planning alike.
A closing thought
A quick closing thought: SNI is one of those quietly essential internet technologies that most people never think about, yet without it the modern, affordable shared-hosting HTTPS landscape most small sites rely on simply wouldn't exist in its current, accessible form.