Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

SNI Proxy

github.com

  • Free plan
  • macOS
  • Linux
  • Self-hosted
7.2 Club score Visit github.com

What SNI Proxy is

SNI Proxy is free, self-hosted software that routes incoming HTTP and TLS connections according to the hostname in a TCP session’s initial request. It can provide name-based HTTPS proxying without decrypting traffic, so the proxy machine needs no keys or certificates. Routing rules can match exact hostnames or regular expressions, with a fallback server for requests lacking a hostname. One instance can use multiple listening sockets. Listeners and backend servers support IPv4, IPv6, and Unix domain sockets, while HAProxy proxy protocol support passes the original source address to backend servers. The software supports TLS and HTTP, but not HTTP/2 hostname multiplexing or HTTP/3 over QUIC. Hostname and wildcard entries require a build with UDNS. The maintainer recommends a local caching DNS resolver with UDNS because queries from its single UDP socket can be relatively easy to spoof. The project is deprecated and uses file-based configuration under the BSD-2-Clause license.

Who it suits

SNI Proxy suits operators running their own Linux or macOS proxy infrastructure. It is relevant when hostname routing without TLS termination is required and the protocol limitations are acceptable.

Good to know, and what to watch

  • Routes HTTPS without decryption
  • Exact and regular-expression host rules
  • IPv4, IPv6, and Unix sockets
  • HAProxy source-address forwarding
  • BSD-2-Clause licensed
  • Project is deprecated
  • No HTTP/2 hostname multiplexing
  • No HTTP/3 over QUIC
  • UDNS required for hostname entries

SNI Proxy

Free

Free plan

The verdict

SNI Proxy offers focused, file-configured hostname routing for self-hosted HTTP and TLS deployments. Its deprecation and missing newer protocol support should be considered before adoption.

What the maker publishes

Configuration
Host routing tables can match exact hostnames or regular expressions, and can use a fallback server when the initial request has no hostname. source
DNS requirement
Hostname and wildcard configuration entries require a build with UDNS; those features are unavailable without it. source
DNS security note
The README recommends a local caching DNS resolver with UDNS because its single UDP socket makes queries relatively easy to spoof. source
HTTPS routing
It supports name-based HTTPS proxying without decrypting traffic and requires no keys or certificates on the proxy machine. source
License
The repository identifies its license as BSD-2-Clause. source
Listeners
A single instance can use multiple listening sockets. source
Network support
It supports IPv4, IPv6, and Unix domain sockets for backend servers and listeners. source
Platforms
The README documents Debian or Ubuntu and Fedora or Red Hat packaging, plus best-effort macOS builds; macOS is not a primary target platform. source
Project status
The maintainer marked the project deprecated on 2023-12-13, citing newer alternatives and limitations with HTTP/2 and HTTP/3. source
Protocols
It supports TLS and HTTP, but the maintainer says it does not support HTTP/2 hostname multiplexing or HTTP/3 over QUIC. source
Proxy protocol
It supports the HAProxy proxy protocol to pass the original source address to backend servers. source
Purpose
SNI Proxy routes incoming HTTP and TLS connections using the hostname in the initial request of a TCP session. source
Support
The maintainer says they will monitor issues and email requests, but users should not expect a response unless the issue is a significant security or reliability problem. source

Checked against the maker's pages on 9 Oct 2026.