Check a capture in your browser
The free PCAP Toolkit gives DNS, TCP and HTTP ratings, top talkers and a sanitized copy of one capture, worked out in your browser. Nothing is uploaded.
Open the toolkit →Practical, tool-agnostic ways to answer common network questions from PCAP and PCAPNG files, with commands you can copy and the evidence you should look for.
Written and maintained by Stuart Mathieson · Updated 12 October 2026
The free PCAP Toolkit gives DNS, TCP and HTTP ratings, top talkers and a sanitized copy of one capture, worked out in your browser. Nothing is uploaded.
Open the toolkit →See where Wireshark is clearly stronger, where a self-hosted report helps, and why the most effective workflow often uses both.
Read the comparison →Validate capture quality, establish scope, rank traffic and turn broad symptoms into testable packet-level questions.
Read the guide →Separate real retransmissions from capture artefacts, identify the affected flow, and reason about loss, congestion and delay.
Read the guide →Pair queries with responses, measure response time, find slow names and distinguish DNS delay from application delay.
Read the guide →Find RST packets, identify which endpoint sent them, and use sequence and timing context to explain why.
Read the guide →Use command-line summaries, split targeted subsets, or process the capture in a self-hosted web interface.
Read the guide →Find clear-text requests and responses, isolate streams, export useful fields, and understand the limits imposed by HTTPS.
Read the guide →Choose a capture format based on interfaces, metadata, timestamp resolution and tool compatibility.
Read the guide →Use TCP sequence analysis, duplicate acknowledgements and retransmissions without confusing missing capture data for network loss.
Read the guide →Review visible handshakes, names, versions, cipher suites and certificates without overstating what encrypted traffic reveals.
Read the guide →Measure the intervals between connections and lookups, validate regular pairs in Wireshark, and rule out legitimate pollers.
Read the guide →Reduce a capture, strip payloads, remap addresses and check the result for leftover names before it leaves your network.
Read the guide →Recognise client software by how it starts TLS, why JA4 stays stable when JA3 doesn’t, and how to extract and group both.
Read the guide →Match addresses, domains, file hashes and TLS fingerprints with tshark, then judge what each hit really means.
Read the guide →Recover downloads and uploads with Export Objects or tshark, hash them, check they’re complete and handle them safely.
Read the guide →Audit what your network leaks: passwords in clear-text protocols, SNMP communities, SMB1, NTLMv1 and weak Kerberos tickets.
Read the guide →Find data hidden in DNS lookups by name length, randomness, unique subdomains per domain and unusual record types.
Read the guide →Find addresses claimed by more than one MAC and unsolicited replies, and rule out failover and virtualisation.
Read the guide →Identify devices passively from MAC vendors, DHCP fingerprints, name announcements, banners and user agents.
Read the guide →Decrypt QUIC Initial packets to see server names, ALPN and JA4 fingerprints, and know what stays hidden.
Read the guide →Structure a report people can act on: executive summary, timeline, checkable findings and evidence slices.
Read the guide →Rank endpoints and conversations by packets, bytes and direction, then account for duration and capture-point bias.
Read the guide →Collect a fair pair, normalise unequal durations and validate meaningful protocol, endpoint and application deltas.
Read the guide →Configure a Docker bind mount, use a safe file handoff, and manage the storage and capacity implications of auto-ingest.
Read the guide →