One Windows VPS can comfortably host dozens of websites. IIS was designed for exactly this: a single server splits traffic across multiple sites, each with its own content folder, application pool, and \u2014 optionally \u2014 its own SSL certificate. The mechanism that makes it work is the binding, the combination of protocol, IP address, port, and host name that tells IIS which site should answer which request. This guide shows how to add a second, third, and tenth site to one VPS using IIS Manager and PowerShell, including HTTPS with SNI.<\/p>\n
Before you start stacking sites, check your resources. Each site adds memory for its application pool and bandwidth for its traffic; a 1 GB VPS is fine for two or three small sites, while a busier portfolio wants 4 GB or more. Our comparison table of Windows VPS providers<\/a> shows RAM, vCPU, and monthly bandwidth per plan, which makes sizing easier.<\/p>\n Every IIS site has at least one binding in the form IP:Port:HostHeader. When a request arrives, IIS walks all bindings and matches the Host header of the request against the HostHeader part. Two sites can therefore share port 80 on the same IP as long as their host names differ, for example site1.example.com and site2.example.com. If no binding matches, the request falls to the default site (usually the first one created), which is why you should keep a placeholder default site.<\/p>\n Repeat for each site. That is the entire process for plain HTTP.<\/p>\n To see exactly which host names are bound where:<\/p>\n With a single public IP, port 443 is shared, so each HTTPS site needs its own certificate and a way to be told apart. That is what SNI (Server Name Indication) does: the client announces the host name during the TLS handshake, and IIS picks the right certificate. SNI works on IIS 8 and later, so every modern Windows Server VPS supports it. Create the HTTPS binding with sslFlags set to 1 (SNI enabled):<\/p>\n Then assign the certificate. The easy way is IIS Manager \u2192 site2 \u2192 Bindings \u2192 https binding \u2192 Edit \u2192 Select\u2026 and choose the certificate for site2.example.com. The PowerShell way is:<\/p>\n Alternative: one wildcard certificate (*.example.com) covers every subdomain with a single SNI binding. For sites on unrelated domains, buy one certificate per domain \u2014 Let\u2019s Encrypt works fine on IIS via the win-acme tool.<\/p>\n Separate application pools are what stop one misbehaving site from taking down the others. A crashed worker process (w3wp.exe) recycles only its own pool:<\/p>\n Set a CPU limit per pool so one noisy site cannot starve its neighbors, and recycle pools periodically to keep memory in check:<\/p>\n Each host name must resolve to your VPS IP. Add A records at your DNS provider, or on the server itself with Add-DnsServerResourceRecordA if it hosts DNS. To test before DNS propagates, edit the hosts file on a test machine, or test locally from the server:<\/p>\n Hosting several sites on one IIS instance is the fastest way to make a single Windows VPS pay for itself: one license, one firewall rule set, one server to patch. For a plan with enough RAM and bandwidth for the whole portfolio, see the full specs and pricing<\/a> in our Windows VPS comparison.<\/p>\nHow bindings and host headers work<\/h2>\n
Add a site with IIS Manager<\/h2>\n
Add a site with PowerShell<\/h2>\n
New-Website -Name \"site2\" -PhysicalPath \"D:\\sites\\site2\" `\n -Port 80 -HostHeader \"site2.example.com\" -Force\nGet-Website | Select-Object Name, State, @{n=\"Bindings\";e={$_.bindings.Collection.bindingInformation}}<\/code><\/pre>\nGet-WebBinding -Name site2 | Select-Object protocol, bindingInformation, sslFlags<\/code><\/pre>\nHTTPS for many sites on one IP: SNI<\/h2>\n
New-WebBinding -Name site2 -Protocol https -Port 443 `\n -IPAddress \"*\" -HostHeader \"site2.example.com\" -SslFlags 1<\/code><\/pre>\n$cert = Get-ChildItem Cert:\\LocalMachine\\My | Where-Object Subject -like \"*site2.example.com*\"\n$site = Get-IISSiteBinding -Name site2 -Protocol https\n$site.CertificateHash = $cert.Thumbprint\n$site.CertificateStoreName = \"My\"\n$site | Set-IISSiteBinding<\/code><\/pre>\nIsolate each site in its own app pool<\/h2>\n
New-WebAppPool -Name \"site2_pool\"\nSet-ItemProperty -Path \"IIS:\\AppPools\\site2_pool\" -Name managedRuntimeVersion -Value \"v4.0\"\nSet-ItemProperty -Path \"IIS:\\Sites\\site2\" -Name applicationPool -Value \"site2_pool\"\nStart-WebAppPool -Name site2_pool<\/code><\/pre>\nSet-ItemProperty -Path \"IIS:\\AppPools\\site2_pool\" -Name cpu.limit -Value 50000 # 50%\nSet-ItemProperty -Path \"IIS:\\AppPools\\site2_pool\" -Name recycling.periodicRestart.requests -Value 5000<\/code><\/pre>\nPoint DNS at the VPS and test<\/h2>\n
curl -H \"Host: site2.example.com\" http:\/\/127.0.0.1\/\ncurl -k -H \"Host: site2.example.com\" https:\/\/127.0.0.1\/<\/code><\/pre>\nCommon mistakes<\/h2>\n
Wrap up<\/h2>\n