Complete User Guide to Network Port States, Common Service Ports & Safe Simulation
How TCP/UDP Ports, Open/Closed/Filtered States & Firewall Behavior Work
On IP networks, a port number (from 1 to 65535) identifies a specific application endpoint or service running behind an IP address—such as port 22 for SSH, port 53 for DNS, port 80 for HTTP, port 443 for HTTPS, or port 5432 for PostgreSQL. When a scanner probes a port, the response (or lack of response) typically falls into three classic states: Open (an application is actively listening and accepting connections on that port), Closed (the host is reachable and responds that no service is listening on that port, often via a TCP RST packet), or Filtered (a firewall, ACL, or packet filter drops or blocks probes so the state cannot be confirmed). Because standard web browsers cannot open raw TCP/UDP SYN sockets directly, this Port Scanner Simulator models deterministic, educational port-state outcomes across host profiles and custom port lists 100% locally in your browser—with zero server uploads.
How to Use the Port Scanner Simulator in 3 Easy Steps
- Enter a Target Label & Choose a Profile Preset: Type an example host/IP label and pick a profile such as Web & App Server, Hardened Workstation, or Database & Cache Node.
- Customize Ports or Ranges (1–65535): Enter comma-separated ports or hyphenated ranges (such as
22, 80, 443, 8000-8005) and click Run Simulated Scan. - Review Port States & Export Report: Inspect Open, Filtered, and Closed counts plus per-port service labels and simulated latency, then export via Copy Scan Report or Download .txt.
Port Number Ranges & Service Identification
IANA divides the 16-bit (65,536-port) address space into three main ranges:
Total Possible Ports = 216 = 65,536
Helpful Tips for Network Security & Authorized Audits
- Close Unused Services & Restrict Management Ports: Production servers typically expose only required public ports (like
80and443) while restricting administrative ports (like22or database ports) via firewalls or VPNs. - Always Obtain Authorization Before Real Scanning: Running live port scanners against external networks or hosts without explicit permission can violate terms of service, trigger security alerts, or be illegal.
- Use Local CLI Tools for Real Packet Diagnostics: When authorized to audit your own machine or lab subnet, tools like
nmapor OS firewall utilities perform actual packet-level checks.
Worked Example: Scanning ports 22, 80, 443, 3306, 8080 against a simulated Web & App Server shows 80 (HTTP) and 443 (HTTPS) as Open, 22 (SSH) as Filtered (restricted behind firewall/VPN), and unused 3306 (MySQL) as Closed.