Port Scanner (Local)

During development and testing, you often need to know which ports on your local machine or internal network are accepting connections. Port scanners typically run as command-line tools, requiring network configuration knowledge. This browser-based scanner offers a lightweight alternative: probe common ports directly from your browser to discover which services are running locally without needing specialized tools.

Browser-based probing

Unlike traditional port scanners (like nmap) that operate at the network layer, this tool uses HTTP requests from the browser. It attempts to connect to specified ports and checks whether they respond within a timeout period. This approach respects browser security policies and works within the web environment.

Development server discovery

When you're running multiple local development servers—a web app on port 3000, a database UI on 5432, an API server on 8000—it's easy to forget what's running where. Use this tool to quickly scan a range of common ports and discover active services. Port 3000 (common for development), 5432 (PostgreSQL), 6379 (Redis), 8080 (web servers), 9090 (monitoring), and others will show as open or closed.

Network awareness

The tool works on localhost (127.0.0.1) by default but can probe other hosts on your local network (192.168.x.x, 10.x.x.x). This is useful for discovering services on other machines within your home or office network.

Browser limitations

Browser-based scanning respects cross-origin policies and security restrictions. It won't detect services on completely different networks and may be blocked by firewalls or CORS policies. For comprehensive network scanning, command-line tools remain more powerful. Use this tool for quick local checks during development.

Common ports to check

Common development ports: 3000, 3001, 5000, 5432, 6379, 8000, 8080, 8443, 9000, 9090. Enter them as a comma-separated list, and the tool quickly probes each one.