← All articles
VPNSergey KarpovMay 15, 20268 min read

VLESS Reality Explained: The Most Censorship-Resistant VPN Protocol

A technical deep-dive into VLESS with XTLS Reality — why it's invisible to DPI systems that block conventional VPNs.

The arms race between VPNs and censorship

Every time a VPN protocol becomes popular, censors study its traffic patterns and add it to their blocklist. OpenVPN was blocked in China within months of widespread adoption. WireGuard, despite its elegance, has a recognizable handshake that DPI systems catch immediately in heavily restricted networks.

The industry response has been a series of obfuscation layers — making VPN traffic look like something else. Shadowsocks made it look like HTTPS. V2Ray added more sophistication. VLESS Reality takes a different approach entirely.

What makes Reality different

Reality doesn't just imitate HTTPS — it actually uses real HTTPS infrastructure as its cover. Here's how:

Standard TLS-based VPN:

  1. Client connects to server: "I'm starting a VPN session"
  2. Server responds with its own VPN certificate
  3. DPI inspection sees a VPN certificate and blocks it

VLESS Reality:

  1. Client connects to server: "I'm connecting to apple.com"
  2. Server presents apple.com's actual TLS certificate via domain fronting
  3. DPI inspection sees a legitimate HTTPS connection to Apple
  4. Traffic passes through — the actual payload is encrypted separately

This is the core insight: Reality leverages SNI (Server Name Indication) to present a legitimate domain's certificate to inspection systems, while the actual VPN tunnel runs underneath.

The XTLS component

XTLS (Xtreme TLS) is the transport layer that makes this efficient. Standard VPN protocols encrypt traffic twice — once with TLS (for the transport) and once with the VPN's own encryption. XTLS recognizes when traffic is already encrypted (like HTTPS websites you visit) and passes it through without double-encrypting, cutting overhead dramatically.

Result: speeds close to your raw connection speed, especially for HTTPS traffic (which is most of what people actually use).

Why DPI can't block it without collateral damage

The fundamental problem for censors: to block VLESS Reality, they'd have to block legitimate traffic to the domains being used as covers (Apple, Microsoft, Amazon). That would take down services their own government and population depends on.

This is why VLESS Reality has remained stable in China, UAE, and other censored networks even as they've aggressively blocked other protocols.

Protocol comparison

ProtocolObfuscation methodDPI-resistantSpeed overhead
PPTPNoneNoNone
OpenVPNNoneNoMedium
WireGuardNoneNo (blocked in restricted networks)Very low
ShadowsocksAEAD cipher disguisePartialVery low
VLESS + RealityReal TLS/domain frontingYesMinimal

Using VLESS Reality with IMBA

IMBA runs VLESS Reality as its primary protocol on all servers. When you install Happ and add your subscription link, Reality is configured automatically. The only manual step: disable Mux in server settings (Mux interferes with Reality's TLS handling).

[Set up IMBA VPN](/auth/register)

Try IMBA free

eSIM + VPN + virtual card in one subscription

Get started