Skip to main content

Timeline for Nmap - Closed vs Filtered

Current License: CC BY-SA 4.0

11 events
when toggle format what by license comment
S Jun 22, 2021 at 18:11 history suggested Matthias Braun CC BY-SA 4.0
spelling, add link
Jun 22, 2021 at 9:37 review Suggested edits
S Jun 22, 2021 at 18:11
Sep 18, 2019 at 17:04 vote accept Ryan B
Mar 29, 2018 at 11:50 history tweeted twitter.com/StackSecurity/status/979324823099924480
Mar 29, 2018 at 10:11 answer added Nomad timeline score: 24
Mar 29, 2018 at 3:02 comment added bonsaiviking Add --reason -v to your scan to see why Nmap chose each port state. filtered can mean "no response" but it can also mean "ICMP Admin Prohibited" and a few other ICMP codes. What is on the line that starts with "Not shown:" ?
Mar 28, 2018 at 20:45 comment added Ryan B Even the official explanation on NMAPs website does not address this question: filtered : Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. In my scenario, NMAP cannot determine whether ports 1, 2, 3, 4, 5 ,6 etc etc are open, because a packet filtering device blocks the probes, yet...we do not see all these ports listed in the output as filtered.
Mar 28, 2018 at 20:41 comment added Ryan B I actually came across this posting, but did not find it valuable. While the question is essentially identical to mine, the responses do not address the question. He asks: If it's normal to see 21,25 and 1863 as "filtered", then why aren't all the other ports appearing as "filtered" too!? This is my question.
Mar 28, 2018 at 20:21 comment added user171922 Did you read this solution from the Unix & Linux portal?
Mar 28, 2018 at 20:13 review First posts
Mar 28, 2018 at 20:21
Mar 28, 2018 at 20:10 history asked Ryan B CC BY-SA 3.0