httpstat VS Wireshark

curl is fantastic. There's also HTTPStat which provides a waterfall visualization on top of curl timings: https://github.com/reorx/httpstat

There's also Skytrace (made by yours truly), which provides timing info as a waterfall visualization inspired by HTTPStat + lots more (syntax highlighting for responses, built-in JMESPath support, command-line assertions and checks etc) - https://github.com/artilleryio/artillery/tree/main/packages/...

thank you! we just grab the timings info for the request from the underlying HTTP library, and sprinkle some ASCII art on top. That part was inspired by httpstat [1]

We want to extend those with support for Server-Timing next, and also Core Web Vitals [3] (via Playwright) for web pages.

1. https://github.com/reorx/httpstat

To begin with Wireshark, visit their official website for the download. The installation process is straightforward, but attention should be paid to the installation of command-line tools, which may require separate steps. Upon launching Wireshark, users are greeted with a selection of network interfaces as seen below. Choosing the correct interface, such as the loopback for local server debugging, is crucial for capturing relevant data.

Wireshark

If you're very curious as to what is really going on under the hood, I recommend you familiarize yourself with port mirroring for your switch platform of choice, and then use a laptop in promiscuous mode to capture traffic using Wireshark. Failing that, hire a network engineer to interview one of their sales engineers or architects, and have them explain it to you.

You should do a hands fins-on lab with Wireshark.

A great way to test the effectiveness of a pinning implementation is by simulating an MITM attack. Tools like Mitmproxy or Wireshack allow us to create a test environment to monitor, intercept, and proxy network requests for a test host.

They even have a nice comment explaining the heuristic: https://github.com/wireshark/wireshark/blob/ef9c79ae81b00a63...

     * Heuristics to detect the WireGuard protocol:

This has been put together for Wireshark, starting on line 1520 https://github.com/wireshark/wireshark/blob/master/epan/dissectors/packet-cip.c

Obviously based on the question you know the answer is a Wireshark-like software and it boils down to how you classify Wireshark. My issue is that Wikipedia refers to it as a Packet Analyzer, Varonis refers to it as a Packet Sniffer, Wireshark refers to itself as a Network Protocol Analyzer, Kali documentation refers to it as a Network Sniffer, Wireshark's README refers to itself as a Network Analyzer OR Sniffer...