No IPv6? Goddamnit, it is 2017.
we will be adding this soon!
You already have it.
What it needs is a way for me to switch. I'm seeing my IPv6 reputation, but I'm more interested in my IPv4.
A vulnerability rating of your IP address
21–30 of 50 posts
Re: A vulnerability rating of your IP address
#22This tool does not provide enough information about the scan and the detected "problems".
1. It's only scanning for default ports.
2. It told me about having a CVE-Score "3/3", please provide me with the exact CVEs, so I can patch my system accordingly.
3. Running a webserver on Port 80 is not insecure per se, it's just not encrypted.
4. No feature to rescan, provided information is probably old.
While I like the overall design, I think this tool is not for technical people, but for everyone who uses the word "cyber" on a daily unironically basis.
Re: A vulnerability rating of your IP address
#23Earlier quoted context omitted.
We will add this information, but essentially we and other partners have seen a high quantity of torrents infected with malware. We intend to fine tune this in the future to differentiate the torrents depending on category!
Thanks! Additional non-related questions: - How do you scan ipv6s? Scanning the entire space is easy for ipv4 (we do that for some router-security-related projects), but ipv6 space is freaking huge. - Have you considered using something like Shodan ( https://www.shodan.io/ ) API instead of scanning the address space by yourselves?
- For IPv6 rather than scanning the entire space, we are currently passively collecting addresses from multiple sources and scan specific addresses
- We wouldn't use shodan as we developed our own custom scanners and methodologies of scanning to increase data quality which is extremely important for our customers (cyberinsurers, SoCs, cyberrating companies). We also do some specific things with data which you can check on http://blog.binaryedge.io/2016/11/18/bsides-lisbon-2015/
Re: A vulnerability rating of your IP address
#24This tool does not provide enough information about the scan and the detected "problems". 1. It's only scanning for default ports. 2. It told me about having a CVE-Score "3/3", please provide me with the exact CVEs, so I can patch my system accordingly. 3. Running a webserver on Port 80 is not insecure per se, it's just not encrypted. 4. No feature to rescan, provided information is probably old. While I like the ove…
Hi!
1 - Its scanning 200 ports
2 - Indeed atm we just provide an overall view, we intend to improve this tool further. We had too many people requesting us custom scans when Doublepulsar came out.
3 - True, please submit an issue on the github so a discussion about this can be started. We like having an open formula that people can change/comment on.
4 - Scans are from last 2 months and will keep changing accordingly. It queries our database rather than doing an active scan!
Re: A vulnerability rating of your IP address
#25The numbers don't add up.
For example, I get 14 out of 100. Encryption are all 0, yet "Overall" is 3 out of 6. The only other non-zero value is "Number of open ports" (2). 2+3 != 14. Σ0 = 0 != 3.
Obviously, I have no idea what those 12 risk points are. The three encryption points are not explained at all, neither are the remaining nine.
Re: A vulnerability rating of your IP address
#26The numbers don't add up. For example, I get 14 out of 100. Encryption are all 0, yet "Overall" is 3 out of 6. The only other non-zero value is "Number of open ports" (2). 2+3 != 14. Σ0 = 0 != 3. Obviously, I have no idea what those 12 risk points are. The three encryption points are not explained at all, neither are the remaining nine.
If you find an issue with the calculation please submit an issue on https://github.com/binaryedge/ratemyip-openframework so that we can address it! Thank you so much!
Re: A vulnerability rating of your IP address
#27The numbers don't add up. For example, I get 14 out of 100. Encryption are all 0, yet "Overall" is 3 out of 6. The only other non-zero value is "Number of open ports" (2). 2+3 != 14. Σ0 = 0 != 3. Obviously, I have no idea what those 12 risk points are. The three encryption points are not explained at all, neither are the remaining nine.
The overall value of each category is truncated to the maximum value of that category - for example, if you have 10 open ports, you will get an overall score in "Attack Surface" category of 2, because it's the maximum value (vulnerability importance) that we attributed to that category.
The final score is the sum of the overall values of all categories, and then it's normalized between 0 and 100.
If you have all 0 in Encryption, and then the overall result for that category is 3, something went wrong... thank you for your feedback!
Re: A vulnerability rating of your IP address
#28> Torrent Downloads: If an IP address detected downloading torrents, the risk level is considered extreme. Why? There is some more info in the README at Github ( https://github.com/binaryedge/ratemyip-openframework ), but nothing about why torrents induce extreme risk level .
We will add this information, but essentially we and other partners have seen a high quantity of torrents infected with malware. We intend to fine tune this in the future to differentiate the torrents depending on category!
You could also differentiate OSes, in that most malware is aimed at Windows machines.
Re: A vulnerability rating of your IP address
#29Earlier quoted context omitted.
We will add this information, but essentially we and other partners have seen a high quantity of torrents infected with malware. We intend to fine tune this in the future to differentiate the torrents depending on category!
You could also differentiate OSes, in that most malware is aimed at Windows machines.
Feedback like this is exactly why we made the formula open, we believe there is still lots that can be done with this. Please submit an issue on https://github.com/binaryedge/ratemyip-openframework so that we can have a discussion about impact/usefullness!
Re: A vulnerability rating of your IP address
#30On a side note, if your fan started spinning up when you opened this, it's because of the particle simulation in the header. I know because I reviewed this library ( https://github.com/VincentGarreau/particles.js ) when a colleague wanted to add something similar to our site. The problem is it uses a naive O(n^2) algorithm for linking up particles when they get near each other, which wastes a lot of CPU cycles. Runni…
I also noticed they have some janky Javascript playing with the scrolling on the page, which also prevents me from using swipes to go back in my browser. Very annoying when sites mess with that. Give me my usual scrolling inertia!