Timeline for What are some instant red flags when scanning an network with nmap
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2018 at 20:02 | comment | added | schroeder♦ | That's not what I'm saying at all | |
| Jul 26, 2018 at 20:01 | comment | added | bashCypher | you're saying that port 21,22,23 is open on an external scan and you'll just ignore it because could be https running there? I don't agree. Asking for commonly dangerous ports to recognize and then do further investigation doesn't require a lesson on how ports work | |
| Jul 26, 2018 at 19:59 | comment | added | schroeder♦ | @bashCypher which is why I added it as a humorous comment and not part of the question. If, as you assert, the question is about exploitable services then the OP needs an education on how ports work. I do not give an education on how ports work, but offer a methodology.You appear to be trying to read a lot into the question. | |
| Jul 26, 2018 at 19:56 | comment | added | bashCypher | Your answer isn't inline with the question. He's asking about red flags from nmap scans, not an education on how ports work. I'm assuming he is aware of that and wants to know if any services are particularly exploitable. Nmap -A will banner grab and confirm if the service is accessible so most of this is pretty moot exept the honeypot, which is uncommon and doesn't invalidate the question. You also contradict yourself in with your comment on telnet. | |
| Jul 21, 2018 at 21:00 | comment | added | schroeder♦ | Except for telnet. If I see telnet, I hit that port first above all else. | |
| Jul 21, 2018 at 20:59 | history | answered | schroeder♦ | CC BY-SA 4.0 |