CyberKit

DNS Sinkhole

Also called sinkholing.

Redirecting malicious domain lookups to a controlled server.

What it is

A defensive technique that answers DNS queries for known-bad domains with an address the defender controls, so infected hosts connect to a monitoring server instead of the real C2. Researchers and registrars also sinkhole domains to disrupt active botnets.

Why it matters

A sinkhole severs the attacker's control and reveals every victim that calls home, scoping an outbreak and measuring infection counts in one step.

In practice

Pointing a malware family's hardcoded domain at a sinkhole and watching hundreds of internal hosts check in, exposing the true blast radius.

What to look for

  • Hosts resolving known bad domains to the sinkhole IP.
  • Repeated lookups from one host, a sign of infection.
  • Sinkhole hits that spike after a new block.

Common mistake

Treating a hit as the fix. A host that looks up a bad domain still needs a closer look.

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

Sources