# Install network-doctor with Homebrew

Network troubleshooting TUI. Version 2.1.1 via Homebrew; verified 2026-10-29.

## Install

```sh
sudo av install brew:network-doctor
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install network-doctor
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:network-doctor
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/network-doctor>
- **Version:** 2.1.1
- **Source summary:** Network troubleshooting TUI
- **Homepage:** <https://github.com/heymaikol/network-doctor/>
- **Repository:** <https://github.com/heymaikol/network-doctor>
- **Upstream docs:** <https://github.com/heymaikol/network-doctor/>
- **License:** Apache-2.0
- **Source archive:** <https://github.com/heymaikol/network-doctor/archive/refs/tags/v2.1.1.tar.gz>
- **Last updated:** 2026-10-29T22:09:44Z
- **Generated:** 2026-11-04T12:20:42+00:00

## Executables

- netdoc (cli)
- netdoc (alias)

## Build dependencies

- go

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux

## Freshness

- Page generated: 2026-11-04
- Package-manager version: 2.1.1
- Package-manager updated: 2026-10-29
- Local data: ok
- Upstream repository: https://github.com/heymaikol/network-doctor
- Upstream latest detected: v2.1.1 (current)
## Project history and usage

Network Doctor is a cross-platform terminal UI and automation-friendly CLI for diagnosing interface, DNS, TCP, TLS, HTTP, proxy, and path-MTU failures.

### Project history

Network Doctor was developed as a Go-based, cross-platform troubleshooting TUI. Its design focuses on locating the failing network layer and presenting evidence and suggested fixes rather than exposing only raw output from individual diagnostic commands.

### Adoption history

The project supplies binaries or packages for Linux, macOS, and Windows, including Homebrew, Winget, Scoop, Fedora COPR, and release artifacts. The same engine supports interactive diagnosis, watch mode, JSON output, and stable exit codes for automation.

### How it is used

Running `netdoc` without a target checks local connectivity, egress, proxy, public DNS, and Wi-Fi metadata. Supplying a hostname or service performs layered diagnosis; `--watch` observes intermittent faults, while `--json` produces machine-readable reports.

### Why package nerds care

Network Doctor consolidates tools commonly invoked separately—such as interface inspection, DNS lookup, TCP connection testing, TLS inspection, and HTTP probing—into a layered diagnosis. Package users gain one cross-platform binary that can explain failures interactively or emit structured reports.

### Timeline

- 2020s: Network Doctor is published as a cross-platform Go project with native package and release-binary distribution.

### Related projects

- Traditional tools such as ping, dig, and curl cover narrower portions of the troubleshooting workflow that Network Doctor combines.

### Sources

- <https://github.com/heymaikol/network-doctor#readme>
- <https://github.com/heymaikol/network-doctor/tree/main/docs>


## Security Notes

No matching local secret-handling manifest was found for network-doctor. Package metadata is still published here so future coverage has a stable package URL.


## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** network-doctor
- **Version Scheme:** 0
- **Revision:** 0
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** stable


## Related links

- [Source-control packages](https://pkg.so/source-control-tools/) - Belongs to a source-control command family.
- [Terminal utility packages](https://pkg.so/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Networking and protocol packages](https://pkg.so/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [netwatch](https://pkg.so/brew/netwatch/) - Choose NetWatch when troubleshooting requires continuous connection and process visibility, live packet capture, protocol decoding, or PCAP-based incident forensics rather than a bounded layered diagnosis.

  Sources: <https://networkdoctor.dev/docs/reference/> · <https://github.com/matthart1983/netwatch/blob/main/docs/REFERENCE.md>

## Combined YAML source

View the package source record on GitHub. [combined/network-doctor.yml](https://github.com/mxcl/pkgdb/blob/main/combined/network-doctor.yml)


## Sources

- pkg.so package database
- package-page enrichment
- curated package history
- package version freshness
- package relationship graph
- cross-ecosystem install command graph