CyberKit

Domain Fronting

Hiding the true destination behind a trusted shared front domain.

What it is

A technique that puts a benign, high-reputation hostname in the visible TLS SNI or HTTPS request while the actual destination is set in the encrypted Host header. Shared hosting and content delivery infrastructure make the two resolve to the same front, masking the real endpoint.

Why it matters

It lets command-and-control blend in with legitimate cloud or CDN traffic, defeating SNI- and domain-based blocking and complicating attribution of where data is really flowing.

In practice

Tracing an implant that appeared to talk to a well-known CDN domain, only to find its inner Host header pointed at the attacker's hidden service.

What to look for

  • SNI for one domain with a Host header for another.
  • Traffic to CDNs from processes that never use them.
  • TLS sessions where inspection shows the mismatch.

Common mistake

Assuming it still works everywhere. Many CDNs now block it, but similar tricks remain.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

  • SNI Inspection: Reading the destination hostname from the TLS handshake.
  • Redirector: An intermediary host that relays C2 traffic to hide the real server.
  • SOCKS Proxy Pivot: Tunneling through a foothold to reach an internal network.

Sources