Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-domain-fronting-and-cdn-abuseDFIR and threat hunting

hunting-domain-fronting-and-cdn-abuse

⁨Hunts for domain fronting and CDN abuse by detecting TLS SNI versus HTTP Host header⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-domain-fronting-and-cdn-abuse

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
7N7SfO5AJi…TvnB7WBw==The CLI checks the SHA-256 and the signature before it writes a file.
Package3e014a60…d418f180
3e014a601ca1…db6bd418f1804 files · ⁦2.9 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-domain-fronting-and-cdn-abuse@da7600a

When to Use

  • You have TLS/HTTP telemetry (Zeek ssl.log + http.log, proxy logs) and want to detect domain fronting, where the TLS SNI shows a benign CDN domain but the inner HTTP Host differs.
  • You are hunting C2 hidden behind high-reputation CDNs.

Do not use SNI/Host mismatch as definitive — some legitimate setups differ. Corroborate with destination behavior and reputation.

Prerequisites

  • Telemetry pairing TLS SNI with the inner HTTP Host (or proxy logs exposing both).

Workflow

Step 1: Detect SNI/Host mismatch

bash
python scripts/analyst.py hunt flows.csv

Flags connections where the TLS SNI and HTTP Host headers resolve to different registered domains, especially when the SNI is a known CDN/fronting-capable domain.

Step 2: Surface CDN-hosted anomalies

Highlight high-reputation CDN SNIs carrying long-lived or beaconing flows.

Step 3: Confirm

Corroborate with beacon periodicity, JA3, and destination reputation; many CDN mismatches are benign.

Step 4: Operationalize

Write a detection for SNI/Host registered-domain mismatch on fronting-capable CDNs.

Validation

  • Mismatch is computed on the registered domain, not the full hostname.
  • Known CDN SNIs are recognized to prioritize fronting-capable cases.
  • Findings are presented with corroboration needs, not as proof.

Pitfalls

  • Legitimate multi-tenant CDN/edge configs producing benign mismatches.
  • Encrypted SNI (ECH) hiding the SNI entirely — different hunt required.
  • Treating any CDN traffic as suspicious (high false-positive rate).

References

  • See references/api-reference.md for the hunter.
  • ATT&CK T1090.004 and the TLS SNI RFC (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a3e014a60Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login