Port Scanner Simulator
Practise reading port scan output with simulated results and port presets. Explains why a browser cannot scan, and what to run instead.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Port Scanner Simulator?
This page is a simulator, not a scanner. You enter a host and a list of ports, and it produces a report in the same shape a real scan gives you: each port with its usual service name and a status of open, closed or filtered. The statuses are generated at random. No packet is sent to the host you type, and the host name is only used as a label.
It is honest about that because a web page cannot scan ports. Browsers do not let JavaScript open raw TCP or UDP sockets, and they block connections to many well-known ports outright. Tools that claim to scan from a browser either guess from timing, which is unreliable, or run the scan on their own server against a target you name. Use the simulator to learn the vocabulary and the port numbers, then run Nmap or nc yourself for real answers.
- Simulated open, closed and filtered statuses, clearly labelled
- Ports, ranges and duplicates parsed into a clean sorted list
- Presets for common, web, database and mail ports
- Service names for well-known ports such as 22, 443, 3306 and 5432
- Sends no traffic to the host you enter
Updated
How to use the Port Scanner Simulator
- Enter any host name in Target Host. It is only used as a label in the report.
- Type ports in Ports to Scan as a comma list, ranges or both, for example 22,80,443,8000-8010. Up to 1,024 ports are used.
- Or choose a Quick Preset: Common Ports, Web Servers, Databases, Mail Servers or Ports 1-100.
- Click Start Simulation and watch the Simulated Results list fill in with a status and service name for each port.
Worked examples
Port list with a range
Input
22, 80, 8000-8003, 80
Output
Simulates ports 22, 80, 8000, 8001, 8002 and 8003
Ranges are expanded, duplicates are dropped and the list is sorted. Earlier versions read 8000-8003 as just 8000.
The real command for the same check
Input
nmap -p 22,80,8000-8003 scanme.nmap.org
Output
A table of PORT, STATE and SERVICE, measured from your machine
This is what the simulator imitates. Run it from a terminal against a host you are allowed to scan.
Background and insight
TCP ports run from 0 to 65535. IANA divides them into well-known ports (0 to 1023), registered ports (1024 to 49151) and dynamic or private ports (49152 to 65535), as described in RFC 6335. A service listening on a port is a convention, not a guarantee: SSH is usually on 22, but nothing stops someone running it on 2222.
The three statuses come from how a target answers a connection attempt. Open means something accepted it (a SYN-ACK in reply to a SYN). Closed means the host answered with a reset (RST), so it is reachable but nothing listens on that port. Filtered means no answer came back, or an ICMP unreachable message did, which usually means a firewall dropped the probe. Nmap's default SYN scan sends a SYN and never completes the handshake; its connect scan (-sT) completes it, which is what an unprivileged user gets.
Scanning systems you do not own or have written permission to test can break computer misuse laws and acceptable-use policies, and it will show up in the target's logs. Scan your own machines, your lab, or hosts that explicitly allow it, such as scanme.nmap.org, which the Nmap project provides for testing.
Common use cases
Learning scan output
Get used to reading open, closed and filtered before running Nmap on a real network for the first time.
Port number reference
Use the presets to see which ports belong to web servers, databases and mail services.
Teaching and workshops
Show students what a scan report looks like without sending traffic to anyone's servers.
Planning a real scan
Build and tidy a port list here, then copy it into an nmap -p argument.
Tips and limitations
- Never use these results to decide whether a real server is exposed. They are random every time.
- To test one port quickly from a terminal, nc -zv host 443 reports whether a TCP connection succeeds.
- A filtered result in a real scan is not proof of a firewall. Packet loss, rate limiting and slow hosts can produce it too; Nmap retries for this reason.
- UDP scanning (nmap -sU) is slow and ambiguous, because a silent UDP port can be open or filtered.
- Get written permission before scanning any network you do not own, including your employer's.
Sources and further reading
- RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry, IETF. Well-known, registered and dynamic port ranges
- Service Name and Transport Protocol Port Number Registry, IANA. Which service is registered on each port
- Port Scanning Basics, Nmap Project. Open, closed and filtered states explained
- Port Scanning Techniques, Nmap Project. SYN and connect scans
Frequently asked questions
Can a website scan ports on my server?
Not from your browser. JavaScript cannot open raw TCP or UDP sockets, and browsers block requests to many well-known ports. Websites that offer port checks run the scan from their own servers, so the result reflects their network path, not yours.
Are the results from this port scanner real?
No. Every status is generated at random to show how a scan report reads, and nothing is sent to the host you enter. Use Nmap or nc from a machine you control to check real ports.
What is the difference between a closed and a filtered port?
A closed port answers with a TCP reset, so the host is reachable but nothing is listening. A filtered port gives no reply, or an ICMP unreachable, usually because a firewall dropped the probe.
Is port scanning legal?
It depends on the country and on permission. Scanning systems you own or are authorised to test is normal practice; scanning others can breach computer misuse laws or your ISP's terms. Always get written permission first.
How do I check if port 443 is open on my server?
From another machine, run nc -zv yourserver 443 or nmap -p 443 yourserver. On the server itself, ss -tlnp (Linux) or netstat -an shows which ports are listening.
What does the Ports 1-100 preset scan?
It lists every port number from 1 to 100. It is not the 100 most common ports; for that, Nmap's --top-ports 100 option uses its own frequency data.
Is there an in-depth guide to the Port Scanner Simulator?
Yes. “Port Scanning Explained: Open, Closed and Filtered Ports” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.