CyberKit

DNS over HTTPS

Also called DoH, DNS over TLS, DoT.

Encrypting DNS queries inside HTTPS or TLS to hide them.

What it is

Protocols that wrap DNS resolution in an encrypted channel (HTTPS for DoH, TLS for DoT), so queries are no longer visible to on-path observers. They were designed for privacy but also conceal name resolution from defenders.

Why it matters

Encrypted DNS blinds traditional query logging and can be abused to reach malicious domains or smuggle data past inspection, forcing teams to control which resolvers endpoints are allowed to use.

In practice

Finding malware configured to resolve its C2 through a public DoH provider, bypassing the organization's DNS monitoring entirely.

What to look for

  • Browsers or malware talking to public DoH resolvers.
  • DNS queries missing from your resolver logs.
  • HTTPS to known resolver IPs from servers.

Common mistake

Ignoring it. Encrypted DNS blinds your DNS logs; route it through a resolver you control.

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