4 ms·
Told me I have port 1723 open, which was a surprise. But it did NOT tell me that I have port 22 open, which I do. False negatives are a serious problem for a
by lisper 6y ago
Told me I have port 1723 open, which was a surprise. But it did NOT tell me that I have port 22 open, which I do. False negatives are a serious problem for a service like this, much more serious than false positives.
- sushisource 6y agoYeah, it's definitely missing some stuff, at least. I have a port open for WireGuard VPN traffic that it completely misses, but that's UDP so maybe that's why.
- ReverseCold 6y agoIt shouldn’t be able to find WireGuard ports. WireGuard drops all traffic that isn’t from a key it trusts, so it’s impossible to tell if you have WireGuard running on a port.
- sushisource 6y agoTIL, cool that's a neat feature.
- timmytokyo 6y agoIt found my L2TP UDP port (500).
- tru3_power 6y agoHad a similar occurrence, have a port open for some testing I’m doing and it did not report it.
- lisper 6y agoThat is unsurprising. It doesn't check in real time, it checks periodically and caches the results. But my ssh is obviously running continuously so it really should have caught it. It did catch port 22 on another IP address that I have.
- xoa 6y agoHave you had port 22 open for a while, and continuously? It's using cached results not an active scan. False negatives though would definitely be worse in this application. Also at least for me it shows nothing while I do have ports open, but that's because I whitelist limited IP ranges or single IPs for ports rather than just opening them up to the net in general. I have a VPS Wireguard bastion I bounce through for remote LAN access. That itself is a good reminder though that it's a limited tool, if a system in my whitelisted range was compromised it'd suddenly have more options, and conversely if I already had something lazy or malicious (maybe IOT, compromise or both) running on my network that was being careful about what it talked to a port scan alone wouldn't necessarily root it out. Still a potentially useful high level pass for low effort, could make one aware of some surprise devices or fat finger mistakes or the like. But "If you see 404 page, nothing is exposed" is overstating it.
- lisper 6y ago> Have you had port 22 open for a while, and continuously? Yes. > "If you see 404 page, nothing is exposed" is overstating it. Exactly.
- this_user 6y agoThis seems to be largely useless if you have a dynamic IP. According to the scan, I have FTP and HTTP open, but I just double checked, and that is definitely not the case.