InternetTest: a Windows connectivity toolkit with a command line companion

One window for the commands you already know

InternetTest is described as a modern connection utility for Windows that can locate IP addresses, send ping requests, recover your WiFi passwords and more. The project's own framing for the paid tier is InternetTest Pro, your Windows connection toolkit: monitor, diagnose and optimize internet connectivity with ease, with actionable insights from network diagnostics through to WiFi password recovery.

The feature set is a list of things that already exist as Windows command line tools, gathered into one interface with the results laid out rather than printed.

Website availability check verifies in real time whether a specific website is up or down, which helps separate a network problem from a site problem. DNS tools retrieve DNS information for a domain, similar to the dig command, and also expose WHOIS registration details, plus the ability to view the local DNS cache and flush it when needed. IP configuration details give a comprehensive overview of the device's network settings, similar to the ipconfig command in Windows. Ping measures latency and responsiveness for IPs or URLs so you can spot a bottleneck.

The pattern is consistent: for each command line tool there is a page, and the value is in the presentation rather than in any capability the operating system lacked. That is a legitimate product, and it is also a clear statement about what this tool is.

The language is C#, the licence is MIT, the default branch is main, and the last push to the repository was on 2026-10-14.

The CLI is a separate project, not a flag

The newest item announced in the project page is a command line interface, and the way it is described matters for anyone deciding what to install.

Introducing InternetTest CLI, the announcement says, a command line interface that provides the same features of InternetTest Pro. It links to a separate repository, Leo-Corporation/InternetTestCLI, rather than to a subdirectory of this one.

So there are two artefacts with two release histories. The desktop application here is the one with the releases, the store page and the bug report templates. The CLI is developed alongside it, in its own repository, and its own versioning will not necessarily track the desktop app's.

For a user this is mostly good news, because a terminal version of a connectivity toolkit is the version that composes. A ping loop, a traceroute piped into a parser, a scripted availability check across a list of hosts: those are things you can only do with the command line version. The desktop application remains the better choice when a person wants to look at a traceroute hop by hop and understand what the picture means.

For a team, the practical note is that you now maintain two dependencies rather than one, and the documentation for each lives with its own project.

Traceroute that reports latency and loss per hop

The traceroute feature gets the most detailed treatment in the documentation, and the detail is about interpretation rather than mechanics.

It enables you to trace the path your data takes through the network from your device to a target IP address or URL, which helps you understand network routing and identify potential points of congestion or delays. Four capabilities are listed.

Trace network hops gives a detailed list of the intermediate routers or hops that your data traverses on its way to the destination. View IP addresses shows, for each hop, the corresponding IP address, allowing you to analyse the routing path and identify any unexpected detours. Evaluate latency measures the round-trip time for each hop, which helps locate bottlenecks or areas of congestion. Identify network issues detects problems such as packet loss or excessively long latency at specific hops.

The first and last of those are the ones that separate this from a raw tracert. A hop that is slow because it is far away is not the same as a hop that is slow because it is congested, and the per-hop round-trip number is what lets you tell them apart. The mention of packet loss per hop is the other useful signal, because a route that loses packets at one intermediate router produces exactly the kind of symptom that looks like a problem with the destination.

The feature also serves the geolocation page's stated purpose: knowing where a server sits physically helps explain latency, and detecting an unexpected IP in an unexpected place is a security signal the project calls out explicitly.

WiFi password recovery is the feature with a policy attached

The WiFi Utilities section describes a comprehensive set of tools for managing and optimising wireless network connections, covering whether you are seeking information about nearby networks or fine-tuning your network. The excerpt of the documentation stops mid-sentence there, so the specific sub-features are not spelled out in what the project publishes here.

What the rest of the page does say is enough to place the feature. The repository's topic list includes wifi-password-viewer, and the description in the header and the tagline both name recovering WiFi passwords as a headline capability. A separate CLI project exists to give the same features on the command line.

This is the part of the tool where a reader should think about environment rather than engineering. Stored WiFi credentials on Windows are readable by the logged-in user for networks that machine has joined, and an application that surfaces them is convenient for a person who has forgotten their own network password and a problem for an organisation that treats those credentials as sensitive.

The other WiFi utility the description does mention is discovering nearby networks, which is the ordinary scan any device performs, and that carries none of the same concern.

For an individual troubleshooting their own machine, the feature is a time saver. For a managed fleet, it is the reason the application would need to be excluded by policy, and the CLI version even more so because it can be scripted.

Four generations of the application in one repository

The repository layout is unusual and worth reading before you judge the project's shape.

The top level contains four directories named after versions of the application: InternetTest 4, InternetTest 5-6, InternetTest 7, and InternetTest, which is the current one. Alongside them are InternetTest.Setup, the installer project, BuildPortable.bat for a portable build, a ROADMAP.md, CONTRIBUTING.md, a CODE_OF_CONDUCT.md, a .licenserc.json configuration and both a LICENSE and a SETUP_LICENSE file.

The naming suggests the application has been through a rewrite cycle and the older generations were kept in the tree rather than deleted, which is common when a rewrite means the previous code still holds a feature the new one has not absorbed yet.

For a reader, the practical consequence is that the tree tells you the project is mid-migration. The current code is the InternetTest directory, the packaging concerns live in InternetTest.Setup, and the older directories are history.

For a contributor, the split between LICENSE and SETUP_LICENSE is a detail with a real question behind it. Installer components often carry different terms from the application itself, and the project has chosen to publish them separately. Which terms cover which part of what you install is something the README excerpt does not resolve, and it is worth asking before redistributing an installer in an organisation with a licence review step.

Getting it, and what the release history tells you

The project page points to a download link, and the homepage recorded for the repository is the store page at leocorporation.dev/store/internettest. There are also issue templates in the repository for bug reports and feature requests, both with labels assigned in their template URLs, which is a small sign of a maintained triage process.

The release history shows the versioning scheme rather than a steady stream. The recent tags are 9.1.0.2602, with a release candidate 9.1.0.2602-rc1 and a pre-release 9.1.0.2602-pre1, all published within a couple of days of each other in February 2026. The trailing number looks like a build identifier rather than a semantic version, so the last two digits appear to identify the build within a year, which would make 2602 the second numbered build of 2026.

That scheme has a consequence for upgrade planning. There is no minor version history to scan for breaking changes in the conventional sense, and the jump from 9.0 to 9.1 is not something the tags explain on their own. The CHANGELOG for the application and the release notes are where that information has to come from.

The last push was on 2026-10-14, well after the February release, so the released build is behind the working tree by roughly eight months. For a utility that talks to the network and to the operating system's credential store, running the released build rather than the tip of the tree is the sensible default.

The documentation is also split between the project page and the store listing, and the page you are reading is the truncated version: the WiFi utilities section is cut off mid-sentence in what the repository publishes, which is a small hint that the store page carries more.

Editorial conclusion

InternetTest suits a Windows user who wants the network diagnostic commands in a single window with the outputs explained, and who wants the same tools in a terminal for scripting. It is the wrong choice if you are on macOS or Linux, since the project is Windows only, and it is the wrong choice for an environment where recovering stored WiFi credentials is a policy problem rather than a convenience. Verify three things before you rely on it: that the feature you want is documented in the build you download rather than in the newer CLI, since the two are separate projects, that the WiFi password feature is acceptable under your organisation's policy, and that the version you install matches the Windows build your machine runs.

Frequently asked questions

Official sources

1. Leo-Corporation/InternetTest on GitHub
2. License: MIT
3. Project website
4. README
5. Releases