Nmap online port scanner use nmap's Advanced port scanner options.

Free online port scanner using online nmap's advanced port scanner tool to detect services including down and up hosts.


OS NameOS VenderOS TypeOS FamilyOS CPE



Nmap portscanner management dashboard

  • Track your openports
  • Keep your scan records
  • Incredibly fancy dashboard
  • Multiple scanner tabs
  • Entirely free

Nmap online commands and tips

Read more

Nmap scan online port scanner

Nmap Internet top port Scanning

  • 21 - FTP (File Transfer Protocol)
  • 22 - SSH (Secure Shell)
  • 23 - Telnet
  • 25 - SMTP (Mail)
  • 80 - HTTP (Web)
  • 110 - POP3 (Mail)
  • 143 - IMAP (Mail)
  • 443 - HTTPS (Secure Web))
  • 445 - SMB (Microsoft File Sharing)
  • 3389 - RDP (Remote Desktop Protocol)

To perform nmap top port scan you just have to issue this command

nmap --top-ports 10

For simplicity in hosting this nmap tool, we decided to build a simple python3-nmap scanner with all nmap command and args defined as python function. This tool is still under development and not all nmap commands are available there.

Read it's Docs The script is really easy to use just like this

import nmap3
nmap = nmap3.Nmap()
result = nmap.nmap_version_detection("")
# This is equivalent to nmap's
nmap  -sV

You can find more about this script at it's github-repository

Or Read the docs all still in development

Nmmapper Portscanner Features

  • TCP Port scanning(default)
  • Nmap online OS Detection
  • Nmap online Version Detection
  • Nmap top port scan

Testing Whether Nmap is Already Installed

$ nmap --version

Nmap version 7.60 ( )
Platform: x86_64-pc-linux-gnu
Compiled with: liblua-5.3.3 openssl-1.1.0g nmap-libssh2-1.8.0 libz-1.2.8 libpcre-8.39 libpcap-1.8.1 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

# This is on linux.


Nmap Options Summary

This options summary is printed when Nmap is run with no arguments, and the latest version is always available at It helps people remember the most common options, but is no substitute for the in-depth documentation in the rest of this manual.

$ nmap
# When you type nmap without any option or argument you get a summar

Nmap 7.60 ( )
Usage: nmap [Scan Type(s)] [Options] {target specification}
  Can pass hostnames, IP addresses, networks, etc.
  Ex:,,; 10.0.0-255.1-254
  -iL <inputfilename>: Input from list of hosts/networks
  -iR <num hosts>: Choose random targets
  --exclude <host1[,host2][,host3],...>: Exclude hosts/networks
  --excludefile <exclude_file>: Exclude list from file


Nmap Target Specification

Everything on the Nmap command-line that isn't an option (or option argument) is treated as a target host specification. The simplest case is to specify a target IP address or hostname for scanning.

When a hostname is given as a target, it is resolved via the Domain Name System (DNS) to determine the IP address to scan. If the name resolves to more than one IP address, only the first one will be scanned. To make Nmap scan all the resolved addresses instead of only the first one, use the --resolve-all option

$ nmap  -iL <inputfilename> # (Input from list) 
$ nmap  -iR <num hosts> # (Choose random targets) 
$ nmap  --exclude <host1>[,<host2>[,...]] # (Exclude hosts/networks) 
$ nmap  --excludefile <exclude_file> # (Exclude list from file) 


Host Discovery

One of the very first steps in any network reconnaissance mission is to reduce a (sometimes huge) set of IP ranges into a list of active or interesting hosts. Scanning every port of every single IP address is slow and usually unnecessary. Of course what makes a host interesting depends greatly on the scan purposes. Network administrators may only be interested in hosts running a certain service, while security auditors may care about every single device with an IP address. An administrator may be comfortable using just an ICMP ping to locate hosts on his internal network, while an external penetration tester may use a diverse set of dozens of probes in an attempt to evade firewall restrictions.

$ nmap  -sL # (List Scan) 
$ nmap  -sn # (No port scan) 
$ nmap  -Pn # (No ping) 
$ nmap -PS <port list> # (TCP SYN Ping) 
$ nmap -PA <port list> # (TCP ACK Ping) 
$ nmap -PU <port list> # (UDP Ping) 
$ nmap -PY <port list> # (SCTP INIT Ping) 
$ nmap -PE; -PP; -PM # (ICMP Ping Types) 
$ nmap  -PO <protocol list> # (IP Protocol Ping) 
$ nmap  --disable-arp-ping # (No ARP or ND Ping) 
$ nmap  --traceroute # (Trace path to host) 
$ nmap  -n # (No DNS resolution) 
$ nmap  -R # (DNS resolution for all targets) 
$ nmap  --resolve-all # (Scan each resolved address) 
$ nmap  --system-dns # (Use system DNS resolver) 
$ nmap  --dns-servers <server1>[,<server2>[,...]] # (Servers to use for reverse DNS queries) 


Port Scanning Basics

While Nmap has grown in functionality over the years, it began as an efficient port scanner, and that remains its core function. The simple command nmap <target> scans 1,000 TCP ports on the host <target>. While many port scanners have traditionally lumped all ports into the open or closed states, Nmap is much more granular. It divides ports into six states: open, closed, filtered, unfiltered, open|filtered, or closed|filtered.

The six port states recognized by Nmap

  • open An application is actively accepting TCP connections, UDP datagrams or SCTP associations on this port. Finding these is often the primary goal of port scanning. Security-minded people know that each open port is an avenue for attack. Attackers and pen-testers want to exploit the open ports, while administrators try to close or protect them with firewalls without thwarting legitimate users. Open ports are also interesting for non-security scans because they show services available for use on the network


  • closed A closed port is accessible (it receives and responds to Nmap probe packets), but there is no application listening on it. They can be helpful in showing that a host is up on an IP address (host discovery, or ping scanning), and as part of OS detection. Because closed ports are reachable, it may be worth scanning later in case some open up. Administrators may want to consider blocking such ports with a firewall. Then they would appear in the filtered state, discussed next.


  • filtered Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software. These ports frustrate attackers because they provide so little information. Sometimes they respond with ICMP error messages such as type 3 code 13 (destination unreachable: communication administratively prohibited), but filters that simply drop probes without responding are far more common. This forces Nmap to retry several times just in case the probe was dropped due to network congestion rather than filtering. This slows down the scan dramatically.


  • unfiltered  The unfiltered state means that a port is accessible, but Nmap is unable to determine whether it is open or closed. Only the ACK scan, which is used to map firewall rulesets, classifies ports into this state. Scanning unfiltered ports with other scan types such as Window scan, SYN scan, or FIN scan, may help resolve whether the port is open.


  • open|filtered  Nmap places ports in this state when it is unable to determine whether a port is open or filtered. This occurs for scan types in which open ports give no response. The lack of response could also mean that a packet filter dropped the probe or any response it elicited. So Nmap does not know for sure whether the port is open or being filtered. The UDP, IP protocol, FIN, NULL, and Xmas scans classify ports this way.


  • closed|filtered This state is used when Nmap is unable to determine whether a port is closed or filtered. It is only used for the IP ID idle scan.