Course contentsShow
← Security
Lesson 2995 of 3,05255. Secure CommunicationsFree lesson

Domain Fronting and CDN Circumvention

Leveraging domain fronting techniques and CDN infrastructure to disguise traffic destinations from censors.

Domain Fronting and CDN Circumvention

You'll learn how to disguise the true destination of encrypted traffic by leveraging Content Delivery Networks (CDNs) to bypass censorship.

What Is Domain Fronting?

Domain fronting exploits how CDNs and HTTPS work together. When you connect to a CDN, the initial TLS handshake uses one domain (the "front domain"), but inside the encrypted connection, your HTTP request actually asks for content from a different domain on the same CDN infrastructure.

Think of it like mailing a letter: the envelope shows an innocuous address (the front domain) that censors can see, but inside the sealed envelope, your actual message goes to a different recipient—all delivered through the same postal service (CDN).

How It Works

CDNs like Cloudflare, Amazon CloudFront, or Google's infrastructure host thousands of domains. Here's the clever part:

  1. Outer layer (visible): Your TLS connection's SNI (Server Name Indication) shows allowed-site.com
  2. Inner layer (encrypted): Your HTTP Host: header requests blocked-site.com
  3. CDN routing: The CDN reads the encrypted Host header and routes your request to the actual blocked site

Censors see only the allowed front domain in the TLS handshake. They cannot inspect the encrypted Host header without breaking TLS entirely—making widespread blocking difficult without collateral damage to legitimate sites.

The Catch

Many CDN providers have restricted or disabled domain fronting because it violates their terms of service and complicates content delivery. As of recent years, Google and Amazon explicitly block this technique. It remains a cat-and-mouse game where new CDN configurations occasionally enable similar circumvention until providers adapt.

Key Takeaway: Domain fronting uses CDN infrastructure to hide the true destination of encrypted traffic by showing censors one domain while routing to another, though provider countermeasures have reduced its effectiveness.