🔍 Port Scanner - Scan Open Ports & Services

🖧
The selected healthy worker peer will originate this network request.

🎯 Target Configuration

Enter hostname or IP address to scan

Comma-separated ports, ranges (80-90), or presets below

Quick Presets:

▶️ Scan Controls

Progress {{ scanProgress.current }} / {{ scanProgress.total }}
{{ scanStatus }}

⚠️ Legal Notice

Only scan systems you own or have explicit permission to test. Unauthorized port scanning may be illegal and can be detected.

⚠️

Scan Failed

📊 Scan Summary

Target:

{{ results.host }} ({{ results.target_ip }})

Ports Scanned:

{{ results.ports_scanned }}

Open Ports:

{{ results.summary.open_ports }}

Closed/Filtered:

{{ results.summary.closed_ports + results.summary.filtered_ports }}

🟢 Open Ports ({{ openPorts.length }})

{{ port.port }} {{ port.service }}
{{ port.response_time }}ms

▶️ 🔴 Closed Ports ({{ closedPorts.length }})

{{ port.port }} {{ port.service ||'Closed' }}
{{ port.response_time }}ms

... and {{ closedPorts.length - 20 }} more closed ports

▶️ 🟡 Filtered Ports ({{ filteredPorts.length }})

{{ port.port }} Filtered/Timeout
{{ port.response_time }}ms

... and {{ filteredPorts.length - 20 }} more filtered ports

⚠️ Important Notices

  • • {{ warning }}

No scan results yet

Configure your target and click"Start Scan" to begin port scanning.

⚠️

ℹ️ About Port Scanner Tool

TCP Port Scanning and Service Exposure

Port scanning checks whether a host accepts network connections on selected TCP ports. A defensive scan helps verify firewall rules, find unexpected services, confirm an outage, or document what a public server exposes before and after a deployment.

TCP connection behavior is defined by RFC 9293. Common service names and well-known port assignments are maintained by the IANA Service Name and Transport Protocol Port Number Registry.

How This Online Port Scanner Works

  • TCP connect scan: attempts a normal TCP connection rather than sending custom packets.
  • Port-range input: accepts individual ports, ranges such as 80-90, and common presets.
  • Service hints: maps common port numbers to likely services, but does not prove the application behind the port.
  • Timing analysis: uses connection success, refusal, and timeout behavior to classify likely states.

Port States Explained

Open

  • The target accepted a TCP connection.
  • A service is probably listening.
  • The service may still require authentication.

Closed

  • The host replied but refused the connection.
  • No service is listening on that port.
  • Network reachability is still confirmed.

Filtered or timed out

  • A firewall, ACL, route, or host policy may be dropping traffic.
  • No response arrived before timeout.
  • Results can vary by source IP and network path.

Common Ports to Review

Web and API services

  • 80: HTTP web service.
  • 443: HTTPS over TLS.
  • 8080 / 8443: common alternate web or proxy ports.
  • 3000 / 5173: common development servers that should not be public unintentionally.

Admin, mail, and data services

  • 22: SSH remote administration.
  • 25 / 587: SMTP mail delivery or submission.
  • 143 / 993: IMAP and IMAPS mailbox access.
  • 3306 / 5432: MySQL and PostgreSQL databases.

Legal, Safety, and Accuracy Limits

  • Only scan systems you own or have explicit permission to test.
  • Remote scans are logged by many firewalls, IDS systems, CDNs, and service providers.
  • This tool performs limited TCP checks; it is not a full vulnerability scanner or UDP scanner.
  • Open ports are not automatically vulnerable, and closed or filtered ports are not proof of full security.
  • Rate limiting, NAT, CDN edges, and source-based firewall rules can make results differ from scans run inside your own network.

API Usage Example:

POST /api/tools/network/port-scan
Content-Type: application/json

{
    "host": "example.com",
    "ports": "22,80,443,8080",
    "timeout": 3
}
Ready