Nmap may label a UDP port open|filtered when it gets no reply: the service may be silent, or a firewall may have dropped the probe. Since UDP has no connection handshake, the scan can’t tell which is true. A clear ICMP port-unreachable message points to a closed port instead.

Multiple Choice

Which statement describes why a UDP scan can show open|filtered results?

UDP scanning relies on whether targets reply to probes, but with UDP there is no connection handshake. Many UDP services simply don’t respond to probes, and many firewalls drop UDP packets rather than replying. When there is no response, the scanner can’t tell if the port is actually open (a service listening) or filtered (blocked by a firewall), so it reports open|filtered. This ambiguity is why the result appears this way. It's not about speed or precision, and open|filtered does not mean the port is definitely open or definitely filtered. If there is a clear ICMP port-unreachable response, the port would be considered closed instead.

Understanding Nmap’s UDP Scan and the open|filtered Result

A UDP scan can leave you with an answer that sounds less than certain: open|filtered. That label isn’t a mistake, and it doesn’t mean Nmap has picked one state at random. It means the scan received no reply that could show whether a UDP port is open or blocked. With UDP, silence can tell you only so much.

Understanding that result makes Nmap’s UDP switch, -sU, much easier to use. It also helps explain why UDP scanning often takes longer than a TCP scan and why a firewall can make the picture even murkier.

UDP doesn’t come with a handshake

TCP starts with a familiar exchange. A client sends a SYN packet, and a listening service usually replies with SYN/ACK. If no service is listening, the target often sends back a reset packet. Those responses give a scanner useful clues.

UDP works differently. It has no connection handshake. A program can send a UDP packet to a service, and the service may respond—or it may not. Some UDP protocols only reply when a packet contains a valid request. A probe that doesn’t match what the service expects can be ignored without a word.

Firewalls add another layer. A firewall may silently drop an incoming UDP packet, just as a quiet doorman might let a knock go unanswered. From the scanner’s point of view, that silence could mean a service is listening but ignored the probe. It could also mean a firewall blocked the packet. The scan can’t distinguish those cases from silence alone, so Nmap reports open|filtered.

That status is deliberately cautious. It does not mean the port is definitely open, and it does not mean the port is definitely filtered. It means Nmap can’t tell which state applies based on the evidence it received.

What -sU asks Nmap to do

The -sU switch tells Nmap to scan UDP ports. For example:


nmap -sU 192.0.2.10

This command asks Nmap to check the target’s commonly scanned UDP ports. To specify particular ports, add -p:


nmap -sU -p 53,123,161 192.0.2.10

Here, Nmap checks UDP ports 53, 123, and 161, often associated with DNS, Network Time Protocol (NTP), and SNMP. These are only common associations, not proof that a service is running. Port numbers are clues; the service’s response provides stronger evidence.

A UDP scan can produce several states:

  • open: Nmap received a UDP response that indicates a service is listening.

  • closed: The target returned an ICMP port-unreachable message.

  • open|filtered: Nmap received no reply, so it can’t tell whether the port is open or filtered.

  • filtered: Nmap received an ICMP error indicating that the traffic is blocked or otherwise unreachable.

The exact interpretation depends on the reply and the network path. In particular, a clear ICMP port-unreachable response points to a closed port—not an open one.

Why silence is so common

Many UDP services don’t answer arbitrary packets. DNS, for instance, generally expects a request in a recognizable format. A generic or malformed probe may not trigger a reply. Other services may respond only under certain conditions, or not respond at all to the type of probe Nmap sends.

Then there are firewalls and network devices. They may drop UDP packets without sending an error message. That policy can reduce unwanted traffic, but it also leaves scanners with less information. The same silence can come from very different causes: an open service that ignored the probe, a filtered port, or a device that never delivered the packet to the host.

This is why “no response” is not the same as “nothing is there.” It’s more like calling a room and hearing nothing. The person might be away, busy, or unable to hear you. You can’t confidently name the reason just from the quiet.

Why UDP scans may take a while

A silent port creates a problem for the scanner: should it try again? Nmap may retransmit probes when it doesn’t receive a reply, since packet loss is possible. It also has to allow time for responses to arrive. On a network where many ports remain silent, those waits can add up.

You can narrow the scan to selected ports with -p, as shown above. That can reduce the number of probes and make the results easier to review. Nmap’s timing settings can also affect scan speed, but pushing too hard may increase missed responses or place extra load on a network. A faster scan isn’t automatically a more reliable one.

For important services, a targeted scan is often more informative than checking every UDP port at once. You can also use version detection:


nmap -sU -sV -p 53,123,161 192.0.2.10

The -sV switch asks Nmap to probe for service and version details. If a UDP service responds in a way Nmap recognizes, this can provide useful confirmation. It won’t resolve every ambiguous result, though. When a service stays silent and the network sends no helpful error, the uncertainty remains.

Zenmap makes the switches easier to see

Zenmap is Nmap’s graphical interface. Instead of typing each command by hand, you can select scan settings or enter an Nmap command in its command field. A UDP scan can use the same -sU switch as a command-line scan, and adding -p or -sV works the same way.

The interface is handy for comparing results across hosts or keeping a record of scan output. Still, the underlying network behavior doesn’t change: Zenmap can present the result, but it can’t make a silent UDP service reply. If the output shows open|filtered, the right interpretation is still “uncertain between open and filtered,” not a definite verdict.

For clearer results, compare scans from an authorized vantage point, check the host’s firewall rules, and look for logs on the target or network devices. A packet capture can also show whether a probe leaves the scanning machine and whether any response returns. These extra sources can help explain the silence, though each has its own limits.

Read the state as evidence, not a verdict

Nmap’s UDP scan is useful precisely because it can reveal services that a TCP-only view might miss. But UDP gives the scanner fewer reliable signals. There’s no handshake, some services ignore unexpected probes, and firewalls often drop packets quietly.

So when -sU reports open|filtered, treat that label as a statement about the evidence: no response arrived that could separate an open port from a filtered one. A clear ICMP port-unreachable message would indicate a closed port; a recognizable service response could confirm an open one. Silence, by itself, settles neither question.