Netcap v0.12: DNS timing and better hunting clues

Which DNS requests went unanswered? What remote operation was attempted? Does that host reconnect every few seconds?

Netcap v0.12 adds fields and views that help answer those questions directly.

DNS gets a timeline

DNS records now show round-trip time, retries, and whether a transaction was answered, late, unsolicited, or reordered. DNS over TCP joins the same workflow, including messages split across TCP segments.

The Domains view summarizes those timings and outcomes, so a troublesome resolver or repeatedly retried domain is easier to pick out.

More context for a hunt

DCE/RPC records include operation names and fault status. You can inspect the remote call that was made and whether it failed.

The new c2.beacon detection highlights connections that recur at regular intervals and shows the measured timing and jitter. Scheduled updates and monitoring can look periodic too, so those measurements are there to help you decide what deserves a closer look.

Connections also gain a producer–consumer ratio: a quick indication of whether a host mostly sent or received data.

Full release notes